I have recompiled kernel 2.2.14 and now i can't boot!
Message kernel panic try...
init=/bin/bash don't work.
Have you selected the correct root=/dev/whatever?Quote:>Hi,
>I have recompiled kernel 2.2.14 and now i can't boot!
>Message kernel panic try...
>init=/bin/bash don't work.
Are you sure you compiled in support for the ext2 filesystem and
the correct (IDE/SCSI) controllers?
"If you can't win on the scoreboard, hit them with your fists."
--Mike, on the penguins losing to the islanders
> I have recompiled kernel 2.2.14 and now i can't boot!
> Message kernel panic try...
> init=/bin/bash don't work.
> Bonjour Thomas,
> Yes i did and i have also try 'make bzlilo'...nothing.
> hello all,
> I have a kernel panic at boot process,
> within 2 hd, the first dedicated to w98, the second one for linux,
> it seems that w98 crashed the tiny partition to boot and acces to the
> other hd,
****************** __ _
/ Marcel Pol / / / (_)__ __ ____ __
/ / / /__/ / _ \/ // /\ \/ /
SuSE 6.3 Kernel 2.2.13
Don't visit http://www.angelfire.com/scifi/marcelpol
This sig is stolen.
But it was released under GNU, wasn't it?
Anyone know why a kernel panic would not cause a reboot even though /proc/sys/kernel/panic is set to "1"?
This morning I had the following message on the console of a 2.2.14 box that had been sitting idle overnight:
When I pressed ENTER, I found that bash was still responding, though when I tried to run "top" everything froze until I pulled the plug on the box:
drwxr-x--- 2 root root 1024 Nov 7 23:56 .
drwxr-xr-x 13 root root 1024 Nov 7 19:56 ..
-rw------- 1 root root 5 Nov 7 23:56 test.txt
Kernel panic: Free list corrupted
1) Anyone know why the kernel panic didn't cause a reboot?
2) Or maybe why something like this would even happen?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
8. twm question