Basically, the attached dmesg shows the kernel via_pata driver trying to assign assign an IRQ to the external controller, followed by the "nobody cares", then the IRQ is disabled. The card shows in lspci, but viaideinfo shows the controllers as disabled and no devices arte accessible. The above and this: https://bugzilla.redhat.com/show_bug.cgi?id=444543 are the two most similar bugs I can find; the result is that nothing is accessible on the generic VIA external controller (the VT6410). The same thing happens with the older IDE, and the newer libata drivers, but if I shutoff APIC or ACPI, then several other devices go wonky (eg, the on-board NIC). I also tried with both smp (my normal default) and uni-processor kernel configs with no real change. # lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:08.0 RAID bus controller: VIA Technologies, Inc. VT6410 ATA133 RAID controller (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)
Created attachment 179857 [details] no-SMP with libata
Created attachment 179858 [details] SMP kernel with VIA IDE driver
Created attachment 179860 [details] lspci -vvvv output
Can you reproduce the problem with sys-kernel/gentoo-sources-2.6.28-r1?
Booting with 'irqpoll' and 'irqfixup' as your boot parameters and attaching your dmesg would be interesting. Also, could we have the output of: 'cat /proc/interrupts' and your kernel config?
Sorry, I got turned into a witch, but I got better... None of the relevant kernel options resulted in a working controller (including irqpoll), and some even made it worse, ie, even lspci couldn't see it. Changing PCI slots made no difference either... Some of the above seemed to cause some interesting changes in the output of other things besides lspci, eg, dmesg and various /proc files. /proc/interrupts changed quite a bit, but I can't really interpret whether any one of them is better than another. Although this is a hardened server, I'll go ahead and try the gentoo-sources kernel and provide some examples of the current config; you'll need to tell me what you want to see after that. It's also my mail/www/proxy server, so it would be nice to minimize the number of reboots. $ cat /proc/interrupts CPU0 0: 29 IO-APIC-edge timer 1: 9 IO-APIC-edge i8042 6: 3 IO-APIC-edge floppy 7: 0 IO-APIC-edge parport0 8: 2 IO-APIC-edge rtc0 9: 0 IO-APIC-fasteoi acpi 12: 331062325 IO-APIC-edge i8042 14: 6158530 IO-APIC-edge pata_via 15: 6173123 IO-APIC-edge pata_via 16: 100002 IO-APIC-fasteoi pata_via 21: 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4 22: 0 IO-APIC-fasteoi VIA8233 23: 17793861 IO-APIC-fasteoi eth0 NMI: 0 Non-maskable interrupts LOC: 293266456 Local timer interrupts TRM: 0 Thermal event interrupts SPU: 0 Spurious interrupts ERR: 0 MIS: 0
Created attachment 183450 [details] config-2.6.28-hardened using libata pata driver current config-2.6.28-hardened, goes with /proc/interrupts output
How is it going with gentoo-sources-2.6.28-r1? Same issue? If you're still having the problem can you try with the latest gentoo-sources kernel (gentoo-sources-2.6.28-r4)?
We're up to hardened-sources-2.6.28-r9 and hardened-sources-2.6.29 now, is this still an issue for you? Has the problem or errors changed at all (and if so can you post new)? Thanks.
Yeah, let me build the 2.6.29 kernel and I'll give it a try...
(In reply to comment #10) > Yeah, let me build the 2.6.29 kernel and I'll give it a try... > any further info pls
We are now working to stabilize 2.6.32-r9. Can you give that a try and let us know if it is still an issue?
Sorry, got busy with extra work/travel, and that's my production server for now (such as it is) yada yada... I'll see if I can get a newer kernel on there shortly...
Okay this is an old bug about a kernel which is no longer on the tree. I'm closing it.
