You are not logged in.
Hi!
I found out this morning that after upgrading the "ck" and "beyond" kernels to 2.6.19 I get kernel panic on boot, just after the kernel26ck.img is loaded (the stock one works fine). I have following kernels installed:
[waldek@wolfblade ~]$ pacman -Q kernel26 kernel26ck kernel26beyond
kernel26 2.6.19-3
kernel26ck 2.6.19.ck2-2
kernel26beyond 2.6.19.beyond1-1
I have custom mkinitcpio.conf that looks as follows:
MODULES="sata_nv sd_mod reiserfs"
BINARIES=""
FILES=""
FBTHEMES="ChromaticBlue"
HOOKS="base udev resume fbsplash"
I have noticed that the content of kernel26*.img differs among the "stock" and the "ck" and "beyond":
[waldek@wolfblade ~]$ diff stock.txt ck.txt
3,13c3,12
< /lib/modules/2.6.19-ARCH
< /lib/modules/2.6.19-ARCH/kernel
< /lib/modules/2.6.19-ARCH/kernel/drivers
< /lib/modules/2.6.19-ARCH/kernel/drivers/ata
< /lib/modules/2.6.19-ARCH/kernel/drivers/ata/libata.ko
< /lib/modules/2.6.19-ARCH/kernel/drivers/ata/sata_nv.ko
< /lib/modules/2.6.19-ARCH/kernel/drivers/scsi
< /lib/modules/2.6.19-ARCH/kernel/drivers/scsi/sd_mod.ko
< /lib/modules/2.6.19-ARCH/kernel/fs
< /lib/modules/2.6.19-ARCH/kernel/fs/reiserfs
</lib> /lib/modules/2.6.19-ck
> /lib/modules/2.6.19-ck/kernel
> /lib/modules/2.6.19-ck/kernel/drivers
> /lib/modules/2.6.19-ck/kernel/drivers/ata
> /lib/modules/2.6.19-ck/kernel/drivers/ata/sata_nv.ko
> /lib/modules/2.6.19-ck/kernel/drivers/scsi
> /lib/modules/2.6.19-ck/kernel/drivers/scsi/sd_mod.ko
> /lib/modules/2.6.19-ck/kernel/fs
> /lib/modules/2.6.19-ck/kernel/fs/reiserfs
> /lib/modules/2.6.19-ck/kernel/fs/reiserfs/reiserfs.ko
20c19
</lib> /lib/klibc-C2z_DMnqPyftZCYmjdWTcAM2woc.so
63d61
< /message
97,99d94
< /lib/modules/2.6.19-ARCH/modules.dep
< /lib/modules/2.6.19-ARCH/modules.alias
< /lib/modules/2.6.19-ARCH/modules.symbols
same goes for "beyond". the "libata.ko" does not exist neither in "ck" nor "beyond" modules directories:
[waldek@wolfblade modules]$ find /lib/modules/ -name libata.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/ata/libata.ko
I re-compiled the "ck" kernel from abs but it did not help.
Is it related?
cheers
waldek
Offline
Thanks for letting us know, waldek, and apologies for any inconvenience. I'll update kernel26ck now, and I'll let iphitus know about beyond - he'll probably read this anyway.
Offline
waldek - brain0 says the absence of the libata module is not the cause of your kernel panic. Can you post the exact error message(s) that appear immediately before the failure?
Offline
I havent't noticed your last update - sorry.
I can try it at home in the evening if it is still important - just for the record - the last update to ck (kernel26ck 2.6.19.ck2-3) fixed the problem.
Offline
No longer important, in that case.
The only change in 2.6.19.ck2-3 is that libata is now a module - so your original theory was right. Thanks for catching it, and glad you're up and running again.
Offline
don't worry - as you can see I have 3 kernels installed and rarely upgrade all 3 at the same time
I need to enable the testing repos though to catch it earlier.
By the way thanks a lot for all the kernels we have to all maintainers - I don't have to compile anything myself because all 4 (?) of them satisfy all my needs on desktops and notebooks. Thanks again.
waldek
Offline
By the way thanks a lot for all the kernels we have to all maintainers - I don't have to compile anything myself because all 4 (?) of them satisfy all my needs on desktops and notebooks. Thanks again.
++
You guys rock!
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
I am having similar problems with mm
Offline
Do you have a particular need for the mm kernel? Most of the new features it provides are now in the 2.6.19 kernel packages.
That aside, kernel26mm already provides libata as a module, so your problems are caused by something else. Please provide as much detail as possible.
Offline
actually I am trying to get reiser 4 working and beyond and mm are the only kernels I know of with the reiser 4 pach, and both are giving me issues saying that the root filesystem (which is reiser3) cannot be found and a kernel panic, unable to mount root fs on unknown block(0,0) when the vanila kernel works just fine, I can't seem to find any problems with my grub menu, any ideas? Or rather is there anything else I might be able to give you?
Offline
here, 2.6.19-beyond breaks my lvm2... complains about a kernel without device mapper. is this my fault, or is something wrong???
edit:
i get this error on boot and on lvm lvscan:
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
inactive '/dev/array/home' [411.11 GB] inherit
edit2: dm-mod isn't loaded by default. it normally was, that's the problem. i'm gonna reboot, see if it works now, after adding dm-mod to my modules in rc.conf...
-=] life sucks deeply [=-
Offline
fixed... dm-mod added. also, hal didn't work very well, reinstalling dbus and hal fixed that..
-=] life sucks deeply [=-
Offline