linux-kernel - Re: CONFIG_NUMA breaks hibernation on x86-32 with PAE

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 10 Nov 2008 09:27:49 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	kernel list <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: CONFIG_NUMA breaks hibernation on x86-32 with PAE

On Mon 2008-11-10 17:24:07, KAMEZAWA Hiroyuki wrote:
> On Mon, 10 Nov 2008 08:55:29 +0100
> Pavel Machek <pavel@...e.cz> wrote:
> 
> > > 
> > > * Pavel Machek <pavel@...e.cz> wrote:
> > > 
> > > > ...at least on 2.6.27 and 2.6.28-rc3. Resume gets to 
> > > > acpi_hibernation_leave, then SLAB corruption is detected and machine 
> > > > ends in series of oops.
> > > > 
> > > > Any ideas how to debug that?
> > > 
> > > do you get any serial log or USB key output, so that it's debuggable 
> > > directly?
> > 
> > Well, I can transcribe the BUG() from a picture, I guess, but it does
> > not seem to contain much useful info: SLAB corruption was detected and
> > backtrace is not quite important at that point...
> > 
> > Serial console is probably possible, but would take few days to setup.
> 
> How about this patch ?
> ==
> http://marc.info/?l=linux-mm-commits&m=122624388629106&w=2
> ==

Yep, that one is neccessary to get that far... yes, I have it applied.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/