Distribution: ubuntu 5.10 Hardware Environment: motherboard ASUS P5LD2-VM, SATA Segate Brracuda Problem Description: This message i get if i use sate with pata there is no problem: [ 32.081190] usb 3-1: new low speed USB device using uhci_hcd and address 2 [ 32.238901] irq 185: nobody cared (try booting with the "irqpoll" option) [ 32.238951] [ 32.238952] Call Trace: <IRQ> <ffffffff8014a350>{__report_bad_irq+48} <ffffffff8014a545>{note_interrupt+424} [ 32.239149] <ffffffff80149f87>{__do_IRQ+137} <ffffffff80110c02>{do_IRQ+45} [ 32.239310] <ffffffff8010eb20>{ret_from_intr+0} <EOI> <ffffffff80311c4e>{thread_return+0} [ 32.239497] <ffffffff8010cca6>{mwait_idle+51} <ffffffff8010cc52>{cpu_idle+63} [ 32.239659] <ffffffff80490738>{start_kernel+383} <ffffffff8049024c>{_sinittext+588} [ 32.239821] [ 32.239921] handlers: [ 32.239961] [<ffffffff802a001c>] (usb_hcd_irq+0x0/0x53) [ 32.240058] Disabling IRQ #185 [ 32.245777] usbcore: registered new driver hiddev
Created attachment 6947 [details] dmesg
Created attachment 6948 [details] lspci
BIOS setting "Enhacent mode" + "SATA only" resolv this problem. But it's inpossible to boot with cdrom.
An older report for this problem (also pointing to the patch by David Brownell causing/triggering it) is: http://lkml.org/lkml/2005/11/14/274
I'll try 2.6.12
2.6.12 had same problem. This is not regrsion and this is not usb problem (i tested with differen bios usb options and dindt get positiv result). I compiled piix us module and made some tests. With bios sata only and sata + pata . This error apper only! after piix module loaded + bios "sata+pata" option.
Created attachment 6959 [details] lspci sata only, before piix loaded
Created attachment 6960 [details] lspci sata only, after piix loaded
Created attachment 6961 [details] lspci sata+pata, before piix loaded
Created attachment 6962 [details] lspci sata+pata, after piix loaded. This one is after error
Comment on attachment 6959 [details] lspci sata only, before piix loaded This configuration working goot.
i can't reproduce this bug anymore. So it seems to be fixed. Thank You.