Re: 2.6.14-rc4-mm1 dead in early boot

[Michael Neuffer <neuffer@neuffer.info>]

Quoting Andrew Morton (akpm@osdl.org):
> Helge Hafting <helgehaf@aitel.hist.no> wrote:
> >
> > On Mon, Oct 17, 2005 at 02:09:06PM -0700, Andrew Morton wrote:
> >  > Helge Hafting <helgehaf@aitel.hist.no> wrote:
> >  > >
> >  > > This one gets me a penguin on the framebuffer, and then dies
> >  > > with no further textual output.  
> >  > > numlock leds were working, and I could reboot with sysrq.
> >  > 
> >  > Can we get anything useful out of sysrq-p and sysrq-t?
> >  > 
> >  > Also, adding initcall_debug to the boot command line might help.
> >  > 
> >  Tried again without the framebuffer.  Still hanging, but more info:
> > 
> >  Last messages before getting stuck:
> >  md autorun DONE
> >  kjournald starting
> >  Ext3-fs mounted fs w. ordered data mode
> >  VFS mounted root (ext3) read-only
> >  freeing unused kernel memory 216k freed.
> >  warning-unable to open an initial console
> >  kernel panic-not syncing:No init found. Try passing init= option to kernel
> > 
> > 
> >  Somewhat silly. There certainly was a console (vgacon) or I wouldn't
> >  be able to read the messages.  And if it mounted root, then there certainly
> >  was an init to run also.
> 
> Can you send the .config please?

I see the same effect, with the only difference
that I don't get the kernel panic line.
For me it gets stuck after the "warning-unable to open an initial console"

I'll send you the .config in a seperate mail.

Cheers
   Mike