Kernel panic - not syncing: Attempted to kill init!
I've seen other threads reporting issues with kernel panics, but in an effort not to offend anyone, I will not "hijack" them with my own problem.
I've researched high and low for a solution the the "kernel panic" issue that I have encountered with kernel 2.6.20.1, but I have found nothing relevant. Some developers purport that the issue may lie with how the kernel file systems are configured, whether as a module or built-in. Well here's a snippet of my kernel configuration: Code:
# Code:
# Used only when booting from CD-ROM Code:
default 0 Also would it be too much to ask the Linux source developers to insert a better kernel panic error message that contained an error code or some useful information? |
Can you post the detailed output of the kernel panic error message.
|
Kernel panic: sync failed - attempted to kill init.
|
You need to post a bit more output than that. You need to post a few lines before and after the message so that others can try to deduce whats causing the kernel panic.
|
My apologies if I was not clear in my OP. This is what I initially see:
$ Yep, that's the shell prompt. Then after typing at the shell prompt this command: $ exit I see the following: Kernel panic - sync failed: attempted to kill init There are no other error messages. The system boots fine. I suspect that it is because I am exiting the one and only shell running on the system that the kernel panic occurs. There is nothing for the system to fall back onto (i.e. there is no getty running on any tty, much less the console). Can you please confirm if this is a valid assessment? P.S. I did find a work-around. I run the following script in lieu of /bin/ash (the script name is specified in the Grub init= statement): Code:
#!/bin/sh |
Kernel panic - not syncing: Attemted to kill init!
I have the same problem. Had winXP installed, and it died. Not able to reinstall, I thougt i might try Isolinux 3.11 Ubuntu (Debian dated march 03 2007, H. Peter Anvin) and when I try to boot from the CD I get the
Kernel panic - not syncing: Attemted to kill init! message not able to make screenshot, but i wrote down what the screen said.. 82.484224 Call Trace: 82.484290 <c0188207> d_alloc+0x107/0x190 82.484364 <c017ee8d> __lookup_hach+0xbd/0x100 82.484450 <c017f399> lookup_one_len_nd+0x89/0x90 82.484534 <c01b8106> create_dir+0x46/0x1e0 82.484616 <c01b89dc> sysfs_create_dir+0x2c/0x70 82.484698 <c01ed94a> kobject_add+0x8a/0x1a0 ... <c01edb7f> subsystem_register+0xf/0x30 ... <c03ea621> param_sysfs_init+0x11/0x1e0 ... <c01b7924> sysfs_add_file+0x mca_init c0100511 init+0x111/0x300 ret_from_fork c0100400 init+0x0/0x330 (this line appears twice) c01044c7 kernel_thread_helper+0x7/0x10 ======================== code: 83 ed 04 8b 45 04 0f 18 00 90 8d 45 04 39 d8 0f 84 bc 00 00 00 f6 45 18 2c 74 e2 89 e8 e8 4b ea ff ff 89 c6 8b 44 24 10 8b 78 24 <ac> ae 75 00 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 75 be 8b EIP: <c01b83de> sysfs_lookup+0x5e/0x200 SS:ESP 0068:df905e94 <0>Kernel Panic - not syncing: Attempted to kill init! I believe this may be caused by a logical or physical disk error.. or a problem with the motherboard or BIOS.. The computer shuts down after aprox 1 minute, so it took me about 10 restarts to write the above.. That's allso why some lines are a bit short... besides the 82.nnnnnn numbers changed, propably because I tried to use different languages to see if it helped. The rest of the lines remained the same, so I guess that part of the lines ar not of interrest.. |
Quote:
What I don’t understand is why you are killing init (when I say init, I mean whatever process runs with PID 1 and PPID 0). I mean, what did you expect to happen? If you are done with a session, why not just halt or reboot? Or perhaps, you want a minimal init? |
Osor -
Thanks for confirming what I surmised. I tried the 'halt' command for grins. With BusyBox 1.1.0, the only option this command allows is for one to specify a delay (in seconds) before the system is supposedly halted. I got the following "error": Code:
halt: no process killed Thank you for your comments. |
Quote:
I get the Kernel Panic with Ubuntu 7.04... I'm going to try the Western Digital Diagnostic utility. I will try to write zeroes to my HDD, and then try to install Linux again, and pray that it works. Otherwise, I'll have to put a new HDD in it, I guess. I just hope there's no motherboard or bios issues... |
You probably have an uncommon setup. Installers for distros like Ubuntu I'd imagine handle a certain number of default cases, but can't be prepared for everything. First I'd try to get a booting kernel. You might have to build one, if you're using uncommon hardware/devices. Get a kernel booting from something like a floppy, then use a boot/root disk combo to start building a system. Wipe the partition table, make new partitions. Verify those took. Make some filesystems, copy your kernel and start loading programs. Linux is really able to run on alot of things, getting it setup right is the tricky part.
|
I am having the same problem as Ungdomspastorn. I have tried lots of distributions (Ubuntu, Kubuntu, Fedora, Gentoo, and some others) all on live CD's and none of them have worked. Im wondering if this could be because my computer is an HP, and not one I built myself.
|
I am also getting this error after building and installing a new kernel under Debian 4.0 'Etch' on a SuperServer box. Not using anything like BusyBox, etc. Just the plain Jane linux kernel.
|
worked for me
I simply added the selinux=0 parameter at boot. (Thats a zero.) Worked perfectly. Let me know how it works for you.
Tim |
Kernel panic - not syncing: Attemted to kill init! message
My problem is exactly like this problem but I have tried everything possible and not getting results. There must be someone here who can walk a beginner thru the steps to solving this error. Please help.
Quote:
|
All times are GMT -5. The time now is 03:54 AM. |