| Summary: | [HSW ULT] Loop to test S4, system will call trace and network disconnect | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Qingshuai Tian <qingshuai.tian> | ||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Status: | CLOSED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | intel-gfx-bugs, przanoni | ||||||
| Version: | unspecified | ||||||||
| Hardware: | Other | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Qingshuai Tian
2013-11-05 01:10:45 UTC
(In reply to comment #0) > Created attachment 88658 [details] > Image of Call trace > > Environment: > ------------------- > Kernel: (drm-intel-next-queued)9d1cb9147dbe45f6e94dc796518ecf67cb64b359 > Author: Paulo Zanoni <paulo.r.zanoni@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 Can you please try to reproduce with a 30 second delay. In strange cases, I've seen 10s not be enough. Hi Is this a recent regression or is it something that did not get fixed by Ben's recent patch? If it's a recent regression, can we bisect it? Thanks, Paulo Created attachment 88806 [details]
Image of Call trace with i915.modeset=0
This machine is a new ultrabook and has been just added into testing this time.
Machin Info: Lenovo idealpad u330p
BIOS Version: 7CCN15WW
CPU: Intel(R) Core(TM) i3-4010U CPU @1.70GHZ
When I looped testing s4 with the "i915.modeset=0" module parameter setted, the machine will still call trace and hang at round 21 of the loop.
Sorry I didn't make it clear before.
Thanks
Qingshuai
(In reply to comment #3) > Created attachment 88806 [details] > Image of Call trace with i915.modeset=0 > > This machine is a new ultrabook and has been just added into testing this > time. > Machin Info: Lenovo idealpad u330p > BIOS Version: 7CCN15WW > CPU: Intel(R) Core(TM) i3-4010U CPU @1.70GHZ > > When I looped testing s4 with the "i915.modeset=0" module parameter setted, > the machine will still call trace and hang at round 21 of the loop. > > Sorry I didn't make it clear before. > > Thanks > Qingshuai Looks like this is someone else's bug then. Do we have the resources to try to investigate which driver is causing the corruption? My first strategy would be to blacklist some modules, try to reproduce, blacklist others, try again and see if it helps. Perhaps we should report this at bugzilla.kernel.org? Agree this should be reported to kernel.org. I have reported the bug on bugzilla.kernel.org. https://bugzilla.kernel.org/show_bug.cgi?id=66311 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.