FS#6550 - Kernel panic with current kernel

Attached to Project: Arch Linux
Opened by Frank Ickstadt (frigg) - Wednesday, 07 March 2007, 20:17 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi Jud,

greatings from Germany to Canada. Some years ago I've made a diving trip to quadra island...

Now back to my serious problem. Yesterday I've performed a Pacman -Syu and after this I've rebooted the system. After starting GRUB and a kernel panic message there is the following message on the panel of my HP Omnibook 6000 laptop:
atkbd.c: Spurious ACK on isa0060/serio=. Some program might be trying access hardware directly.
The message above is repeated infinitely.

Now I need a solution to come again to a bootable system. Any hints?

regards,
Frank
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 10 March 2007, 07:51 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Wednesday, 07 March 2007, 22:07 GMT
somewhere on forum there is a parameter posted that should fix your problem, sorry i don't remember it now.
Comment by Roman Kyrylych (Romashka) - Thursday, 08 March 2007, 07:42 GMT
frigg, see http://bbs.archlinux.org/viewtopic.php?t=28006 ;-)
tpowa, can we close this bug?
Comment by Roman Kyrylych (Romashka) - Thursday, 08 March 2007, 07:45 GMT
tpowa, is this patch found by iphitus useful: http://marc.theaimsgroup.com/?l=linux-kernel&m=116535141312852&w=2 ?
Comment by Frank Ickstadt (frigg) - Thursday, 08 March 2007, 08:20 GMT
Hi,

thanks for your help. I will try your suggested solutions today evening. First I will add break=y to the kernel line at the boot menu to verify the cause (patch found by iphitus). Mabe this is the rigt suggestion because the Omnibook 6000 is an old laptop without piix and sata capabilites.

Please don't close the bug until you get my report.

regards,

Frank
Comment by Frank Ickstadt (frigg) - Friday, 09 March 2007, 07:02 GMT
Hi,

here are some news. This is the output after adding the break=y line:
:: Running Hook [filesystems]
:: Loading root filesystem module...-e
Attemptimg to create root device '/dev/hda2'
ERROR: Failed to parse block device name for '/dev/hda2'
unknown
ERROR: root fs cannot be detected: Try using the rootfstype= kernel parameter.
:: Break requested, type 'exit' to resume operation
NOTE: klibc contains no 'ls' binary, use 'echo *' instead
ramfs$

Some lines above this quoted text I recognized the appearance of sda devices. I remember on changing the device names from hda to sda. After bootig knoppix I changed in arch linux menu.lst from root=/dev/hda2 to root=/dev/sda2 and performed a reboot. Now the kernel hangs and give me as last informatrion the type of my filesystem (ext3).

OK again booting knoppix and now I made a chroot /mnt/hda2
In the next step I edited /etc/mkinitcpio.conf and deleted the sata entry in HOOKS line and run a mkinitcpio -p kernel26. Mkinitcpio throws an error the the hook 'base" was not found and some errors on access permissions of /dev/null

As a result the system doesn't come up after reboot (changed /dev/sda2 to /dev/hda2 after editing mkinitcpio.conf).

Do you have further advices?

regards,

Frank
Comment by Frank Ickstadt (frigg) - Saturday, 10 March 2007, 06:10 GMT
Hi,

i think this case can be closed bcause all work is well done by changing the vmlinux line in /boot/grub/menu.lst from /dev/hda2 to /dev/sda2 AND remove break=y
The system comes up but complains about a wrong superblock and wants an e2fsck running. A bit later I recognized the cause: /etc/fstab still contains the /dev/hda2 entry. I have to change it to /dev/sda2, rebooting and everything comes up again.

No change to HOOKS line in /etc/mkinitcpio.conf nor additional parameter in the vmlinuz line in /boot/grub/menu.lst are necessary!

regards,

Frank

Loading...