[Bug 71238] New: [HSW ULT] Loop to test S4, system will call trace and network disconnect

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Nov 4 17:10:45 PST 2013


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

          Priority: medium
            Bug ID: 71238
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [HSW ULT] Loop to test S4, system will call trace and
                    network disconnect
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: qingshuai.tian at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 88658
  --> https://bugs.freedesktop.org/attachment.cgi?id=88658&action=edit
Image of  Call trace

Environment:
-------------------
Kernel: (drm-intel-next-queued)9d1cb9147dbe45f6e94dc796518ecf67cb64b359
Author: Paulo Zanoni <paulo.r.zanoni at intel.com>
Date:   Fri Nov 1 13:32:08 2013 -0200
         drm/i915: avoid unclaimed registers when capturing the error state

Description:
--------------------
When I test s4 in a loop , the machine will resume with call trace and the
network disconnect, and sometimes it will also hang at the same time. It may
happen at the 5 or 6 round of the loop ,or more like 24 round . I add the
picture of the call trace in the attachment.

Reproduce step:
----------------------
1.boot up machine 
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 on the CC list 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/20131105/ca5a4921/attachment.html>


More information about the intel-gfx-bugs mailing list