Messages in this thread | | | Date | Thu, 27 Jul 2017 22:13:18 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: Suspend-resume failure on Intel Eagle Lake Core2Duo |
| |
On Thu, 27 Jul 2017, Thomas Gleixner wrote: > On Thu, 27 Jul 2017, Tomi Sarvela wrote: > > > On 27/07/17 10:42, Thomas Gleixner wrote: > > > On Thu, 27 Jul 2017, Tomi Sarvela wrote: > > > > On 26/07/17 17:26, Thomas Gleixner wrote: > > > > > So reverting that commit does not help. Does it help on your machine? > > > > > > > > Yes. Reverting it does not cause the machine to lock up on resume. > > > > > > > > I haven't tested if the machine locks up later on, but at least it > > > > survives > > > > couple of s/r cycles. > > > > > > Can you please try to add 'nohpet' to the kernel command line? > > > > Option nohpet didn't change anything, still hangs on s/r. > > Ok. Was a shot in the dark. I tried on a similar machine, but that one > resumes fine (except that the AHCI controller plays silly buggers, but > nothing interrupt related). I might have access to another core2duo machine > tomorrow. > > I'll send you a debug patch shortly, but can you please first check when > the wreckage happens by testing the states in > > /sys/power/pm_test > > freezer > devices > platform > processors > core
Actually for suspend to ram we only have
freezer, devices, platform
I assume it's platform because that is where the actual interrupt suspend/resume happens.
If that survives, then it's the low level architecture s/r code which fiddles with the interrupt controllers and leaves them in a state which is not known to the core code.
Thanks,
tglx
| |