linux-kernel - Re: v2.6.23-rc2 locks up during boot (without acpi=off)

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] [day] [month] [year] [list]

Date:	Sun, 12 Aug 2007 23:48:12 +0300 (EEST)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	LKML <linux-kernel@...r.kernel.org>, linux-acpi@...r.kernel.org,
	john stultz <johnstul@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	Len Brown <len.brown@...el.com>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Subject: Re: v2.6.23-rc2 locks up during boot (without acpi=off)

On Sun, 12 Aug 2007, Andrew Morton wrote:

> On Sun, 12 Aug 2007 20:15:51 +0300 (EEST) "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi> wrote:
> 
> > Hmm, it was really worth of it, I did:
> > $ git-fetch linus
> > $ git-reset --hard linus
> > [...make & install & boot...]
> > 
> > ...and voila, the problem went away, so something else seems to have
> > fixed it between: ac07860264bd and 963c6527e0a0e. As you can notice,
> > I didn't even have to revert it (I was just double checking current
> > mainline first).
> > 
> > Is there a need to get a more detailed view about the cause or something, 
> > or are details of this issue clear enough to everyone? I can do some more 
> > research if necessary, though expect a bit longer latencies during the 
> > next week...
> > 
> > In case none, thanks everyone, this issue seems solved. :-)
> 
> We just had an acpi commit.  Something like ed3110efb538d7acbf635095c1382118f7414f75
> might have fixed this.

...Yeah, it's very likely the same issue as bisect in that case seemed to 
end up to the very same commit I found, and it was answered with that 
fix...

-- 
 i.