linux-kernel - Re: 2.6.29 git, resume from ram broken on thinkpad

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: <200904020023.58363.rjw@sisk.pl>
Date:	Thu, 2 Apr 2009 00:23:57 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Arkadiusz Miskiewicz <a.miskiewicz@...il.com>,
	linux-kernel@...r.kernel.org, Mike Travis <travis@....com>,
	Jeremy Fitzhardinge <jeremy@...source.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad

On Thursday 02 April 2009, Chris Wright wrote:
> * Rafael J. Wysocki (rjw@...k.pl) wrote:
> > On Wednesday 01 April 2009, Chris Wright wrote:
> > > * Rafael J. Wysocki (rjw@...k.pl) wrote:
> > > > This may be caused by the recent PM changes.  Can you please test if commit
> > > > 8efb8c76fcdccf5050c0ea059dac392789baaff2 is fine?
> > > 
> > > I just tested on my t400, it's not[1].  See same symptoms as Arkadiusz.
> > > Seems as if it responds to initial apci event, I see some disk activity,
> > > then nothing (as if it tried to wakeup, then went back to sleep).
> > > 
> > > [1] 15f7176eb1cccec0a332541285ee752b935c1c85 bad
> > >     fae3e7fba4c664b3a15f2cf15ac439e8d754afc2 good(ish) (display stays blank)
> > 
> > Hmm, can you also test commit 0a0c5168df270a50e3518e4f12bddb31f8f5f38f, please?
> 
> Well, that's already included in 15f7176eb1cccec0a332541285ee752b935c1c85

Sorry for the misunderstanding, I thought the breakage might be introduced
between 15f7176eb1cccec0a332541285ee752b935c1c85 and
0a0c5168df270a50e3518e4f12bddb31f8f5f38f, so I thought it would be a good
idea to verify if 0a0c5168df270a50e3518e4f12bddb31f8f5f38f fails too.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/