Created attachment 112902 [details] call trace System Environment: -------------------------- Regression: good commit: cd52471999ef08bca35568525c1d85d883ffedb6 Platform: BDW-Y Kernel: -------------------------- -nightly latest 9438dec1c7538fdd3b356a59ca929632fcb57132 Bug detailed description: ----------------------------- I have tried S3 on BDW-Y with the night-latest kernel. And the first S3 can work normally.The second and third times, it has write error: Resource temporarily unavailable. If any more ,it will call trace and can’t S3 any more. Since the machine doesn't have any serial port or built-in network card, we can't catch the dmesg. And the call trace message seen as the attached picture. Steps: --------------------------- echo mem>/sys/power/state for several times.
Without i915 module, blank screen problem occurs after s3 resume , but the system is alive. If I load i915 module, the system will hang after second s3 operation.
This issue also exists on BSW with BIOS V55 and -testing 2015_01_30 commit 4d3645e40c7039f60b6db0ce9c2251ac34faef81 : System will hang after S3 several times.
I reported BSW system hang issue as a new bug 89005.
(In reply to Jeff Zheng from comment #3) > I reported BSW system hang issue as a new bug 89005. Looks like an SCSI issue. Could you still try if you can reproduce the issue booting with the i915.modeset=0 kernel parameter?
Created attachment 113851 [details] Works with 10 S3 I tried S3 10 times on 2015_02_27 drm-intel-nightly commit 376ebc108c774b357e211b5fc0aab558fc89ede9, and didn't reproduce this issue. Attached is the dmesg log.
let's close it as we can't reproduce it.
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.