LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Closed Thread
 
LinkBack Search this Thread
Old 08-16-2005, 02:27 PM   #1
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,063

Rep: Reputation: 974Reputation: 974Reputation: 974Reputation: 974Reputation: 974Reputation: 974Reputation: 974Reputation: 974
Explained: "kernel panic - not syncing - attempted to kill init"


When the kernel gets into a situation where it does not know how to proceed (most often during booting, but at other times), it issues a kernel panic by calling the panic(msg) routine defined in kernel/panic.c. (Good name, huh?) This is a call from which No One Ever Returns.

The panic() routine adds text to the front of the message, telling you more about what the system was actually doing when the panic occurred ... basically how big and bad the trail of debris in the filesystem is likely to be. This is where the "not syncing" part comes from, and when you see that, it's good. (panic() does try to issue a sinc() system-call to push all buffered data out to the hard-disks before it goes down.)

The second part of the message is what was provided by the original call to panic(). For example, we find panic("Tried to kill init!") in kernel/exit.c.

So, what does this actually mean? Well, in this case it really doesn't mean that someone tried to kill the magical init process (process #1...), but simply that it tried to die. This process is not allowed to die or to be killed.

When you see this message, it's almost always at boot-time, and the real messages ... the cause of the actual failure ... will be found in the startup messages immediately preceding this one. This is often the case with kernel-panics. init encountered something "really bad," and it didn't know what to do, so it died, so the kernel died too.

BTW, the kernel-panic code is rather cute. It can blink lights and beep the system-speaker in Morse code. It can reboot the system automagically. Obviously the people who wrote this stuff encountered it a lot...

In diagnosing, or at least understanding, kernel-panics, I find it extremely helpful to have on-hand a copy of the Linux source-code, which is usually stored someplace like /usr/src/linux-2.x. You can use the grep utility to locate the actual code which caused the panic to occur.

Last edited by sundialsvcs; 08-16-2005 at 02:28 PM.
 
Old 08-16-2005, 02:36 PM   #2
tuxdev
Senior Member
 
Registered: Jul 2005
Distribution: Slackware
Posts: 2,008

Rep: Reputation: 110Reputation: 110
what about when init dies normally("halt")?
 
Old 11-30-2006, 11:16 AM   #3
John Sharp
LQ Newbie
 
Registered: Nov 2006
Posts: 1

Rep: Reputation: 0
Kernel panic message

I have this very message on my red hat Fedora system while trying to boot after installing a new cpu fan and necessarily disconnecting and reconnecting the several components to the board, which had to come out due to mounting screws UNDER the board. I have reset the date and time and I suspect some other item(s) need to be set correctly so boot can continue, but I don't knkow which ones. Can anyone instruct me? Here is the last page of messages seen while booting, and I don't know how to retrieve any that scrolled by before these came:

…………..other stuff I can’t see off the screen)

Buffer I/O error on device hdb, logical block 2
Buffer I/O error on device hdb, logical block 3
Buffer I/O error on device hdb, logical block 4
Buffer I/O error on device hdb, logical block 5
Buffer I/O error on device hdb, logical block 6
Buffer I/O error on device hdb, logical block 7
Buffer I/O error on device hdb, logical block 8
Buffer I/O error on device hdb, logical block 9
/dev/hdb: read failed after 0 of 2048 at 0: Input/output error
/dev/hdb: read failed after 0 of 2048 at 528023552: Input/output error
/dev/hdb: read failed after 0 of 2048 at 0: Input/output error
No volume groups found
/dev/hdb: read failed after 0 of 2048 at 0: Input/output error
/dev/hdb: read failed after 0 of 2048 at 0: Input/output error
/dev/hdb: read failed after 0 of 2048 at 528023552: Input/output error
/dev/hdb: read failed after 0 of 2048 at 0: Input/output error
Unable to find volume group “VolGroup00”
Unable to access resume device (/dev/VolGroup00/LogVol01)
Mount: error No such device or address mounting /dev/root on /sysroot as ext3
Setuproot: moving /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
Switchroot: mount failed: No such file or directory
Kernel panic – not syncing: Attempted to kill init!

(and that’s all she wrote -- it freezes at that point)











Quote:
Originally Posted by sundialsvcs
When the kernel gets into a situation where it does not know how to proceed (most often during booting, but at other times), it issues a kernel panic by calling the panic(msg) routine defined in kernel/panic.c. (Good name, huh?) This is a call from which No One Ever Returns.

The panic() routine adds text to the front of the message, telling you more about what the system was actually doing when the panic occurred ... basically how big and bad the trail of debris in the filesystem is likely to be. This is where the "not syncing" part comes from, and when you see that, it's good. (panic() does try to issue a sinc() system-call to push all buffered data out to the hard-disks before it goes down.)

The second part of the message is what was provided by the original call to panic(). For example, we find panic("Tried to kill init!") in kernel/exit.c.

So, what does this actually mean? Well, in this case it really doesn't mean that someone tried to kill the magical init process (process #1...), but simply that it tried to die. This process is not allowed to die or to be killed.

When you see this message, it's almost always at boot-time, and the real messages ... the cause of the actual failure ... will be found in the startup messages immediately preceding this one. This is often the case with kernel-panics. init encountered something "really bad," and it didn't know what to do, so it died, so the kernel died too.

BTW, the kernel-panic code is rather cute. It can blink lights and beep the system-speaker in Morse code. It can reboot the system automagically. Obviously the people who wrote this stuff encountered it a lot...

In diagnosing, or at least understanding, kernel-panics, I find it extremely helpful to have on-hand a copy of the Linux source-code, which is usually stored someplace like /usr/src/linux-2.x. You can use the grep utility to locate the actual code which caused the panic to occur.
 
Old 11-30-2006, 11:52 AM   #4
matthewg42
Senior Member
 
Registered: Oct 2003
Location: UK
Distribution: Kubuntu 12.10 (using awesome wm though)
Posts: 3,530

Rep: Reputation: 62
This is a fairly un-educated guess on my part, but for what it's worth... looks like your IDE controller is freaking out, or the drive is corrupted. Could be that screw under the board shorted something out.
 
Old 11-30-2006, 01:05 PM   #5
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,469

Rep: Reputation: 64
Yea probably shortted out the io controller.
 
Old 01-07-2007, 10:36 PM   #6
Yull29m
Member
 
Registered: Feb 2005
Distribution: linux mandrake 10.0
Posts: 40

Rep: Reputation: 15
I am having the same problem as sundialsvcs and John Sharp. If in fact it did short something, how would I figure that out or remedy it? At the lowest cost possible pls? I am not very well to do money wise. I make under 17,000 a year, and have a family to support as well as tons of bills. Free stuff rox, I love linux
 
Old 03-26-2007, 08:10 PM   #7
rocketman8541
LQ Newbie
 
Registered: Jul 2005
Location: Connecticut
Distribution: FC 3 on desktop FC5 on lappy, rHELL 2.4.9 at the grind
Posts: 3

Rep: Reputation: 0
Cheers for that explanation sundial
 
Old 04-22-2007, 02:02 AM   #8
mr805newbie
Member
 
Registered: Aug 2004
Posts: 78

Rep: Reputation: 15
Quote:
Originally Posted by matthewg42
This is a fairly un-educated guess on my part, but for what it's worth... looks like your IDE controller is freaking out, or the drive is corrupted. Could be that screw under the board shorted something out.

What if my machine boots fine in Windows XP? The Mandriva 2007 partition is the only boot that gives this problem....
 
Old 05-09-2007, 11:23 AM   #9
lordofthechia
LQ Newbie
 
Registered: Jul 2005
Posts: 3

Rep: Reputation: 0
Quote:
Originally Posted by mr805newbie
What if my machine boots fine in Windows XP? The Mandriva 2007 partition is the only boot that gives this problem....
I just experienced this same issue w/ a machine I was working on. The problem stemmed from the HDD being reconnected to the motherboard on a different IDE channel than it was originally set up on. So the bootloader was indicating that root should be at hda1 but in fact it was at hdc1.

Moving the HDD to the correct IDE channel (channel 1) fixed it.
 
Old 05-12-2007, 02:57 AM   #10
mr805newbie
Member
 
Registered: Aug 2004
Posts: 78

Rep: Reputation: 15
I have a motherboard that only has 1 IDE connector. I thought it was strange but I have the HDD and the CDROm both on the same IDE. I play around with the jumpers on the hard drive and see what happens.
 
Old 06-13-2007, 07:52 AM   #11
doronb2
LQ Newbie
 
Registered: Jun 2007
Posts: 7

Rep: Reputation: 0
i get the kernel panic: attempted to kiil init" messege when i boot from cd (i want to install kubuntu.. i haven't linux yet).

What can I do??

Last edited by doronb2; 06-13-2007 at 07:53 AM.
 
Old 07-31-2007, 01:06 AM   #12
kashifkamyana
LQ Newbie
 
Registered: Jul 2007
Posts: 6

Rep: Reputation: 0
on Redhat Linux AS 4 this message appear

hdd: no disk in drive
/bin/sh: no such file or direcotry

kernel panic not syncing attempting to kill init

Please guide
 
Old 08-04-2007, 12:45 AM   #13
mr805newbie
Member
 
Registered: Aug 2004
Posts: 78

Rep: Reputation: 15
Quote:
Originally Posted by lordofthechia
I just experienced this same issue w/ a machine I was working on. The problem stemmed from the HDD being reconnected to the motherboard on a different IDE channel than it was originally set up on. So the bootloader was indicating that root should be at hda1 but in fact it was at hdc1.

Moving the HDD to the correct IDE channel (channel 1) fixed it.

My motherboard only has 1 IDE channel. I added a PCI /IDE card and I'm still freezing at the Kernel Panic! prompt. How can I edit where Mandriva looks for boot files?
 
Old 08-04-2007, 12:49 AM   #14
mr805newbie
Member
 
Registered: Aug 2004
Posts: 78

Rep: Reputation: 15
Quote:
Originally Posted by exvor
Yea probably shortted out the io controller.
If the I/O controller was shorted then Windows XP would not boot neither. This seems to be isolated to Mandriva. Some system boot file is looking in the wrong places for the appropriate environment variables and paths.
 
Old 08-06-2007, 04:22 PM   #15
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,469

Rep: Reputation: 64
Yeah I realized that later in this conversation. This error occurs for several diffrent reasons tho so its hard to pin down what exactly is causing it.


As for your error you should look at what messages you get before you get this one and see if you can figure out what is going on. From a guess I would say that the driver to load your pci controller is not being loaded before the system attempts to read the harddrive.

but thats only a guess.
 
1 members found this post helpful.
  


Closed Thread


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic - not syncing: Attempted to kill init! potsilui Linux - Kernel 28 05-09-2012 11:46 AM
Kernel Panic - Not Syncing: Attempted To Kill Init! tegralens Linux - Software 13 06-23-2008 03:15 PM
kernel panic - not syncing: Attempted to kill init! k5knt Linux - General 39 07-18-2007 12:47 AM
Updated = Kernel panic - not syncing: Attempted to kill init! potsilui Fedora 4 04-18-2005 03:02 PM
Fedora Core 2 Install "attempted to kill init" kernel panic STuPiDiCuS Fedora - Installation 1 06-21-2004 03:41 PM


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

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration