sys-kernel/gentoo-sources-3.14.14 was built with the following: USE="symlink -build -deblob -experimental" ABI_X86="64" [ 5.143994] ------------[ cut here ]------------ [ 5.144001] WARNING: CPU: 0 PID: 72 at drivers/gpu/drm/i915/intel_pm.c:5356 i915_request_power_well+0x34/0x40 [i915]() [ 5.144002] Modules linked in: i915 snd_hda_codec_hdmi rtl8192ce i2c_algo_bit rtl_pci drm_kms_helper rtlwifi snd_hda_codec_realtek intel_gtt snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec evdev snd_pcm iTCO_wdt snd_timer video snd drm rtl8192c_common soundcore coretemp hwmon x86_pkg_temp_thermal microcode i2c_i801 agpgart firmware_class backlight rtc_cmos mei_me lpc_ich mei mfd_core button sg vboxnetadp(O) vboxnetflt(O) vboxdrv(O) acpi_cpufreq ipv6 efivarfs ext4 crc16 mbcache jbd2 raid456 async_raid6_recov async_memcpy async_pq raid6_pq async_xor xor async_tx md_mod sr_mod cdrom sd_mod usbkbd hid_generic usbhid ahci libahci libata xhci_hcd scsi_mod ehci_pci ehci_hcd usbcore usb_common processor unix dm_mod efivars [ 5.144022] CPU: 0 PID: 72 Comm: kworker/0:1 Tainted: G W O 3.14.14-gentoo-perfectus #9 [ 5.144023] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H87 Pro4, BIOS P2.10 07/09/2014 [ 5.144025] Workqueue: events azx_probe_work [snd_hda_intel] [ 5.144026] 0000000000000009 ffff880417d93cb8 ffffffff81445ad3 0000000000000001 [ 5.144027] 0000000000000000 ffff880417d93cf8 ffffffff81057ce7 0000000000000000 [ 5.144028] ffff880417d69780 ffff880417e4ea20 ffff880417e4ea20 0000000000000000 [ 5.144030] Call Trace: [ 5.144033] [<ffffffff81445ad3>] dump_stack+0x4f/0x7c [ 5.144040] [<ffffffff81057ce7>] warn_slowpath_common+0x87/0xb0 [ 5.144041] [<ffffffff81057d25>] warn_slowpath_null+0x15/0x20 [ 5.144045] [<ffffffffa09fe4d4>] i915_request_power_well+0x34/0x40 [i915] [ 5.144047] [<ffffffffa0878cd2>] hda_display_power+0x32/0x40 [snd_hda_intel] [ 5.144048] [<ffffffffa0877385>] azx_probe_work+0x55/0xc00 [snd_hda_intel] [ 5.144051] [<ffffffff810145e2>] ? __switch_to+0x172/0x500 [ 5.144053] [<ffffffff8108229e>] ? finish_task_switch+0xce/0x120 [ 5.144055] [<ffffffff81447eae>] ? __schedule+0x39e/0x7c0 [ 5.144057] [<ffffffff81073158>] process_one_work+0x178/0x450 [ 5.144059] [<ffffffff81073589>] worker_thread+0x119/0x370 [ 5.144061] [<ffffffff81073470>] ? process_scheduled_works+0x40/0x40 [ 5.144062] [<ffffffff8107a1a4>] kthread+0xc4/0xe0 [ 5.144063] [<ffffffff8107a0e0>] ? flush_kthread_worker+0x70/0x70 [ 5.144065] [<ffffffff8145328c>] ret_from_fork+0x7c/0xb0 [ 5.144066] [<ffffffff8107a0e0>] ? flush_kthread_worker+0x70/0x70 [ 5.144067] ---[ end trace 3cbe06ca6c826fb0 ]---
My hardware: MB: AsRock H87 Pro4 CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Linux developer 3.14.14-gentoo-perfectus #9 SMP PREEMPT Fri Aug 22 13:25:47 EEST 2014 x86_64 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz GenuineIntel GNU/Linux
Can you please test 3.14.22 and tell me if this still is an issue?
Same happens with 3.14.22: ================================================================= Package Settings ================================================================= sys-kernel/gentoo-sources-3.14.22 was built with the following: USE="-build -deblob -experimental -symlink" ABI_X86="64" Linux developer 3.14.22-gentoo-perfectus #1 SMP PREEMPT Wed Oct 22 17:22:32 EEST 2014 x86_64 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz GenuineIntel GNU/Linux [ 4.179004] ------------[ cut here ]------------ [ 4.179011] WARNING: CPU: 0 PID: 72 at drivers/gpu/drm/i915/intel_pm.c:5356 i915_request_power_well+0x34/0x40 [i915]() [ 4.179012] Modules linked in: i915 i2c_algo_bit drm_kms_helper drm arc4 rtl8192ce snd_hda_codec_hdmi evdev rtl_pci rtlwifi snd_hda_codec_realtek intel_gtt agpgart iTCO_wdt snd_hda_codec_generic coretemp snd_hda_intel hwmon mac80211 snd_hda_codec snd_pcm mei_me video mei rtl8192c_common lpc_ich snd_timer snd x86_pkg_temp_thermal rtc_cmos microcode mfd_core firmware_class button i2c_i801 soundcore backlight sg acpi_cpufreq ipv6 efivarfs usbkbd ext4 crc16 mbcache jbd2 hid_generic usbhid raid456 async_raid6_recov async_memcpy async_pq raid6_pq async_xor xor async_tx md_mod sr_mod cdrom sd_mod ahci libahci xhci_hcd libata ehci_pci ehci_hcd scsi_mod usbcore usb_common processor unix dm_mod efivars [ 4.179031] CPU: 0 PID: 72 Comm: kworker/0:1 Tainted: G W 3.14.22-gentoo-perfectus #1 [ 4.179040] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H87 Pro4, BIOS P2.10 07/09/2014 [ 4.179043] Workqueue: events azx_probe_work [snd_hda_intel] [ 4.179044] 0000000000000009 ffff880417a1bcb8 ffffffff81446932 0000000000000001 [ 4.179045] 0000000000000000 ffff880417a1bcf8 ffffffff81057d17 0000000000000000 [ 4.179046] ffff880417a0b780 ffff88041202be20 ffff88041202be20 0000000000000000 [ 4.179048] Call Trace: [ 4.179051] [<ffffffff81446932>] dump_stack+0x4f/0x7c [ 4.179054] [<ffffffff81057d17>] warn_slowpath_common+0x87/0xb0 [ 4.179056] [<ffffffff81057d55>] warn_slowpath_null+0x15/0x20 [ 4.179059] [<ffffffffa08655a4>] i915_request_power_well+0x34/0x40 [i915] [ 4.179061] [<ffffffffa06cccd2>] hda_display_power+0x32/0x40 [snd_hda_intel] [ 4.179063] [<ffffffffa06cb385>] azx_probe_work+0x55/0xc00 [snd_hda_intel] [ 4.179066] [<ffffffff810145e2>] ? __switch_to+0x172/0x500 [ 4.179068] [<ffffffff810822de>] ? finish_task_switch+0xce/0x120 [ 4.179070] [<ffffffff81448d0e>] ? __schedule+0x39e/0x7c0 [ 4.179072] [<ffffffff81073188>] process_one_work+0x178/0x450 [ 4.179073] [<ffffffff810735b9>] worker_thread+0x119/0x370 [ 4.179074] [<ffffffff810734a0>] ? process_scheduled_works+0x40/0x40 [ 4.179076] [<ffffffff8107a1e4>] kthread+0xc4/0xe0 [ 4.179077] [<ffffffff8107a120>] ? flush_kthread_worker+0x70/0x70 [ 4.179079] [<ffffffff8145410c>] ret_from_fork+0x7c/0xb0 [ 4.179080] [<ffffffff8107a120>] ? flush_kthread_worker+0x70/0x70 [ 4.179081] ---[ end trace dc9de820b4df6c32 ]---
This bug: https://bugzilla.kernel.org/show_bug.cgi?id=73971 talks to this being fixed in a april 2014 commit. While I cannot say which commit it is, I can see that the latest april commit is in >=3.15 kernels. Can you test on a later kernel than 3.14 and report the results. The latest 3.18 kernel is preferred which is 3.18.1 as of this writing.
@Mike, Sure. I will check and report.
Just checked with 3.18.2 and 3.17.7 and problem seems fixed. I think we can mark this bug as SOLVED. Thanks, Mike.
Thanks for testing, Igor
