LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices

Reply
 
Search this Thread
Old 01-24-2007, 12:16 PM   #1
Wocky
LQ Newbie
 
Registered: Oct 2004
Location: Australia
Posts: 29

Rep: Reputation: 1
Kernel panic - not syncing: Attempted to kill init!


My old (about 8 years) system disk failed last week, so I was forced to install a new system on a new disk. I went with FC6. The install was clean, though several things (sound, some networking) have stopped working. After installing the new system, I got the latest stable kernel (2.6.19.2) and built it. The build was clean, but installation wasn't; it stopped with the message "/lib/modules/2.6.19.2 - doesn't exist" (it didn't, but the installation process should have created it.) I created it, and the install was successful. Boot failed, with several pages of what appeared to be kernel symbols - it went off the top of the screen so quickly I couldn't tell - and the message "kernel panic - not syncing: Attempted to kill init!"

The original FC6 install (with kernel 2.6.5) still works.

A web search suggested that my initrd might be broken, so I tried rebuilding it, but that made no difference.

The original system (on the dead disk) was RedHat 7.1, though I'd changed almost everything. The system is a dual-processor, 500MHz Celeron, with CD-RW and 5 HDDs.

Any suggestions?

TIA
Wocky
 
Old 01-24-2007, 01:00 PM   #2
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,319

Rep: Reputation: 140Reputation: 140
Is there anything in /lib/modules/2.6.19.2? When you compiled the kernel did you remember to do "make modules" and "make modules_install"? The latter command is what installs the modules to /lib/modules/<kernel version>.
 
Old 01-24-2007, 06:03 PM   #3
Wocky
LQ Newbie
 
Registered: Oct 2004
Location: Australia
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by kilgoretrout
Is there anything in /lib/modules/2.6.19.2? When you compiled the kernel did you remember to do "make modules" and "make modules_install"? The latter command is what installs the modules to /lib/modules/<kernel version>.
Yes, it's fully populated. I should have said. Incidentally, there's no longer (under this kernel version, anyway) a need to do "make modules," though there is still a need to do "make modules_install".

Wocky
 
Old 01-25-2007, 11:42 AM   #4
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,319

Rep: Reputation: 140Reputation: 140
What is your root filesystem(eg ext2, ext3, reiserfs)? I recall people having kernel panic problems with fedora when ext2 or ext3 is compiled as a module instead of being compiled directly in the kernel.
 
Old 01-25-2007, 10:14 PM   #5
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,401

Rep: Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119
Look to the messages preceding this one for the true cause of the error.

This message is simply the last cough before it halts.

"Kernel panic" means the system cannot continue.

"Not syncing" means, good news, it wasn't in the middle of a disk write.

"Attempted to kill init" actually means that the init process ("process #1") died. It isn't allowed to die.

So the message is really telling you that "it died," not why it died. The preceding messages will.
 
Old 01-26-2007, 12:17 PM   #6
Wocky
LQ Newbie
 
Registered: Oct 2004
Location: Australia
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by kilgoretrout
What is your root filesystem(eg ext2, ext3, reiserfs)? I recall people having kernel panic problems with fedora when ext2 or ext3 is compiled as a module instead of being compiled directly in the kernel.
The root fs is ext3, and I made sure that ext3 was compiled-in (not a module.) I learned that lesson the first time I built a kernel.

Quote:
Originally Posted by sundialsvcs
So the message is really telling you that "it died," not why it died. The preceding messages will.
sundialsvcs, as I said in the OP, the preceding data seems to be a dump of kernel symbols; the top of it scrolls off the screen too quickly for me to read. Do you know of a way to save this output for later examination? I've looked in all the places I can think of for a clue as to how to do this, but without success.

Wocky

Last edited by Wocky; 01-26-2007 at 12:18 PM.
 
Old 01-26-2007, 09:25 PM   #7
jayjwa
Member
 
Registered: Jul 2003
Location: NY
Distribution: None (src & compile)
Posts: 253

Rep: Reputation: 36
I have the same error on an old, old system, my #3 system. I've yet to put a working 2.6 linux on it. 2.4 will work, but I dropped support for those a long time ago and can't compile them with GCC 4.1.1 at last I checked. Never tried old 2.6's either, so maybe it is something to do with more recent 2.6 kernels (using 2.6.19.2 now). Trying to find the problem, I compiled the kernel with debugging in various places and the best I can get out of it is that it seems the first error calls do_invalid_op (invalid opcode). I tried to compile a static shell and use that for init, I tried using other's pre-made root disks, etc, nothing seems to work. It's like an invalid machine instruction is hit somewhere, although I did set the correct CPU type, compiler switches and all.

Try compiling the kernel with CONFIG_MAGIC_SYSRQ=y. You should still be able to use that, even if the system locks up. The key is "alt-sysreq-l" ("l" as in "lion"), for a list. Try showMem, showTasks, or showPc to get a better look at what's happening. You might also want to add other kernel debugging support while you're recompiling it, also CONFIG_KALLSYMS=y.
 
  


Reply


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


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! k5knt Linux - General 39 07-18-2007 12:47 AM
Kernel panic -not syncing:Attempted to kill init! vengadesan Linux - Server 1 10-31-2006 07:39 AM
Kernel panic -not syncing:Attempted to kill init! vengadesan Linux - Server 1 10-28-2006 11:17 AM
Kernel panic-not syncing:Attempted to kill init skie_knite007 Linux - General 3 10-02-2006 10:46 PM


All times are GMT -5. The time now is 03:09 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