Bug 67515

Summary: [HSW]igt/gem_suspend causes Call Trace
Product: DRI Reporter: lu hua <huax.lu>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: xunx.fang, yangweix.shui
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description lu hua 2013-07-30 03:35:50 UTC
Created attachment 83256 [details]
dmesg

System Environment:
--------------------------
Platform:    Ironlake
Kernel:     (drm-intel-next-queued)fae5cbff3e3e4097de2e76178d462b90626c2bdb

Bug detailed description:
-----------------------------
Run ./gem_suspend or sub cases fence-restore-untiled/fence-restore-tiled2untiled ,
Call trace appears in dmesg. It happens on -queued, -fixes, -nightly kernel.
It's a new igt case.

output:
rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jul 30 03:27:55 2013
checking the first canary object
checking the second canary object
rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jul 30 03:28:28 2013
checking the first canary object
checking the second canary object

Call trace:
[   36.055267] ------------[ cut here ]------------
[   36.055279] WARNING: CPU: 7 PID: 3803 at drivers/gpu/drm/i915/intel_ddi.c:383 intel_ddi_put_crtc_pll+0x111/0x221 [i915]()
[   36.055287] Modules linked in: ipv6 dm_mod snd_hda_codec_realtek pcspkr i2c_i801 iTCO_wdt iTCO_vendor_support lpc_ich snd_hda_intel mfd_core snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore acpi_cpufreq i915 video button drm_kms_helper drm mperf freq_table
[   36.055289] CPU: 7 PID: 3803 Comm: kworker/u16:9 Not tainted 3.11.0-rc2_drm-intel-fixes_61c254_20130727_+ #6282
[   36.055290] Hardware name: Intel Corporation Shark Bay Client platform/Flathead Creek Crb, BIOS HSWLPTU1.86C.0109.R03.1301282055 01/28/2013
[   36.055293] Workqueue: events_unbound async_run_entry_fn
[   36.055295]  0000000000000000 0000000000000009 ffffffff816ed5e8 0000000000000000
[   36.055296]  ffffffff810320e9 0000000000000282 ffffffffa00910e9 ffff88023f60c000
[   36.055297]  ffff88023f60c000 ffff88024318c000 0000000000202418 0000000000000000
[   36.055297] Call Trace:
[   36.055302]  [<ffffffff816ed5e8>] ? dump_stack+0x41/0x51
[   36.055305]  [<ffffffff810320e9>] ? warn_slowpath_common+0x73/0x8b
[   36.055310]  [<ffffffffa00910e9>] ? intel_ddi_put_crtc_pll+0x111/0x221 [i915]
[   36.055314]  [<ffffffffa00910e9>] ? intel_ddi_put_crtc_pll+0x111/0x221 [i915]
[   36.055319]  [<ffffffffa009123a>] ? intel_ddi_pll_mode_set+0x41/0x7cf [i915]
[   36.055320]  [<ffffffff8104ea7d>] ? up+0xb/0x36
[   36.055322]  [<ffffffff81032996>] ? console_trylock+0x28/0x47
[   36.055326]  [<ffffffffa00685ff>] ? ivybridge_enable_vblank+0x16/0x5b [i915]
[   36.055330]  [<ffffffffa000be59>] ? drm_vblank_get+0x20f/0x220 [drm]
[   36.055335]  [<ffffffffa00878af>] ? haswell_crtc_mode_set+0x3c/0x2da [i915]
[   36.055340]  [<ffffffffa008995f>] ? __intel_set_mode+0xd30/0xf4e [i915]
[   36.055346]  [<ffffffffa008d0f0>] ? intel_modeset_setup_hw_state+0x7be/0x8fb [i915]
[   36.055348]  [<ffffffff816f0854>] ? mutex_lock+0xd/0x2d
[   36.055351]  [<ffffffffa0062203>] ? __i915_drm_thaw+0x9e/0x188 [i915]
[   36.055354]  [<ffffffff812e25dd>] ? pci_pm_restore+0x7b/0x7b
[   36.055357]  [<ffffffffa00625ed>] ? i915_resume+0x7d/0x9f [i915]
[   36.055358]  [<ffffffff812e2631>] ? pci_pm_resume+0x54/0x7b
[   36.055361]  [<ffffffff813689eb>] ? dpm_run_callback.isra.11+0x24/0x52
[   36.055363]  [<ffffffff8136953b>] ? device_resume+0x109/0x14a
[   36.055364]  [<ffffffff81369590>] ? async_resume+0x14/0x38
[   36.055365]  [<ffffffff8104fbff>] ? async_run_entry_fn+0x55/0x10b
[   36.055367]  [<ffffffff810460b4>] ? process_one_work+0x1c5/0x2df
[   36.055368]  [<ffffffff8104660b>] ? worker_thread+0x1c7/0x2bc
[   36.055369]  [<ffffffff81046444>] ? rescuer_thread+0x251/0x251
[   36.055371]  [<ffffffff8104afca>] ? kthread+0xad/0xb5
[   36.055373]  [<ffffffff8104af1d>] ? kthread_freezable_should_stop+0x40/0x40
[   36.055374]  [<ffffffff816f7d6c>] ? ret_from_fork+0x7c/0xb0
[   36.055376]  [<ffffffff8104af1d>] ? kthread_freezable_should_stop+0x40/0x40
[   36.055377] ---[ end trace cd8ad24ffdb0eae1 ]---


Reproduce steps:
----------------------------
1. ./gem_suspend
Comment 1 Chris Wilson 2013-07-30 08:18:49 UTC
Another set of shared plls that need reconstruction upon resume. I'll propose something and Daniel can rewrite it completely when he gets back from holiday.
Comment 2 Daniel Vetter 2013-08-04 21:27:14 UTC
Hm, where's the patch I should completely rewrite?
Comment 3 Daniel Vetter 2013-08-04 21:34:49 UTC
Oh, that's just hsw ddi plls getting confused after resume. Already tracked.

*** This bug has been marked as a duplicate of bug 64379 ***
Comment 4 lu hua 2014-06-10 05:24:43 UTC
Verified.Fixed.
Comment 5 Elizabeth 2017-10-06 14:44:31 UTC
Closing old verified.

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.