Recently, Somebody Somewhere wrote these words
> So, I recently built (and rebuilt) svn-20060220. Both times resulted in
> the same kernel panic. Any tips as to how to interpret the panic so as
> to point to a specific cause would be much appreciated.
>
>
> I can't see all of the data from the panic, because it scrolls of the
> screen. Basically, I see the tail end of a column of hex numbers, then
> some other data, as follows:
>
> [<00000000>]
> Code: 57 56 53 83 ec 2c 8b 44 24 44 85 c0 0f 88 e5 04 00 00 8b 74 24 40
> 8b 44 24 44 8d 6c 06 ff 89 f0 83 e8 01 39 e8 77 43 8b 4c 24 48 <80> 39
> 00 74 25 0f b6 01 3c 25 74 42 39 ee 77 06 8b 4c 24
> <0>Kernel panic - not syncing: Attempted to kill init!
Not enough there for us.
Mount the disk and go through the logs. Get into /var/log and find
the first error in the boot, which usually is the issue. ideally
use a distro kernel, made to be as adaptable as possible.
Another useful thing is to set up another kernel and modules in grub.
You may have to copy over /lib/modules/something as well, and boot on a
known good kernel & modules, then hunt for errors.
Your hardware may not be coming up correctly. I'd be looking for
your mobo chipset driver(s) and video driver(s) compiled in, and
other drivers not compiled in.
--
With best Regards,
Declan Moriarty.
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
