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  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]
Date:	Mon, 31 Dec 2007 10:06:58 -0500
From:	Vivek Goyal <>
To:	Dhaval Giani <>
Cc:, lkml <>,
Subject: Re: kexec refuses to boot latest -mm

On Sat, Dec 29, 2007 at 11:11:13AM +0530, Dhaval Giani wrote:
> On Fri, Dec 28, 2007 at 09:27:39AM -0500, Vivek Goyal wrote:
> > On Fri, Dec 28, 2007 at 06:15:32PM +0530, Dhaval Giani wrote:
> > > Hi Vivek,
> > > 
> > > I can't seem to get the latest -mm (2.6.24-rc6-mm1) to boot with
> > > kexec. It just gets stuck at "Starting new kernel".
> > > 
> > > It does boot normally when booted as the first kernel.
> > > 
> > > Any hints debugging? (x86 architecture)
> > 
> > I generally try few things.
> > 
> > - Specify earlyprintk= parameter for second kernel and see if control
> >   is reaching to second kernel.
> > 
> > - Otherwise specify --console-serial parameter on "kexec -l" commandline
> >   and it should display a message "I am in purgatory" on serial console.
> >   This will just mean that control has reached at least till purgatory.
> > 
> Ok, so it reaches till here. I get "I'm in purgatory" on the console.

Ok. So it atleast reaches till purgatory. My hunch is that it also reaches
the second kernel but dies early in that kernel before any message can
be printed on screen.

Can you put some "outb()" messages on serial console in start_kernel() in
second kernel and see up to what point do you reach.

My 2.6.24-rc6-mm1 kernel panics during boot on 32bit box. Let me try it on
64 bit box.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists