Hide Forgot
Description of problem: Kernel oops on resume from suspend on HP z230 workstation Version-Release number of selected component (if applicable): kernel-4.7.3-200.fc24.x86_64 How reproducible: every time Steps to Reproduce: 1. Suspend from F24 Workstation (GNOME, X11 session) 2. hit a key on keyboard to wake/resume 3. oops! freeze, must reboot. Kernel trace: ------------[ cut here ]------------ WARNING: CPU: 6 PID: 7554 at sound/pci/echoaudio/echoaudio_gml.c:116 set_digital_mode+0x34b/0x400 [snd_layla24] Modules linked in: snd_seq_dummy hid_logitech_hidpp hid_logitech_dj xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT nf_reject_ipv6 xt_conntrack ip6t_rpfilter ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw ip6table_security ip6table_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw iptable_security iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_cstate intel_uncore snd_hda_codec_realtek snd_hda_codec_generic intel_rapl_perf snd_seq_midi snd_seq_midi_event hp_wmi sparse_keymap iTCO_wdt rfkill iTCO_vendor_support mei_wdt ppdev tpm_infineon i915 snd_hda_intel snd_hda_codec e1000e snd_hda_core snd_layla24 i2c_i801 video snd_hwdep snd_rawmidi i2c_algo_bit snd_seq drm_kms_helper snd_seq_device ptp lpc_ich shpchp snd_pcm drm pps_core wmi mei_me snd_timer mei snd parport_pc parport soundcore tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc crc32c_intel serio_raw fjes CPU: 6 PID: 7554 Comm: kworker/u16:59 Not tainted 4.7.2-201.fc24.x86_64 #1 Hardware name: Hewlett-Packard HP Z230 Tower Workstation/1905, BIOS L51 v01.18 01/23/2014 Workqueue: events_unbound async_run_entry_fn 0000000000000286 00000000515ce47f ffff88022bc9fb88 ffffffff813d941f 0000000000000000 0000000000000000 ffff88022bc9fbc8 ffffffff8109facb 00000074813e6c37 ffff8802535ad000 00000000fffffff5 0000000000000000 Call Trace: [<ffffffff813d941f>] dump_stack+0x63/0x84 [<ffffffff8109facb>] __warn+0xcb/0xf0 [<ffffffff8109fbfd>] warn_slowpath_null+0x1d/0x20 [<ffffffffc0319d9b>] set_digital_mode+0x34b/0x400 [snd_layla24] [<ffffffffc031a626>] restore_dsp_rettings+0x156/0x1d0 [snd_layla24] [<ffffffffc031a754>] init_line_levels+0xb4/0xc0 [snd_layla24] [<ffffffffc031a917>] init_hw+0x1b7/0x9c0 [snd_layla24] [<ffffffffc031b18e>] snd_echo_resume+0x6e/0x280 [snd_layla24] [<ffffffff8142bf54>] pci_pm_resume+0x64/0xa0 [<ffffffff8142bef0>] ? pci_pm_thaw+0x90/0x90 [<ffffffff8152e87d>] dpm_run_callback+0x4d/0x130 [<ffffffff8152ede6>] device_resume+0xa6/0x200 [<ffffffff8152ef5d>] async_resume+0x1d/0x50 [<ffffffff810c1f2a>] async_run_entry_fn+0x4a/0x140 [<ffffffff810b9314>] process_one_work+0x184/0x440 [<ffffffff810b961e>] worker_thread+0x4e/0x480 [<ffffffff810b95d0>] ? process_one_work+0x440/0x440 [<ffffffff810bf4f8>] kthread+0xd8/0xf0 [<ffffffff817eba7f>] ret_from_fork+0x1f/0x40 [<ffffffff810bf420>] ? kthread_worker_fn+0x180/0x180 ---[ end trace 3bee3f949233084d ]---
Sorry, this was kernel-4.7.2-201.fc24, not 4.7.3-200.fc24.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.