Created attachment 80505 [details] dmesg: S3 call trace Environment: -------------------------- Kernel: (drm-intel-next-queued)22e407d749a418b4bb4cc93ef76e0429a9f83c82 Some additional commit info: Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Fri Jun 7 18:52:24 2013 +0300 drm/i915: Make g4x_fixup_plane() operational again Reproduce steps: -------------------------- 1. push power button to boot up machine 2. echo mem >/sys/power/state 3. push power button to resume 4. checkout dmesg BIOS version: -------------------------- HSWLPTU1.86C.0109.R03.1301282055 Description: -------------------------- After resume from S3, there's "Call trace" in dmesg. I have tested HSW ULT(BIOS version: 126), S3 is good. Call Trace: -------------------------- [ 44.290775] Call Trace: [ 44.290780] [<ffffffff816de142>] ? dump_stack+0xd/0x17 [ 44.290787] [<ffffffff8102c67d>] ? warn_slowpath_common+0x5f/0x77 [ 44.290795] [<ffffffffa00b3599>] ? intel_ddi_put_crtc_pll+0x111/0x221 [i915] [ 44.290802] [<ffffffffa00b36ea>] ? intel_ddi_pll_mode_set+0x41/0x7cf [i915] [ 44.290807] [<ffffffff81048da5>] ? up+0xb/0x36 [ 44.290810] [<ffffffff8102cfbd>] ? console_trylock+0x28/0x47 [ 44.290816] [<ffffffffa008990a>] ? ivybridge_enable_vblank+0x16/0x5c [i915] [ 44.290822] [<ffffffffa002febd>] ? drm_vblank_get+0x20f/0x220 [drm] [ 44.290834] [<ffffffffa00a9cbc>] ? haswell_crtc_mode_set+0x37/0x2b8 [i915] [ 44.290842] [<ffffffffa00abd18>] ? __intel_set_mode+0xcf6/0xf17 [i915] [ 44.290853] [<ffffffffa00af5e0>] ? intel_modeset_setup_hw_state+0x68c/0x7c8 [i915] [ 44.290856] [<ffffffff816e0d38>] ? mutex_lock+0xd/0x2d [ 44.290861] [<ffffffffa0085203>] ? __i915_drm_thaw+0x9e/0x188 [i915] [ 44.290865] [<ffffffff812ce5f1>] ? pci_pm_restore+0x7b/0x7b [ 44.290874] [<ffffffffa00855ed>] ? i915_resume+0x7d/0x9f [i915] [ 44.290876] [<ffffffff812ce645>] ? pci_pm_resume+0x54/0x7b [ 44.290880] [<ffffffff813534bf>] ? dpm_run_callback.isra.11+0x24/0x52 [ 44.290882] [<ffffffff8135400f>] ? device_resume+0x109/0x14a [ 44.290884] [<ffffffff81354064>] ? async_resume+0x14/0x38 [ 44.290890] [<ffffffff81049aef>] ? async_run_entry_fn+0x55/0x10b [ 44.290893] [<ffffffff8104075c>] ? process_one_work+0x1c5/0x2df [ 44.290895] [<ffffffff81040cb3>] ? worker_thread+0x1c7/0x2bc [ 44.290898] [<ffffffff81040aec>] ? rescuer_thread+0x251/0x251 [ 44.290900] [<ffffffff810451ca>] ? kthread+0xad/0xb5 [ 44.290905] [<ffffffff8104511d>] ? kthread_freezable_should_stop+0x40/0x40 [ 44.290907] [<ffffffff816e7d6c>] ? ret_from_fork+0x7c/0xb0 [ 44.290909] [<ffffffff8104511d>] ? kthread_freezable_should_stop+0x40/0x40 [ 44.290910] ---[ end trace ffe50d9ee4f07f39 ]---
Will you please stop cutting important information from before the Call Trace. When copying you want everything from after the '----[ cut here ]-----'
*** This bug has been marked as a duplicate of bug 64379 ***
(In reply to comment #1) > Will you please stop cutting important information from before the Call > Trace. When copying you want everything from after the '----[ cut here > ]-----' I will notice it hereafter. :)
On Sat, Jun 8, 2013 at 9:41 AM, <bugzilla-daemon@freedesktop.org> wrote: > > --- Comment #3 from shui yangwei <yangweix.shui@intel.com> --- > (In reply to comment #1) >> Will you please stop cutting important information from before the Call >> Trace. When copying you want everything from after the '----[ cut here >> ]-----' > > I will notice it hereafter. :) Note that for some backtrace bugs there's even 1-2 lines right before the cut marker (specifically the modeset state checker backtraces). The current BKMs should be up to date though, I'll add a big note about the "cut here" marker though. -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
(In reply to comment #4) > On Sat, Jun 8, 2013 at 9:41 AM, <bugzilla-daemon@freedesktop.org> wrote: > > > > --- Comment #3 from shui yangwei <yangweix.shui@intel.com> --- > > (In reply to comment #1) > >> Will you please stop cutting important information from before the Call > >> Trace. When copying you want everything from after the '----[ cut here > >> ]-----' > > > > I will notice it hereafter. :) > > Note that for some backtrace bugs there's even 1-2 lines right before > the cut marker (specifically the modeset state checker backtraces). > The current BKMs should be up to date though, I'll add a big note > about the "cut here" marker though. > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch Thanks for your reminding, I will read BKMs carefully.
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.