LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   kernel panic - not syncing: attempted to kill init! (https://www.linuxquestions.org/questions/fedora-35/kernel-panic-not-syncing-attempted-to-kill-init-528768/)

asif2k 02-13-2007 03:44 PM

kernel panic - not syncing: attempted to kill init!
 
I have been running fc2 server on my box. I tried upgrading to fc3, fc4, fc5 server. I was able to upgrade to fc5 server. Finally, I decided to give a shot at it. Now, I get an error when it boots up. I have backed up all my data already. Anyone can help me find a solution if possible. Your help is appreciated.

Quote:

kernel panic - not syncing: attempted to kill init!

thanks in advance :D

wmakowski 02-13-2007 10:03 PM

The kernel panic message is not enough to determine what is causing the problem. Usually there are messages leading up to the panic message that give a clue about what is going on. Sometimes it has to do with incorrect mount information for your root or boot devices. Post more details when you can and perhaps we can figure out what is happening.

Bill

asif2k 02-13-2007 11:36 PM

Quote:

root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/ rhgb quite
linux-bzimage, setup=0x1e00, size=0x16eb71,
initrd /initrd-2.6.15-1.2054_FC5.img
linux-initrd @ 0x17eff000, 0xe0baa bytes,

Uncompressing linux... OK, booting the kernel
agpgart: Unsupported SiS chipset (device id: 5600)
Red Hat nash version 5.0.32 starting
Kernel panic - not syncing: Attempted to kill init!
This is all i see on my monitor screen when it boots up and it halts.

thanx :)

wmakowski 02-14-2007 08:44 AM

I saw a few posts about agpgart: Unsupported SiS Chipset using google. Some those suggested adding agp_try_unsupported=1 to the kernel line in grub.conf. You would enter that right after root=LABEL=/.

However, I'm not certain that is the main culprit of the kernel panic. I would boot again, but remove rhgb and quiet from the kernel line so you can get more information on what the kernel is doing before the panic.

You can temporarily edit the kernel boot command through grub when grub first comes up. Hopefully either the addition of agp_try_unsupported or getting more info will lead to a solution.

Bill


All times are GMT -5. The time now is 12:12 AM.