Hi. I recently complied my own 2.6 kernel. I noticed that it didn't have iptables support,so I recompiled it again with the iptables support. Now,when I boot up,everything goes fine and then I get
And the kernel hangs. I've googled it for a while,but I can't seem to find a solution. A few sites said it was related to a keyboard,but I know the keyboard on my laptop works because I can still use it on my old 2.4 kernel(glad I kept it as a backup). I'm really stumped about what to do.


EDIT:Okay,I've narrowed down the problem to either xtables or iptables. I'm trying a few troubleshooting methods,I'll post the results.

EDIT 2: Okay,with just xtables compiled in,it gives the panic. I'm guessing there is a problem with xtables somehow,I'm not sure what it could be.

See if this helps, http://imcdnzl.blogspot.com/2006/10/...ding-edge.html

I've got the same problem, and will try it now.

Edit, i've found my problem. I hope you have SATA, because this turns out to be that SATA on 2.6 up to 2.6.18 was in Device Drivers -> SCSI -> low level drivers (as far as i remember). Now in 2.6.19 they changed the location.

It's silly that make oldconfig didn't detect that i had it enabled... They should have re-thought this to cause less hassle.

how did you solved it? I got the same problem, and under which menu to do what?

I meet the same problem when update 2.6.19 kernel.

I just try the method as link page in comment #2, go into Device Drivers---Serial ATA (prod) and Parallel ATA (experimental), turn on ATA device support and then the chipset I have(Marvell), and select them as "*", compile the kernel and reboot with the same "ACK" error. Then, it seems very crazy that I select all items in "Serial ATA (prod) and Parallel ATA (experimental)", failed again, same outcome.

I'll update my process if I fix it.

Regards
Phillip

Fixed.

Upgrade CentOS4.4(2.6.9) box to kernel 2.6.19 successfully. In the previous upgrade process, when recompiled the kernel and reboot, it will halt at "audit" point, and then locks in a loop with the following message:
I review .config file and only remove the audit selection in "General Setup-Auditing support", recompile the kernel, restart... boot succcessfully with new kernel.

This issue troubles me a lot of time to investigate "atkbd.c:Spurious ACK on isa0060/serio0", and now I think this message indicates not real reason caused the kernel panic(in my case, it seemes to miss some policy that audit failed). It confused me earlier to consume time on hardware/driver problem, and ignore the underlying reason.

Cheers,
--Phillip

For my penguin, Debian etch, (2.6.19.2)

Auditing support off -> does not work.

http://lkml.org/lkml/2006/12/5/239 does not either.

Happy Penguins!

solution :: http://www.linuxquestions.org/questi...d.php?t=512839

Still in problem

Hi,

I tried various things.

Both depreciated SATA modules and xtables are off. still same message.

I found that the real problem is NOT BUT cannot mount root (or something), this message is pushed away immediately. I am trying to take photo, but not easy.

I assume that SATA drive is not recognized on boot. I think I need to find out which kernel option enables libata (supposed to be under SCSI, but I have not found yet...)

Happy Penguins!

for the atkb issue try compiling in serial and ps2 mouse as per
http://wiki.linuxquestions.org/wiki/...ring_keyboards

Hi,

With my Penguin, (Debian Etch) serial and PS2 mouse trick did not work. I spent some time again, and found that "sata_sil" is not on after "make oldconfig" (I selected all default without paying attention), so that root partition cannot be mounted.

SOLUTION for my penguin was:
check "sata_sil" under serial-ATA (device driver), as compiled into kernel.

Happy Penguins!

In case somebody wants to know:

Make oldconfig is not supported nor recommended when kernel version changes. It's meant to work only for minor changes - e. g. from 2.6.20-1 to 2.6.20-2.

I do not think that anybody wants to know At least, I do not. I was quite sure that "make oldconfig" is recommended way to save time when upgrading, per README file in kernel tree.

You do not have to take my word for that. Just read this (and similar) threads.

You can call me sick nerd, but I think kernel (as most important part of the OS) requires a little more attention than just make oldconfig. I personally move to a new kernel version doing make allnoconfig.

yeah Emerson is right cos the change in sata location caught me out too
Amongst all the other changes.