fc2 kernel panic

[Ted Kaczmarek]

On Mon, 2004-05-24 at 11:15 -0400, Robert P. J. Day wrote:
> On Mon, 24 May 2004, Ted Kaczmarek wrote:
> 
> > On Mon, 2004-05-24 at 06:52 -0400, Thomas Molina wrote:
> > > > root at inyoureyes boot]# ls -latr initrd-2.*
> > > > -rw-rw-r--  1 root root 276009 Aug 20  2003 initrd-2.4.20-20.9.img
> > > > This one post yum upgrade.
> > > > -rw-r--r--  1 root root 195900 May 23 18:28initrd-2.6.5-1.358smp.img.old
> > > > This one I created "mkinitrd 2.6.5-1.358"
> > > > -rw-r--r--  1 root root 194628 May 23 18:34 initrd-2.6.5-1.358smp.img
> > > > And Arjans latest test kernel.
> > > > -rw-r--r--  1 root root 195429 May 23 19:13 initrd-2.6.6-1.376smp.img
> > > > 
> > > > 
> > > > mkrootdev: label / not found
> > > > mount: error 2 mounting ext3
> > > > pivotroot: pivot_root(/sysroot/initrd) failed: 2
> > > > umount /initrd/proc failed: 2
> > > > Freeing unused kernel memory: 188k freed
> > > > Kernel panic: No init found. Try passing init=option to kernel
> 
> this is one of the banes of my current existence -- people claiming
> "kernel panic" when it's just a missing/broken init.
> 
> i know it sounds pedantic, but i'm working on a project that involves
> messing considerably with the init structure (replacing it with minit,
> actually, so it's not unexpected to mess that up and get a broken init
> and get that kind of error message.)
> 
> given that i'm looking after the kernel, i freak out just a little when
> someone comes running up, saying, "i just got a kernel panic!".  then i 
> see that it's a boot-time init problem, and i calm down.
> 
> so, might it be possible to be a bit more precise in the subject lines 
> than the generic, catch-all "fc2 kernel panic"?  
> 
> rday
I apologize for the lack of detail in my subject, but I thought I made
it crystal clear in the body. 

 Us less experienced users depend on feedback from people just like you,
whether it be good or bad.

I would love to learn more about your minit project, so please do keep
us posted :-)

Sorry for any trouble my poor subject matter might have caused you.

Regards,
Ted