[Bug 80549] [IVB,HSW bisected]Resuming form s3 cause Call Trace, with warm boot
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jul 18 06:40:34 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=80549
--- Comment #7 from Paulo Zanoni <przanoni at gmail.com> ---
(In reply to comment #6)
> (In reply to comment #5)
> > Can you please retest this on HSW with the current drm-intel-nightly tree?
> >
> > I believe commit daa390e5ee45cc051d6bf37b296901f2f92b002d "drm/i915: don't
> > warn if IRQs are disabled when shutting down display IRQs" fixed the last
> > problem on HSW.
> >
> > I am not sure about IVB.
>
> We retested on latest drm-intel-nightly and we didn't find this Call Trace.
> But we found another one still there. I have no idea that if this one is
> related with the one we talked about.
> [ 620.126722] ------------[ cut here ]------------
> [ 620.126747] WARNING: CPU: 2 PID: 3692 at
> drivers/gpu/drm/i915/i915_irq.c:154 ironlake_disable_vblank+0x41/0x54
> [i915]()
> [ 620.126763] Modules linked in: dm_mod iTCO_wdt iTCO_vendor_support
> snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi pcspkr
> i2c_i801 lpc_ich mfd_core snd_hda_intel snd_hda_controller snd_hda_codec
> snd_hwdep snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core
> v4l2_common videodev snd_timer snd soundcore wmi battery ac acpi_cpufreq
> i915 button video drm_kms_helper drm
> [ 620.126766] CPU: 2 PID: 3692 Comm: kworker/u16:61 Tainted: G W
> 3.16.0-rc5_drm-intel-nightly_f326cd_20140717+ #574
> [ 620.126767] Hardware name: LENOVO 20267 /Cherry 3A , BIOS
> 7CCN15WW 07/24/2013
> [ 620.126772] Workqueue: events_unbound async_run_entry_fn
> [ 620.126774] 0000000000000000 0000000000000009 ffffffff8178053d
> 0000000000000000
> [ 620.126776] ffffffff8103986c ffff88015a3ec000 ffffffffa0096887
> ffff88015a3ec000
> [ 620.126778] 0000000000000001 ffff880154cf0000 ffff880154cf7020
> 0000000000000002
> [ 620.126779] Call Trace:
> [ 620.126785] [<ffffffff8178053d>] ? dump_stack+0x41/0x51
> [ 620.126789] [<ffffffff8103986c>] ? warn_slowpath_common+0x78/0x90
> [ 620.126802] [<ffffffffa0096887>] ? ironlake_disable_vblank+0x41/0x54
> [i915]
> [ 620.126813] [<ffffffffa0096887>] ? ironlake_disable_vblank+0x41/0x54
> [i915]
> [ 620.126821] [<ffffffffa0005548>] ? vblank_disable_and_save+0x3d/0x152
> [drm]
> [ 620.126828] [<ffffffffa0005d26>] ? drm_vblank_off+0x3a/0x147 [drm]
> [ 620.126843] [<ffffffffa00ba9b5>] ? haswell_crtc_disable+0x3c/0x278 [i915]
> [ 620.126857] [<ffffffffa00b456f>] ? intel_crtc_control+0x81/0xc4 [i915]
> [ 620.126864] [<ffffffffa006e265>] ? i915_drm_freeze+0xd4/0x166 [i915]
> [ 620.126868] [<ffffffff81350d12>] ? pci_pm_suspend+0x7b/0xfb
> [ 620.126873] [<ffffffff813de98f>] ? __pm_runtime_barrier+0x10/0xfe
> [ 620.126875] [<ffffffff81350c97>] ? pci_pm_freeze+0xb5/0xb5
> [ 620.126878] [<ffffffff813e0260>] ? dpm_run_callback+0x57/0xcf
> [ 620.126881] [<ffffffff813e105c>] ? __device_suspend+0x1d3/0x25f
> [ 620.126884] [<ffffffff813e10fe>] ? async_suspend+0x16/0x7d
> [ 620.126887] [<ffffffff810568af>] ? async_run_entry_fn+0x55/0x10b
> [ 620.126889] [<ffffffff8104d636>] ? process_one_work+0x1e2/0x363
> [ 620.126891] [<ffffffff8104de16>] ? worker_thread+0x2f2/0x3f1
> [ 620.126893] [<ffffffff8104db24>] ? pool_mayday_timeout+0xf2/0xf2
> [ 620.126896] [<ffffffff8105258e>] ? kthread+0xc5/0xcd
> [ 620.126899] [<ffffffff810524c9>] ?
> kthread_freezable_should_stop+0x40/0x40
> [ 620.126902] [<ffffffff8178602c>] ? ret_from_fork+0x7c/0xb0
> [ 620.126904] [<ffffffff810524c9>] ?
> kthread_freezable_should_stop+0x40/0x40
> [ 620.126906] ---[ end trace 9e41ade7fe768372 ]---
This WARN should not exist on -nightly anymore. Are you sure the tree you
tested contains commit daa390e5ee45cc051d6bf37b296901f2f92b002d "drm/i915:
don't warn if IRQs are disabled when shutting down display IRQs"?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140718/c32f107d/attachment.html>
More information about the intel-gfx-bugs
mailing list