Distribution: Debian Etch Hardware Environment: CPU: Intel Pentium III (Katmai) 450 Mhz 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 64 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1] [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1] I/O ports at ffa0 [size=16] Problem Description: Hi, I want to test PATA drivers on my PC, I compiled the kernel (2.6.19 and 2.6.20) without support CONFIG_IDE and with support CONFIG_ATA, CONFIG_SATA_AHCI, CONFIG_ATA_PIIX, CONFIG_ATA_GENERIC, CONFIG_PATA_JMICRON, CONFIG_PATA_MPIIX and CONFIG_PATA_OLDPIIX. At boot, there are the error messages : atkbd.c: Spurious ACK on isa0060/serio0... atkbd.c: Spurious ACK on isa0060/serio0... atkbd.c: Spurious ACK on isa0060/serio0... atkbd.c: Spurious ACK on isa0060/serio0... The messages are fast, but according to what I could see like message, I believe that IDE controller is not recognized. I can boot with support CONFIG_IDE and without support CONFIG_ATA. Regards.
The ATA controller you posted the data for is disabled.
Please attach dmesg and lspci -v for the system as a whole not just the one device so I can see better what is going on (a boot of the old IDE is fine)
Created attachment 10404 [details] The lspci -v output
Created attachment 10405 [details] dmesg output of kernel 2.6.20 with support CONFIG_IDE and without support CONFIG_ATA.
Created attachment 10874 [details] lspci -v Output of lspci -v from an old Compaq Deskpro P550 (same issue)
Same problem here for me. Interestingly enough, the atkbd.c: Spurious ACK on isa0060/serio0... messages alternatively turn on and off the scroll-lock LED on the keyboard. Will gladly test patches or provide access to the box for diagnostics.
Alan, ping.
Not sure - we saw similar breakage from the PCI hack stuff to stop buggy X breaking and it may well be we've accidentally fixed it in sorting that out and in redoing the PCI resource handling. Not sure.
Frederic, Johnatan, can you confirm if the problem has been fixed for you? Thanks.
Hi, I tested the kernel 2.6.22 with the same configuration and I have the same error. I tested the kernel 2.6.23 with the same configuration and I do not have any more error, I could boot with the PATA. I post the dmesg. Regards.
Created attachment 13100 [details] dmesg of kernel 2.6.23
Hi, I tested the kernel 2.6.25 on other PC and I have the same problem, I couldn't boot with the PATA and the led caps lock and scroll lock blinks. I don't have the error message : atkbd.c: Spurious ACK on isa0060/serio0... The kernel block when he wants to mount the root, the error message says he does not find the disc. To avoid problems of naming, I indicated in lilo setting to use the UUID : root="UUID=4286b046-9977-4a39-9b78-5dd20775bd83" I post the dmesg ant the lspci. Regards.
Created attachment 16291 [details] dmesg of kernel 2.6.25
Created attachment 16292 [details] The lspci -v output
The dmesg appears to be incomplete and doesn't include the panic. Note also that lilo does not support root= for UUID, and the kernel will only do so if you have a suitable initrd built.
Hi, Thank you for your reply. The dmesg is for the kernel to boot properly, it includes : CONFIG_HAVE_IDE=y CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y CONFIG_BLK_DEV_IDEACPI=y CONFIG_IDE_PROC_FS=y CONFIG_BLK_DEV_IDEDMA_SFF=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_PCIBUS_ORDER=y CONFIG_BLK_DEV_GENERIC=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDE_ARCH_OBSOLETE_INIT=y and CONFIG_ATA=y CONFIG_ATA_ACPI=y CONFIG_SATA_AHCI=y CONFIG_ATA_PIIX=y CONFIG_ATA_GENERIC=y From the lilo.conf man page : (22.6) The root filesystem may also be specified by a LABEL= or UUID= directive, as in '/etc/fstab'. In this case, the argument to root= must be enclosed in quotation marks, to avoid a syntax error on the second equal sign; viz., I will test the kernel with an initrd. Regards.
Here is the message for the kernel without initrd: VFS: cannot open root device "UUID=4286b046-9977-4a39-9b78-5dd20775bd83" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) The last message for the kernel with initrd: Begin: Waiting for root filesystem...
Frederic, your harddisks are detected fine. You can't use LABEL/UUID w/o initrd. Can you boot by specifying the root partition directly?
I tested without initrd and with the "root=/dev/sda1" boot option: VFS: cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Hi, I tried the kernel 2.6.25 on the PC that works well with kernel 2.6.23 and libata (PATA) (see the beginning of this bug report), and I have the same problem at the boot: VFS: cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) It boot well with the libata of kernel 2.6.23, but not with that kernel 2.6.25. I post the dmesg for the kernel 2.6.23, lspci and both config.
Created attachment 16340 [details] dmesg of kernel 2.6.23
Created attachment 16341 [details] lspci
Created attachment 16342 [details] config of kernel 2.6.23
Created attachment 16343 [details] config of kernel 2.6.25
Can you please try to capture the kernel logs from failing boot? You'll need to use either serial console or netconsole (Documentation/networking/netconsole.txt). Thanks.
Hi, I used netconsole, great tool! :o) What is surprising in the kernel logs is that after the line "SCSI subsystem initialized" there is no line "libata version 3.00 loaded". The kernel is yet compiled with the support of the libata, see the configuration file earlier. This could be due to the ACPI? Below the kernel logs.
Created attachment 16366 [details] dmesg of kernel 2.6.25
Hmmmm..... strange. It looks like libata isn't compiled in. Or, maybe loglevel is set to a higher value. Does specifying "loglevel=7" make any difference?
Created attachment 16442 [details] dmesg of kernel 2.6.25 with loglevel=7
The libata message is printed from ata_init() which is always called during boot if built in. Can you please try kernel parameters "loglevel=7 initcall_debug"?
Created attachment 16450 [details] dmesg of kernel 2.6.25 with loglevel=7 and initcall_debug
Thanks. Both ata_init and piix_init are running. Messages not printed on console is probably due to printk loglevel. Can you please post the result of "lspci -nnvvv"?
Created attachment 16453 [details] The lspci -nnvvv
Created attachment 16454 [details] The lspci -vvxxx
Might be related. http://bugzilla.kernel.org/show_bug.cgi?id=10854
Looks like this have been fixed in latest kernel (2.6.28.7). PIIX4 controller is recognized and ata_piix module is used. So far no problems using it. Config, dmesg and lspci -nnvvv attached below
Created attachment 20593 [details] Config for 2.6.28.7 kernel with libata PATA support
Created attachment 20594 [details] dmesg of 2.6.28.7 kernel
Created attachment 20595 [details] lspci -nnvvv (PIIX4 controller is 8086:7111)