Bug 82841 - [BYT-M Regression]S3/S4 sauses " WARNING: CPU: 0 PID: 987 at drivers/gpu/drm/i915/intel_dp.c:1223 intel_dp_probe_oui.part.14+0x12/0xb9 [i915]()"
Summary: [BYT-M Regression]S3/S4 sauses " WARNING: CPU: 0 PID: 987 at drivers/gpu/drm/...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: highest normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-20 06:01 UTC by Guo Jinxian
Modified: 2017-02-10 08:54 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (107.23 KB, text/plain)
2014-08-20 06:01 UTC, Guo Jinxian
no flags Details

Description Guo Jinxian 2014-08-20 06:01:06 UTC
Created attachment 104936 [details]
dmesg

==System Environment==
--------------------------
Regression: Yes.
Result on -next-queued(5193109cd669c7990b043a7187548546c16f8af3) was "System unable resume from S3/S4 "(Bug 81948)

Non-working platforms: BYT-M

==kernel==
--------------------------
origin/drm-intel-nightly: 49ceddc7b3b0e3f7eb21b9fb4c9b840cff630047(fails)
    drm-intel-nightly: 2014y-08m-19d-19h-02m-49s integration manifest
origin/drm-intel-next-queued: 3f72c7b12f1a81a32fd37216b3382e6fe46a7184(fails)
    drm/i915/bdw: Disable execlists by default
origin/drm-intel-fixes: 1a125d8a2c22b11741fc47d4ffcf7a5ffa044dd3(fails)
    drm/i915: don't try to retrain a DP link on an inactive CRTC

==Bug detailed description==
-----------------------------
S3/S4 sauses " WARNING: CPU: 0 PID: 987 at drivers/gpu/drm/i915/intel_dp.c:1223 intel_dp_probe_oui.part.14+0x12/0xb9 [i915]()"

System unable resume from S3/S4 before(Bug 81948)

Output:
root@x-bytm02:~# dmesg -r|egrep "<[1-4]>"|grep drm
root@x-bytm02:~# echo 0 > /sys/class/rtc/rtc0/wakealarm ; echo +10 > /sys/class/rtc/rtc0/wakealarm; echo mem > /sys/power/state
root@x-bytm02:~# dmesg -r|egrep "<[1-4]>"|grep drm                                                                 
 <4>[   57.438319] WARNING: CPU: 0 PID: 987 at drivers/gpu/drm/i915/intel_dp.c:1223 intel_dp_probe_oui.part.14+0x12/0xb9 [i915]()
<4>[   57.438348] Modules linked in: dm_mod iTCO_wdt snd_hda_codec_hdmi iTCO_vendor_support snd_hda_codec_conexant snd_hda_codec_generic pcspkr i2c_i801 snd_hda_intel lpc_ich snd_hda_controller r8169 mfd_core snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore battery wmi iosf_mbi ac acpi_cpufreq uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea
<4>[   57.438353] CPU: 0 PID: 987 Comm: kworker/u8:2 Not tainted 3.17.0-rc1_drm-intel-nightly_09fcef_20140819+ #1580
<4>[   57.438492]  [<ffffffffa00590ac>] ? drm_helper_hpd_irq_event+0x60/0xe8 [drm_kms_helper]
<4>[   57.438507]  [<ffffffffa007d216>] ? __i915_drm_thaw+0x121/0x16a [i915]
<4>[   57.463714] WARNING: CPU: 3 PID: 987 at drivers/gpu/drm/i915/intel_dp.c:1294 edp_panel_vdd_off+0x33/0x58 [i915]()
<4>[   57.463742] Modules linked in: dm_mod iTCO_wdt snd_hda_codec_hdmi iTCO_vendor_support snd_hda_codec_conexant snd_hda_codec_generic pcspkr i2c_i801 snd_hda_intel lpc_ich snd_hda_controller r8169 mfd_core snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore battery wmi iosf_mbi ac acpi_cpufreq uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea
<4>[   57.463747] CPU: 3 PID: 987 Comm: kworker/u8:2 Tainted: G        W      3.17.0-rc1_drm-intel-nightly_09fcef_20140819+ #1580
<4>[   57.463910]  [<ffffffffa00590ac>] ? drm_helper_hpd_irq_event+0x60/0xe8 [drm_kms_helper]
<4>[   57.463926]  [<ffffffffa007d216>] ? __i915_drm_thaw+0x121/0x16a [i915]

Reproduce steps:
-------------------------
==Reproduce steps==
---------------------------- 
1. echo mem >/sys/power/state
2. Press power button
Comment 1 Imre Deak 2014-11-11 12:05:21 UTC
Could you try the latest -nightly, Ville's VDD/PPS locking fixes should get rid of this WARN.
Comment 2 Li Xu 2014-11-14 02:00:29 UTC
We have try 5 times with the latest -nightly,and this situation has disappered.
Comment 3 Jari Tahvanainen 2017-02-10 08:54:36 UTC
Closing (>2 years) old Verified+Fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.