PDA

View Full Version : Kernel panic after installing 2.6.22 kernels in F7



aatlasis
9th September 2007, 04:27 AM
Hello to everybody,

I have an HP nx9105 laptop where I've installed F7 x86_64. Although it is working smoothly with any kernel up to 2.6.21-1.3228, when I tried to update to any newest version of the 2.6.22 series (up to the latest), when I boot I receive an error "kernel panic - not syncing: Attempted to kill init!" I have tried all the 2.6.22 kernel versions, either using yum or by downloading and installing "manually" the rpm packet.

Are there any ideas? Has anyone faced a similar problem with these kernels in F7? Can I do anything, or should I install FC6 again?

Thanks in advance

Antonios

sunset
9th September 2007, 03:18 PM
Might be worth trying the fedora-test kernel:
yum --enablerepo=updates-testing update kernel

leigh123linux
9th September 2007, 03:25 PM
Hello to everybody,

I have an HP nx9105 laptop where I've installed F7 x86_64. Although it is working smoothly with any kernel up to 2.6.21-1.3228, when I tried to update to any newest version of the 2.6.22 series (up to the latest), when I boot I receive an error "kernel panic - not syncing: Attempted to kill init!" I have tried all the 2.6.22 kernel versions, either using yum or by downloading and installing "manually" the rpm packet.

Are there any ideas? Has anyone faced a similar problem with these kernels in F7? Can I do anything, or should I install FC6 again?

Thanks in advance

Antonios


I doubt that you have tried them all :)

Have you tried this one kernel-2.6.22.5-77.fc7

http://koji.fedoraproject.org/packages/kernel/2.6.22.5/77.fc7/x86_64/kernel-2.6.22.5-77.fc7.x86_64.rpm

http://koji.fedoraproject.org/koji/buildinfo?buildID=17377

or for others

http://koji.fedoraproject.org/koji/packageinfo?packageID=8

aatlasis
10th September 2007, 02:54 PM
I doubt that you have tried them all :)

Have you tried this one kernel-2.6.22.5-77.fc7

....


The last kernel that I had tried was 2.6.22.4-65 (I 'd tried all the ones available using yum).

Anyway, I just tried kernel-2.6.22.5-77.fc7 and again, I had the same problem.

By the way, is this a testing kernel?

I'm also going to try sunset's suggestion and I'll tell you the results!

Thanks a lot!

Antonios

leigh123linux
10th September 2007, 03:00 PM
The last kernel that I had tried was 2.6.22.4-65 (I 'd tried all the ones available using yum).

Anyway, I just tried kernel-2.6.22.5-77.fc7 and again, I had the same problem.

By the way, is this a testing kernel?

I'm also going to try sunset's suggestion and I'll tell you the results!

Thanks a lot!

Antonios

Yes but it hasn't made it into updates-testing yet but I have been using since it was posted.

[root@localhost ~]# uname -r
2.6.22.5-77.fc7
[root@localhost ~]#


Try adding nodmraid to your grub.conf


[root@localhost ~]# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd4,2)
# kernel /boot/vmlinuz-version ro root=/dev/sdd3
# initrd /boot/initrd-version.img
#boot=/dev/sdd3
default=0
timeout=5
splashimage=(hd4,2)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.22.5-77.fc7)
root (hd4,2)
kernel /boot/vmlinuz-2.6.22.5-77.fc7 ro root=LABEL=/1234 rhgb nodmraid quiet pci=routeirq
initrd /boot/initrd-2.6.22.5-77.fc7.img
title Fedora (2.6.22.5-71.fc7)
root (hd4,2)
kernel /boot/vmlinuz-2.6.22.5-71.fc7 ro root=LABEL=/1234 rhgb nodmraid quiet pci=routeirq
initrd /boot/initrd-2.6.22.5-71.fc7.img
title Fedora (2.6.22.4-65.fc7)
root (hd4,2)
kernel /boot/vmlinuz-2.6.22.4-65.fc7 ro root=LABEL=/1234 rhgb nodmraid quiet pci=routeirq
initrd /boot/initrd-2.6.22.4-65.fc7.img
title Fedora (2.6.22.1-41.fc7)
root (hd4,2)
kernel /boot/vmlinuz-2.6.22.1-41.fc7 ro root=LABEL=/1234 rhgb nodmraid quiet
initrd /boot/initrd-2.6.22.1-41.fc7.img

aatlasis
11th September 2007, 07:53 PM
...
Try adding nodmraid to your grub.conf
...

I did, but I faced the same problem.

Would be helpful if I post here the exact messages that appear on the screen?

Does anybodu know if other users have similar problems with me with this kernel version (2.6.22)? Because I have this problem only with the variants of this kernels, and not with the previous ones.

thanks again for your help! :)

leigh123linux
11th September 2007, 07:58 PM
Would be helpful if I post here the exact messages that appear on the screen?




output of the error is always useful so post it

cryan7755
12th September 2007, 03:34 AM
I have been experiencing the same issue since installing 2.6.22.* kernel and its driving me crazy, I have tried the nodmraid option but with no success,

reboot into 2.6.22.* kernel

Uncompressing Linux... Ok, booting the kernel
Red Hat nash version 6.0.9 starting
ata1: SRST failed (error=-16)
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
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: Attempt to kill init!


$ cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.22.4-65.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.22.4-65.fc7 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.22.4-65.fc7.img
title Fedora (2.6.21-1.3228.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.21-1.3228.fc7 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.21-1.3228.fc7.img

Any help would be greatly appreciated.

Running on an older PIII 800 Compaq Deskpro (don't laugh it was free and I have been using it to run fedora for years with much success, until now)

universalpoe
12th September 2007, 04:34 AM
It seems your physical drive has detached so that the system cannot mount the filesystem. Please check it out.

Poe

cryan7755
12th September 2007, 02:38 PM
That can't be if I select the other 2.6.21-1.3228.fc7 kernel it boots with no issue.

universalpoe
12th September 2007, 06:35 PM
Then can you check your fstab file because according to the information generated, it does say the system cannot mount the file systems which causes the kernel panic.

Poe

cryan7755
12th September 2007, 06:43 PM
I still don't think thats it, I have both the 2.6.21-1.3228.fc7 and 2.6.22.4-65.fc7 Kernels, one boots fine the other can't locate the file system and kernel panic.

cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/sdb5 /mnt/disk ext3 defaults 0 0
/dev/sdb3 swap swap defaults 0 0

jstoddard
12th September 2007, 08:25 PM
I also don't think that's the issue -- I mentioned in some other thread that I'm having this problem on my laptop as well with 2.6.22 x86_64 kernels. I've just been using the 2.6.21 kernels for now until one that works (hopefully) comes around...

harry.x.r
12th September 2007, 11:03 PM
Hi everybody,

I have been following this thread closely since my Compact R3000 laptop (with AMD64
processor) has the same kernel panic problem. I spotted some differences in the
config-2.6... files of the 2.6.21 and 2.6.22 kernels.

In config-2.6.21-1.3194.fc7 there is this line
CONFIG_PHYSICAL_START=0x200000

In config-2.6.22.4-65.fc7 there are
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_START=0x1000000

I wonder if this difference in kernel compilation caused the problem. I am not good
with building kernel for fedora. I would appreciate if someone can recompile the 2.6.22 kernel with the configuration of config-2.6.21-1.3194.fc7 above and see if it still panics.

Harry

universalpoe
13th September 2007, 02:04 AM
I think I cannot help on this now. Hope somebody with good knowledge on Fedora coming here to help to identify the causes and solve this problem.

Poe

cryan7755
13th September 2007, 04:49 AM
Thanks for all your assistance Poe.

aatlasis
19th September 2007, 06:01 PM
I installed the "latest" kernel update available from yum (2.6.22.5-76) and I was ready to write down the exact message in order to post it here (quite big and complicated). Before doing this I decided to try the corresponding kernel-debug option and - guess what: it worked!

- Does anybody know if kernel-debug saves somewhere a log file in order to check it and, if necessary, to post it?
- Is it normal that kernel-debug works properly and the corresponding normal version doesn't?
- Can I use this kernel-debug version in my daily usage of the laptop? Is there any problem (i.e. degradation of the performance)?

Thanks a lot

Antonios

KimBP
20th September 2007, 06:53 PM
A month ago or so I had the same problem. Suddenly after updating some packages (most probably also a kernel update or two - I didn't pay that much attention to the updates then) I had the same problem. Couldn't find VolGroup0 and panic'ed. I never found any solution and by some reason my old kernels were lost so I started from scratch again - this time without volume manager. Don't know if the problem was caused by volume manager though, but with only one disk I can't see the reason for using it.

Well this wasn't any help to you I guess, but maybe a warning about a possible risk when updating the kernel

/Kim BP

KimBP
20th September 2007, 07:21 PM
.. I just forgot to tell that my disk didn't had any defects. Whenever I booted at the rescue CD all partitions on my disk where mounted as supposed to.

/Kim BP

arne@fedora
20th September 2007, 10:45 PM
Yes, there are some trouble. Do you know if many have the same ?

arne@fedora
20th September 2007, 10:54 PM
.. I just forgot to tell that my disk didn't had any defects. Whenever I booted at the rescue CD all partitions on my disk where mounted as supposed to.

/Kim BP

Did you have kernel panic after installing recent kernels in Fedora ?
What kind of machine do you have

arne@fedora
20th September 2007, 11:03 PM
I am new to this game, will I receive any answer ?

arne@fedora
20th September 2007, 11:13 PM
Well, I have little time. Just tried to figure out how many may have this problem.
In my case, tested FC6,7,8 and test versions. The reason is connected to the
ACPI - it doesn't find your disk, - have any of you done a kernel compile ?

KimBP
21st September 2007, 06:35 PM
Did you have kernel panic after installing recent kernels in Fedora ?
What kind of machine do you have
After reinstalling Fedora I'm running quite stable at 2.6.22.4-65. Some days (weeks?) ago I installed some updaets among which apparently was a kernel update 2.66.5.76 with mwhich my machine isn't able to boot properly. See http://forums.fedoraforum.org/showthread.php?t=166913&page=2&pp=15

I have an VIA EPIA EN12000 with one SATA disk and a KWORLD DVB-T 220 TV card installed

/Kim BP

my_linux
21st September 2007, 10:15 PM
Hi,

I have a similar error on my Acer Aspire 7520 running 2.6.22.5-76. x86_64.

Red Hat nash version 6.0.9 starting
Unable to access resume drive (Label=swap-sd3)
Mount: Could not find filesystem '/dev/root'
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!

Unfortunately as yet it is an ongoing problem :(

harry.x.r
22nd September 2007, 10:53 PM
Hello everybody reading this thread:

I found a solution to this problem.

First. Download the latest kernel 2.6.22.7 from, for instance,
http://www.kernel.org/pub/linux/kernel/v2.6/

Second. gunzip and tar xvf the kernel file.

Third. Copy /boot/System.map-2.6.22.5-76.fc7 to .config in the kernel
directory you just made, assuming your latest Fedora kernel is 2.6.22.5-76.fc7.

Fourth. Run make menuconfig.
Select Processor type and features.
Near the end, de-select Build a relocatable kernel(EXPERIMENTAL) .
In the next line change the value to 0x2000000.

Finally run
make all
and as root run
make modules_install
make install

The new kernel solved my 2.6.22 kernel panic problem. Moreover it also solved another
problem. My PC card to CF card adapter is working again. I could not use my CF card before.

arne@fedora
23rd September 2007, 10:48 AM
Hi,

I did join this forum, just to get an idea as who many struggle with this problem. So I wasn't the only one ;);)
Well, I have tried to participate with some possible bughunting at kernel.org, as well testing Fedora development.
One way I was able to boot up, was to toggle the power button during the boot up process. For Fedora8t2, you may try
to add -noapic in grub.conf for the kernel, if you have any NVIDIA based notebook. This may help with the more recent
test releases, but there are still problems with USB and other things. NVIDIA will not release any info - and if Fedora
and other Linux distros will run on this hardware eventually, I can't say. Personally I am preparing to return this
procuct . Have spent every waking hour for a month investigating this problem, and if products can't run Linux, I am
not interested ! Have received info from RedHat about these problems - they have the same problem gaining needed
info. So ?? The problem isn't really Linux. It is also funny to note that Windows user complain, want their XP back,
as some of their old programs will not run under Vista. Perhaps we need to demand that hardware vendors will
take us seriously ? I wish you all good luck, hopefully ways around some of these problems can be found. Personally,
I haven't been this confused and frustrated in years. I am going to test some other hardware. If you can find some
ways it will play - you give help to all the rest of us.

arne