[Bug 98695] New: WARNING: CPU: 0 PID: 123 at ../drivers/gpu/drm/i915/intel_runtime_pm.c:1455 intel_display_power_put+0x13a/0x170 [i915]()
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Nov 12 13:17:42 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98695
Bug ID: 98695
Summary: WARNING: CPU: 0 PID: 123 at
../drivers/gpu/drm/i915/intel_runtime_pm.c:1455
intel_display_power_put+0x13a/0x170 [i915]()
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: matwey.kornilov at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Hello,
I see the following warnings at boot and every 5 seconds:
[ 17.637647] ------------[ cut here ]------------
[ 17.637814] WARNING: CPU: 0 PID: 123 at
../drivers/gpu/drm/i915/intel_runtime_pm.c:1455
intel_display_power_put+0x13a/0x170 [i915]()
[ 17.637831] WARN_ON(!power_domains->domain_use_count[domain])
[ 17.637989] Modules linked in: iscsi_ibft iscsi_boot_sysfs sd_mod
hid_generic snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
joydev hid_penmount usbhid intel_rapl intel_soc_dts_iosf intel_powerclamp
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel
jitterentropy_rng snd_hda_intel iTCO_wdt drbg iTCO_vendor_support igb
snd_hda_codec ahci libahci ptp pps_core lpc_ich dca ansi_cprng i915 mei_txe
aesni_intel xhci_pci xhci_hcd aes_x86_64 lrw gf128mul glue_helper ablk_helper
cryptd serio_raw drm_kms_helper pcspkr i2c_i801 snd_hda_core mfd_core shpchp
snd_hwdep mei usbcore usb_common drm fb_sys_fops syscopyarea sysfillrect
sysimgblt libata i2c_algo_bit fan thermal snd_intel_sst_acpi snd_intel_sst_core
snd_soc_sst_mfld_platform snd_soc_rt5640 snd_soc_rl6231 snd_soc_core
snd_compress 8250_fintek snd_pcm regmap_i2c snd_timer fjes intel_smartconnect
video i2c_hid rfkill_gpio snd soundcore sdhci_acpi sdhci
i2c_designware_platform i2c_designware_core mmc_core snd_soc_sst_acpi rfkill
8250_dw pwm_lpss_platform pwm_lpss button processor sg scsi_mod autofs4
[ 17.638061] CPU: 0 PID: 123 Comm: kworker/0:2 Tainted: G W
4.4.27-2-default #1
[ 17.638066] Hardware name: Lex BayTrail 3I380CW A2 /Type2 -
Board Product Name, BIOS 3I380CW A3 09/29/2014
[ 17.638220] Workqueue: events edp_panel_vdd_work [i915]
[ 17.638235] 0000000000000000 ffffffff81327657 ffff88007f84bda8
ffffffffa059c598
[ 17.638245] ffffffff8107e821 ffff88012ed4006c ffff88007f84bdf8
ffff88012ed40000
[ 17.638256] ffff88012ed49570 0000000000000000 ffffffff8107e89c
ffffffffa05adebf
[ 17.638258] Call Trace:
[ 17.638308] [<ffffffff81019e69>] dump_trace+0x59/0x320
[ 17.638330] [<ffffffff8101a22a>] show_stack_log_lvl+0xfa/0x180
[ 17.638348] [<ffffffff8101afd1>] show_stack+0x21/0x40
[ 17.638367] [<ffffffff81327657>] dump_stack+0x5c/0x85
[ 17.638387] [<ffffffff8107e821>] warn_slowpath_common+0x81/0xb0
[ 17.638404] [<ffffffff8107e89c>] warn_slowpath_fmt+0x4c/0x50
[ 17.638544] [<ffffffffa04e6faa>] intel_display_power_put+0x13a/0x170 [i915]
[ 17.638584] [<ffffffff81097205>] process_one_work+0x155/0x440
[ 17.638603] [<ffffffff81097d46>] worker_thread+0x116/0x4b0
[ 17.638623] [<ffffffff8109d328>] kthread+0xc8/0xe0
[ 17.638645] [<ffffffff8160978f>] ret_from_fork+0x3f/0x70
[ 17.652669] DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70
[ 17.652671]
[ 17.652674] Leftover inexact backtrace:
[ 17.652674]
[ 17.652693] [<ffffffff8109d260>] ? kthread_park+0x50/0x50
[ 17.652769] ---[ end trace a1367dbfc4ba2a52 ]---
Using bisect, I've found that a781ce79d51fc4952870c998937980a042927e84 is the
first broken commit, and this issue is present in kernel master too.
Additional information are available in openSUSE bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=1009674
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161112/e8cb27d4/attachment.html>
More information about the intel-gfx-bugs
mailing list