fedora core 3 installation kernel panic - not syncing
 

Hello there

I just bought a new machine:
* MSI 915P Neo2 mobo
* Intel Prescott 3.2 socket 775 1M L2 cache
* 1024 MB DDRII533 RAM
* ASUS Extreme6600 (Nvidea Geforce)
* Maxtor HDD SATA 250 GB (Primary Master)
* MSI DVD-writer (Third Master)

I tried to install fedora core 3 but got a kernel panic. This is also the case with knoppix (kernel 2.6.9 and suse 9.2)

If I boot with option mem=1024 It seems to go over the kernel panic, but I get nothing more then:

"Uncompressing the kernel...OK ;-) Booting the kernel" with a blinking underscore on the second line...

In an other tread I read about MAXTOR problems with CD drives on the same cable, mine isn't, but the only way to see the DVD is to set the SATA MAXTOR to IDE... :-(((

here comes the kernel panic, Anybody any ID?

CPU: 0
EIP: 0030:[<c00f0488>] Not tainted VLI
EFLAGS: 00010246 (2.6.9-1.667)
EIP is at 0xc00f0488
eax: 0000b100 ebx: 00000000 ecx: 00002504 edx: 25808086
esi: 00000000 edi: c03798cc ebp: 00000000 esp: dfc87f70
ds: 007b es: 007b ss: 0068
Process Swapper (pid: 1, treadinfo=dfc87000 task=dfcb1730)
Stack: b1000400 c00f026b c00f028d 00000400 000098cc 00002570 0100b102 8086c00f
00540000 0246c00f c02a4cd0 00000060 dfc87fbe dfcab400 00000000 00000000
c02a51b9 dfc87fbe dfc87fbf c03c6d86 dfc87fc0 dfc87fc0 c03d1674 00000000
Call Trace:
[<c02a4cd0>] pci_bios_find_device+0x19/0x38
[<c02a51b9>] pcibios_sort+0xc9/0x14b
[<c03c6d86>] pcibios_allocate_resources+0xeb/0xfc
[<c03c77e7>] pcibios_init+0x65/0x68
[<c03b1702>] do_initcalls+0x49/0x8e
[<c010051b>] init+0xc1/0x1f3
[<c010045a>] init+0x0/0x1f3
[<c01041d5>] kernel_thread_helper+0x5/0xb
Code: 81 fe 00 ff 75 05 8a c1 ee eb 11 66 81 fe 01 ff 75 07 66 8b c1 66 ef eb 03
8b c1 ef 66 9d 66 5a 58 f8 c3 c3 c3 66 50 66 53 b7 00 <2e> 8a 83 96 04 00 00 66
5b 8a d8 66 58 c3 00 01 02 03 04 05 06
<0>Kernel panic - not syncing: Attempted to kill init!



So with kernel 2.4 nothing's wrong, it's only kernel 2.6.........


Thanks for the help!!!

Wouter

What bootloader are you using? It seems to be the kernel has issues with the initial RAMdisk image (initrd), which is why it's complaining about init... I may be wrong.

I didn't used any boot loader yet, just the installation CD.
My disk was low level formated (just new from the store)

I now run Slackware (kernel 2.4.29) and it runs just fine with LILO in the MBR (first tried LILO in the boot partition, but that didn't do the trick --> "L 99 99 99 99...").

I now know that nor kernel 2.4.26, nor kernel 2.6.xx support my SATA disk (250 GB Maxtor) or my onboard LAN (Gigabyte). I hope that a newer release of kernel 2.6 will help me with these problems, but in the mean time, I'll continue using 2.4.29 with an extra LAN because the onboard LAN is still not supported... :-s

fedora core 3 installation kernel panic
 

I bought a new machine last month and had similar results trying to install either Fedora Core 3 or Debian. With Fedora I get

Call Trace:
[<0222dd34>] pci_bios_find_device+0x1d/0x3e
...
[<021041d9>] kernel_thread_helper+0x5/0xb

Code: 2e 8a 83 96 04 00 00 66 5b 8a d8 66 58 c3 00 01 02 03 04 05
<0>Kernel Panic: Attempted to kill init!


The machine has a 3.4GHz P4 on an MSI mother board with DVD and TV capabilities.

It also has cold swappable hard drives, one with Mandrake which nicely comes up, and one with XP.

I'd love to find out why Fedora and Debian can't work on it. Maybe someone will have a clue! (hope, hope)

Solution?
 

Hi!

I have the same problem with a new P4 3GHZ, MSI Neo 916G and a Maxtor Diamon 80 GB. Have you found a solution to install Fedora?

kernel panic
 

hello

i have a similar problem. I have installed fedora within vmware 4.0 and it appeared that the fedora installation went successfully. upon reboot, i receive the kernel panic - not syning; attempting to kill init

I am stuck, any ideas on how to resolve??

thanks in advance.

FWIW: I have the same problem. I have tried every kernel command line parameter I can think of and still get the kernel panic. I regret the day I bought this MSI MB with the the 915P chipset. These MB's have got to be the most "linux" incompatible MB's I have ever seen.

hello

same problem here

Call Trace:
[<0222dd34>] pci_bios_find_device+0x1d/0x3e
...
[<021041d9>] kernel_thread_helper+0x5/0xb

Code: 2e 8a 83 96 04 00 00 66 5b 8a d8 66 58 c3 00 01 02 03 04 05
<0>Kernel Panic: Attempted to kill init!

i have tried suse 8.2/fedora 1,2,3 + test versions/redhat 4 Ws nothing works ;(


MSI NEON 2 platinium

I see that the last post on this topic is just a few days ago, but is there any chance you guys have found anything useful? I'll keep searching google and post back if I find anything, but hopefully one of you has already found a fix. :)

hello
 

no solution i think MSI SUCKS HARD !!! ;)

Ok, found the solutions, the article on this page:
http://kerneltrap.org/node/4030
tipped me off to the obvious fix. As with most software manufacturers the fixes are often in the newer versions. :)
Upgrade to Vmware 4.5.2 and you're off to the races boys :)

Kernel Panic - Dont Panic!
 

Here's my solution (suggest you try the same especially if system is hanging when trying to install Fedora X).

My machine was running Fedora Core 1 just fine. I upgraded to Fedora Core 3. Then after running the Kernel update (up2date) every time I rebooted I had various Kernel Panics which was very very very annoying.

Thinking it was Fedora 3 clashing with my motherboard I downloaded and installed version 2 (same results) and also version 1 (also same annoying hang on install).

After trying the 3 versions of Fedora I was fairly sure it was hardware related so buy process of elimination I finally discovered it was my memory which was causing the headache. Wish I tried my memory before buying a new harddrive (such is life!).

So the moral of the story is if your getting Kernel panics then I strongly suggest testing your system memory. I used software called Amidiag (dos version). My memory was failing on the pattern test.

Hope this helps ;)

I think it's an Fedora related problem. SUSE Linux 9.0 ist booting fine?!

Found the solution!
Try to boot with "F4" (Kernel Options) #linux pci=nosort text
Now Fedora can be installed.
The next problem is to get X running on the 915G chipset.

or....upgrade vmware :) Hehe, wow you guys are sure working hard to not upgrade your version of vmware. Too much $$ ?

I had the same problem and this is what I did:

1. download a new kernel (I'm using 2.6.11.6 kernel right now)
2. use the kernel config used for your original install or update. this can be found in "/boot" directory and mine is called "config-2.6.10-1.770_FC3" (use this as your base kernel configuration)

3. once your have loaded the "config-2.6.10-1.770_FC3" into the kernel you can then remove the things you don't need or things you need. (CAUTION!!! I wouldn't change anything in the "FILE SYSTEM" area of the kernel. Some wrong changes here I believe is what causes the kernel panic.)

4. simply make the changes you need and then save the changes.

5. Give the usual commands: make all
6. make modules_install
7. make install
8. everything should be ready to go so reboot the system and choose the kernel you wish to boot from the grub loader screen.

9. if you get a kernel panic again then there is something wrong in the kernel configuration setting which you compiled (hint: you might have removed the wrong settings)

This worked for a stand alone install of Fedora Core 3 and the hard drive was NOT split to work as a dual boot. I suffered numerous kernel panics until I tried to use one of the original kernel configs and it compiled and rebooted perfectly. If you are like me and like to run a lean mean fast kernel then I would recommend trying to remove little by little from the kernel config each time your recompile. Every time you have a successful reboot simply save the kernel config and try again. If you get a kernel panic you probably went too far (changed something you shouldn't have) so go back to the last kernel config that worked and mess with settings again. I know it is a long ass lame process but it works and well worth it once you get the kernel where you want it. Save the final kernel config somewhere safe (on a CD-R) so if you need it again it will be a breeze to recompile. Good luck and hope this helps. :)

Here is what my "grub.conf" file looks like:

default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11.6)
root (hd0,0)
kernel /vmlinuz-2.6.11.6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.11.6.img
title Fedora Core (2.6.10-1.770_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.770_FC3 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.10-1.770_FC3.img
title Fedora Core (2.6.9-1.667)

Kernel panic - not syncing: Attempted to kill init!
 

Thanks mgerste
fedora core 4 test
linux pci=nosort text really worked for me but like you said it X wont work ;)

Meaby somebody could fix that too ;)

kernel panic attempted to kill init
 

Hi All

Finally resolution to install linux msi neon 2 platinium based motherboard update Bios 1.7v then everything works GR8

hello,

I have exactly the same problem as the original poster (panic occuring at kernel_thread_helper). I am trying to install FC3 for the first time on a machine with only XP installed. I am using the dvd version, with the both download and the burnt dvd verified. It's not a case of updating vmware as I have not installed that nor do I have any idea what it is. I'm currently downloading the CD version to see if that works any better. A bit annoying as I have a monthly data quota but it has to be tried I suppose.
Thanks.

Update: Exactly the same issue with the CD version. Trying suse instead...

This thread has been dead for a while, but in case someone else stumbles across it like I did, I thought I would post the solution (it worked for me anyway).

I got the following from here:
I don't understand it and didn't expect it to work, but it did! :D Hope I'm not to late to help anybody!

The Fedora Core 4
 

I had similar problems with the:

Kernel panic - not syncing : kill init!

the problem was the bios not sending the correct mem amount to the kernel.
when u boot with the cd,look under the F1-F4 options for the memtest,then
see what amount of memory the memtest program tests...then reboot your
machine,and at the prompt enter : linux mem=amountM

hope it helps u folks

Now this is retarded, but it did indeed work. On boot, I just spammed characters w/ my left hand, hit enter, then hit enter again after the cannot find kernal asdafasafdsfa error. Amazing.

Spamming random characters has to be the most ridiculous bug workaround that I've ever heard of, but it worked for me on FC4, too.

what to do when it happens to a previously working sys?
 

hi. sorry to re-open this old thread-- but, i've encountered a similar situation, and i've found little in the way of googling.

mine is a standalone Fedora Core 5 (albeit, i had an XP slaved, which i was viewing mounted via /mnt/windows/... but i'm doubting that is relevant here?)

my Fedora Core 5 was working great-- since late May 2006. coincidentally to your discussion, the Kernel has recently updated, but this all is "automatic" w/ the Yumex. everything seemed okay, and i've never had any boot problems from the start. but something i did while trying to customize some directories / move files around, i think i accidentally sent a command to the wrong directory-- and now i've got a Kernel Panic happening. i'm not Linux savvy enough to know what to do "outside of" the OS environment i'm used to. i pulled up the grub> prompt, but i don't know what to do from there.

my understanding is that the Fedora installer makes 2 partitions: one for Grub and the other for the rest of the OS (if i had to write an essay on that, i'd have to stop there because i don't really know more about what Grub vs the Os vs what's going on w/ the partitions-- but my guess is that Grub handles boot-time-config, and from there, the "other" half takes over for the "desktop environment"?)

so, if it's possible for me to solve this problem by editing something in "Grub", then i'm certain that i DON'T know where to look. likewise, if it's something i do from Grub to the Filesystem... etc., etc.. this is where i need some guidance 'cause i've no idea really what i'm looking for this far "early" in the boot processes.

thanks! my first post on the issue, before i found this thread is here:
http://www.linuxquestions.org/questi...d.php?t=484267

thanks! oh, and since this is my "Primary" drive, i don't really have the luxury of wiping it and starting over-- i mean, i'm hoping not to have to lose several "original" code and graphics documents.

thanks! (sorry for the long text)

This is an old thread, but I thought I'd add to it. I found this thread from a google search. I got the same error message with fc6 that had been working for several months. I tried an upgrade & new install of Fedora 7, same thing. After trying cmos clearing, vid card & memory swap & several other things I ran a hdd fitness test on my WD 40 gig sata hdd. It failed. Error 0225, to many errors. I wiped the drive, wrote zeroes, full. I did a fresh install of Fedora 7. All is well now. I'm sure my hdd is living on borrowed time, but this got me going again. Seems there are several things that will give this error code. Hope this helps someone.

The commonalities between your situation, crenclan, and mine seem to be limited to the fact that no filesystem could be found-- yours due to hardware failure; mine due to corrupt filesystem paths, but both resulting in a "panic" for the Kernel. In my research on the matter, I learned that there are many situations which may cause Kernel Panic.

I still have the HDD, in the same condition as when I first opened this thread. The data is still there, and there's no hardware trouble, so I'll keep it until I am able to figure out how to extract it.

I don't understand why a completely functional ext2 or ext3 Fedora Core 5 system, having that distorted HDD installed as a slave, is yet unable to "see" the partition containing the FileSystem (as WinXP, in analogy, would continue to "see" the directories of a slave "E: Drive"-- even if E:\Windows\ were removed or damaged.)

I've tried the "slave" method with 2 functional Fedora systems as well, and not been able to "see" the slave. I'm probably doing something wrong with fstab, but i don't know what.