[Bug 65496] New: [HSW] Probabilistic resume from s4 causes call trace and system hang, with warm boot

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jun 7 00:51:01 PDT 2013


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

          Priority: medium
            Bug ID: 65496
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [HSW] Probabilistic resume from s4 causes call trace
                    and system hang, with warm boot
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: yangweix.shui at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 80458
  --> https://bugs.freedesktop.org/attachment.cgi?id=80458&action=edit
picture: probabilistic S4 call trace and hang

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:
--------------------
This bug is used to separate from bug #63586, run S4 test in a loop, when
execute 95 times, system resume with call trace and hang. This issue is
probabilistic, perhaps it will come up to your eyes for just a while S4 test or
more. I append the picture of the call trace in attachment.

Reproduce step:
----------------------
1.boot up machine with command "reboot"(warm boot)
2.echo 0 > /sys/class/rtc/rtc0/wakealarm ; 
  echo +10 > /sys/class/rtc/rtc0/wakealarm; 
3.echo disk > /sys/power/state
4.loop running step 2 and 3

-- 
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/20130607/b5dcc81f/attachment-0001.html>


More information about the intel-gfx-bugs mailing list