linux-kernel - Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.1707281514000.1986@nanos>
Date:   Fri, 28 Jul 2017 15:15:10 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Tomi Sarvela <tomi.p.sarvela@...el.com>
cc:     Martin Peres <martin.peres@...ux.intel.com>,
        jeffy.chen@...k-chips.com, linux-kernel@...r.kernel.org
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On Fri, 28 Jul 2017, Thomas Gleixner wrote:
> On Fri, 28 Jul 2017, Tomi Sarvela wrote:
> > On 28/07/17 00:08, Thomas Gleixner wrote:
> > The patch didn't apply cleanly: can you tell exact commit or tag it has been
> > created against?
> 
> Linus head
> 
> > I tried to hand-wrangle the changes in, but then I got compilation
> > errors:
> 
> Sorry, forgot to refresh the patch. Working version below.
> 
> > Also, the usage of /sys/power/pm_test was not intuitive to me. Can you explain
> > which kind of combinations do you want to test?
> 
> # echo freezer >/sys/power/pm_test
> # echo mem >/sys/power/state
> 
> # echo devices >/sys/power/pm_test
> # echo mem >/sys/power/state
> 
> # echo platform >/sys/power/pm_test
> # echo mem >/sys/power/state
> 
> To reset the test stuff do:
> # echo none >/sys/power/pm_test
> 
> Please try that before applying the debug patch.

Another question. Is the machine completely dead or not?

Can you ping it or does the serial console show the start of resume or just
nothing at all?

Thanks,

	tglx