kernel panic after upgrade: Spurious ACK...

bmalewski · 2006-12-19 00:45:29

Hallo,
I am very beginner in Arch linux. I used Ubuntu before. When upgraded my Arch by
pacman -Syu, my machine couldn't start. It means, there was a list of the same comunicates:
atkbd.c: Spurious ACK on isa 0060/serio0. Some program might be trying hardware directly.
I had the same problem when I installed by ftp with a new kernel. I changed my GRUB correctly. I read something about "earlymodules=piix". Could you explain me, what it is and where should I write that line.
I did this command, it may help: mkinitcpio -M
and I received:
Modules autodetected:
cdrom
ide-cd
ide-core
ide-disk
generic
piix
e100
eepro100
mii
usbcore
uhci-hcd
jbd
ext3
Could anybody help me?

CavalierBob · 2006-12-19 01:38:49

First post I see...welcome to the Arch community bmalewski!

I just went thorugh what you are facing myself today. Let us see if I can walk you through it.

1. When you boot and the Grub screen appears, press the down arrow key on your keyboard. This will stop Grub from booting a kernel image.

2. Read the text at the bottom of the Grub screen. Arrow up to highlight the Arch Linux boot image (not the fallabcak image) and press the "e" key to edit.

3. Should be 3 lines of text for this boot stanza. Arrow down to the line that should read something like:

kernel /vmlinuz26 root=/dev/hd* ro

to highlight the line.

NOTE: your line may have hda1 here or something else (mine has hda3 due to my optical drives).

4. Press the "e" key to edit the highlighted line.

5. Add the test "earlymodules=piix" (no quotes) after the ro on the line. Should look something like this:

kernel /vmlinuz26 root=/dev/hd* ro earlymodules=piix

6. Press the Enter key on the keyboard. This commits the edit for this boot only. Will do a permanent fix in a moment.

7. You should now see all 3 lines of the boot stanza on your screen and the middle line should have your edit. Press the "b" key to boot with the change you just made.

8. You should now be able to boot to your desktop enviroment (DE).

9. Once in the DE, use your DE's text editor to edit Grub's menu.lst. You must be root to do this. From my terminal in Gnome it would look something like this:

[bob@localhost ~]$ su
Password:
[root@localhost bob]# gedit /boot/grub/menu.lst

10. You will now see the same boot stanza in the menu.lst file as you edited in Grub. Add the earlymodules=piix text exactly as you did above to the equivelent line in the menu.lst file. Save the file and exit your text editor.

11. You should now be able to reboot and have everything work as it should.

Hopefully I did not leave anything out. Post back if you find I have made a mistake or you have further problems.

Bob

Last edited by CavalierBob (2007-02-13 04:14:49)

bmalewski · 2006-12-19 02:15:56

Hallo Bob,
Thank You very much for Your reply. I did as You had wrote and now my Arch linux is working on 2.6.19.1-1 kernel.
Thank You once again.

CavalierBob · 2006-12-19 02:33:01

You are most welcome! Glad to have been of some assistance.

Bob

brain0 · 2006-12-19 10:05:57

The keyboard message seems to be unrelated to the problem itself, it's just a weird message. Damn you kernel devs again.

iphitus · 2006-12-19 11:59:32

brain0 wrote:

The keyboard message seems to be unrelated to the problem itself, it's just a weird message. Damn you kernel devs again.

searching LKML shows it up as a bug in the input driver. Kernel panics, maybe because of piix, and each flash of the keyboard leds, it spits out this message, which eventually overwrites the original error.

Patch here... no idea if it works.
http://marc.theaimsgroup.com/?l=linux-k … 312852&w=2

James

byte · 2006-12-19 12:45:06

Thread is solved? Time for off-topic? Ok:

Adding "i8042.panicblink=0" to the kernel commandline should be a nice workaround.

bmalewski · 2006-12-19 12:59:43

byte wrote:

Adding "i8042.panicblink=0" to the kernel commandline should be a nice workaround.

As I wrote I was very beginner in Arch. Could you byte explain where exactly should I write this commandline. What should I do? I suppose that you mean the same place where I wrote 'earlymodules=piix'. Is it ok?
Thank you very much.
Benedykt

byte · 2006-12-19 13:08:31

Yes, on the "vmlinuz" line. It won't solve any problems but at least it will help to see the actual error.
But you don't really need it if you don't intend to experiment with bootloaders or device naming schemes. If your setup works now, just keep it that way.

Jet Li · 2006-12-27 06:47:48

i have the same problem guys.... i have tried all tha you say but the problem remains...still my pc doesn't boot... the error message is :

kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Jet Li · 2006-12-27 07:04:45

ok i think i found it there was a line changed at the loader...instead of

initrd /boot/kernel26.img

it was :

initrd /boot/initrd26.img

so i changed it and it is ok now...

OssiR · 2006-12-28 19:38:22

Jet Li wrote:

ok i think i found it there was a line changed at the loader...instead of
initrd /boot/kernel26.img

Yeah, that did the trick for me too.
Didn't have to add earlymodules line.

Bernie · 2007-01-02 21:16:50

I've got the same problem..... but the sollution offered here doesn;t work for me. I got the same error over and over again. Does anyone have any thoughts on how to solve it?

Sb0y · 2007-01-03 00:26:27

I have panic too after upgrade

Vrieskist · 2007-01-10 18:03:04

First of all, hello everybody! I'm new to arch, and to this board.

Well, I also had the above problem with the repeating error messages, the initrd /boot/kernel26.img trick solved that for me.

But now the keyboard locks! I'm watching at the login screen now and I can't type my user name etc. Before getting to the login screen I can still activate and deactivate the keyboard but in the login screen the keyboard locks completely.

I don't use any x environment. Just plain old arch 7.2 with all the upgrades from FTP.

Can anybody help?

-- update --
Just visited the irc channel. The problem was the USB mouse I had plugged in.

fingerpicker · 2007-01-11 12:31:51

hey ho, another linux noob gort problems with the sys upgrade

so the last 3 lines while boot

RAMDISK: Compressed image found at block 0
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)

Parttable looks like this:

grub entry should be right:
title Arch Linux
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/hda2 ro
initrd /boot/initrd26.img

in another thread there was said that you should rollback to the laste kernel. well I tried it, it doesn't work (perhaps because it's the first syu after install^^) cause i got an ibm pc i tried the earlymodules=piix to but it didn't fix anything

well i could just add the kernel to the ignorelist for pacman to upgrade but that wasn't what I was willing to do (i changed from ubuntu and wanted to start solving problems, instead of ignoring the error outputs ^^)
so would be great if sb could help

thx a lot

Asmodeus · 2007-01-11 13:57:10

Ya baby! Thanks to all who posted here...this fix worked.

LONG LIVE ARCH!
:twisted:

fingerpicker · 2007-01-11 15:45:22

uhm tried
kernel /boot/vmlinuz26 root=/dev/hda2 rootdelay=30 but still same error ^^

so dont really have a clue what to do (could it be that the autodetect doesn't work and if, is there a way to manuel set this?)

so long

byte · 2007-01-11 15:56:27

fingerpicker: initrd /boot/kernel26.img

fingerpicker · 2007-01-11 19:26:33

i already tried replacing it with kernel26.img, but not yet in combination with rootdelay, gonna do that tonight

Bernie · 2007-01-11 22:16:40

Hiya all.

After the update I had the error and used the solution earlymodules=piix. That worked perfectly. In Arch I updated the rc.conf file and I shutdown the computer. A couple of days later I boot the computer again and I get the same error. But the earlymodules thing does appear in the grub list.

what should I do?

yours

bernhard

bmalewski · 2007-01-11 22:40:12

Hello all,
when I started with Arch and I had upgrade problem I added earlymodules=piix to the kernel commandline and it worked. But few days ago I reinstalled my system once again and it didn't worked. I am working on my fallback kernel. I have no idea where the problem is. Why it worked and now it does not?

fingerpicker · 2007-01-11 23:17:49

well to the ones where earlymodules worked, try to add instead rootdelay=15 http://bbs.archlinux.org/viewtopic.php?t=28669<- written in this thread

for myself, i tried now to replace initrd32.img with kernel32.img and rootdelay=15 and if i replace with kernel32.img i get:
kinit not found
kernel panic no syncing - couldn't kill init

so really weird

gonna try the i8042.panicblink=0 now gonna post the return

bmalewski · 2007-01-11 23:35:21

OK I have good news. brain0 helped me and it works. I had to remove "sata" from HOOK line in mkinitcpio.conf. After that I did mkinitcpio -p kernel26.
Everything is ok.
Maybe it will help for somebody.

fingerpicker · 2007-01-13 23:22:16

Reinstalled arch today and tried agin (made an extra boot partition)

with grub initrd /kernel26.img it says kinit failed and with /initrd26.img it says not synching (0,0)

really strange (but after all gonna buy a notebook soon and perhaps arch will run on it well, otherwise oughta look for a diffrent distri)

Arch Linux

#1 2006-12-19 00:45:29

kernel panic after upgrade: Spurious ACK...

#2 2006-12-19 01:38:49

Re: kernel panic after upgrade: Spurious ACK...

#3 2006-12-19 02:15:56

Re: kernel panic after upgrade: Spurious ACK...

#4 2006-12-19 02:33:01

Re: kernel panic after upgrade: Spurious ACK...

#5 2006-12-19 10:05:57

Re: kernel panic after upgrade: Spurious ACK...

#6 2006-12-19 11:59:32

Re: kernel panic after upgrade: Spurious ACK...

#7 2006-12-19 12:45:06

Re: kernel panic after upgrade: Spurious ACK...

#8 2006-12-19 12:59:43

Re: kernel panic after upgrade: Spurious ACK...

#9 2006-12-19 13:08:31

Re: kernel panic after upgrade: Spurious ACK...

#10 2006-12-27 06:47:48

Re: kernel panic after upgrade: Spurious ACK...

#11 2006-12-27 07:04:45

Re: kernel panic after upgrade: Spurious ACK...

#12 2006-12-28 19:38:22

Re: kernel panic after upgrade: Spurious ACK...

#13 2007-01-02 21:16:50

Re: kernel panic after upgrade: Spurious ACK...

#14 2007-01-03 00:26:27

Re: kernel panic after upgrade: Spurious ACK...

#15 2007-01-10 18:03:04

Re: kernel panic after upgrade: Spurious ACK...

#16 2007-01-11 12:31:51

Re: kernel panic after upgrade: Spurious ACK...

#17 2007-01-11 13:57:10

Re: kernel panic after upgrade: Spurious ACK...

#18 2007-01-11 15:45:22

Re: kernel panic after upgrade: Spurious ACK...

#19 2007-01-11 15:56:27

Re: kernel panic after upgrade: Spurious ACK...

#20 2007-01-11 19:26:33

Re: kernel panic after upgrade: Spurious ACK...

#21 2007-01-11 22:16:40

Re: kernel panic after upgrade: Spurious ACK...

#22 2007-01-11 22:40:12

Re: kernel panic after upgrade: Spurious ACK...

#23 2007-01-11 23:17:49

Re: kernel panic after upgrade: Spurious ACK...

#24 2007-01-11 23:35:21

Re: kernel panic after upgrade: Spurious ACK...

#25 2007-01-13 23:22:16

Re: kernel panic after upgrade: Spurious ACK...

Board footer