[Bug 63586] New: [HSW desktop regression]Resume from s4 causes call trace and system hang

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 15 23:08:05 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=63586

          Priority: high
            Bug ID: 63586
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [HSW desktop regression]Resume from s4 causes call
                    trace and system hang
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: cancan.feng at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 78055
  --> https://bugs.freedesktop.org/attachment.cgi?id=78055&action=edit
dmesg by netconsole

Environment:
-------------------
Kernel: (drm-intel-next-queued)d41ca032afdb4e12a9782df523c8798cd42aaaa3
Some additional commit info:
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date:   Thu Apr 11 19:49:07 2013 +0200

    drm/i915: move debug output back to the right place

Description:
--------------------
When I do s4 on Haswell desktop, I found the machine can suspend successfully,
but resume with call trace and system hang. I attached the dmesg info in the
attachment. I couldn't fetch the call trace info, so I took a picture and
attached it in the attachment.
If I remove i915, then do s4, the machine can suspend successfully, but just
auto resume from s4 without call trace or system hang. By the way, problem of
auto resume always exist.

Reproduce step:
----------------------
1.boot or reboot
2.echo disk > /sys/power/state
3.resume

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130416/dc76c843/attachment.html>


More information about the intel-gfx-bugs mailing list