Created attachment 81617 [details] dmesg: S4 cause call trace sporadically Environment: ------------------------- Acer Haswell Notebook Aspire V3 772G 17.3 ; Host bridge ID=0x0c04 (rev 06); VGA ID=0x0416 (rev06); CPU: i7-4702MQ 2.2GHz; BIOS:v1.04 MEM: 4G ; Kernel: (drm-intel-next-queued)9199918a1e148c18e3519cb7b2d90a127d7ea87b Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Thu Jun 27 17:52:15 2013 +0200 drm/i915: fix hpd interrupt register locking Description: ------------------------- Running S4 on HSW mobile acer product will cause call trace sporadically, It will reproduced about loop running S4 3 times. The machine is reachable. Remove i915, S4 works well. I also test another MSI HSW mobile product, S4 is good. I list the MSI machine info below: -------- MSI Haswell Notebook MSI MS-16GC Notebook 15.6; Host bridge ID=0x0c04 (rev 06); VGA ID=0x0416 (rev06); CPU: i7-4700MQ 2.4GHz BIOS: E16GCIMS.509 (04/24/2013) EC: 16GCEMS1 ver5.00 (04/12/2013); ME: 9.0.2.1345; reproduce step: ------------------------- 1. boot up machine 2. loop running S4 about 3 times. 3. call trace will come up on screen.
Can you please retest with intel_iommu=igfx_off added to the kernel cmdline?
Created attachment 82353 [details] call trace of S4 with intel_iommu=igfx_off
(In reply to comment #1) > Can you please retest with intel_iommu=igfx_off added to the kernel cmdline? I used (drm-intel-next-queued)c0d6a3dd61d46a640ead0a9d38b78ca22d37a304 kernel with intel_iommu=igfx_off and retested it again, the call trace showed at the fourth time, I attached the dmesg info after system booting in the attachment.
I really think this is a duplicate of #65496.
Yeah, I think it makes sense to first resolve the overall hsw s4 issues. If there's still something left we can reasses the situation. *** This bug has been marked as a duplicate of bug 65496 ***
(In reply to comment #5) > Yeah, I think it makes sense to first resolve the overall hsw s4 issues. If > there's still something left we can reasses the situation. > > *** This bug has been marked as a duplicate of bug 65496 *** The reason I file two bugs to track is: this bug , machine can resume from S4 even though there's call trace in dmesg. Bug 65496: machine will be hang when resume from S4. I compared the dmesg between two machine and it's now the same. If you think these two bugs are really correlated, I verified here. Any questions, please comment.
I think we can (for now at least) throw all haswell s4 issue that lead to backtraces/memory corruptions or early hangs when resuming into the same bug.
(In reply to comment #7) > I think we can (for now at least) throw all haswell s4 issue that lead to > backtraces/memory corruptions or early hangs when resuming into the same bug. Got it.
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.