On Sun, 2004-07-18 at 13:48, Jens Olav Nygaard wrote: > > From: Jurgen Kramer > > >>Just gave it a try. My EHCI controller is still failing (Asus P4C800-E > >>i875p) as in the 2.6.7-mm series. > >> > >> > >>ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 23 > >>ehci_hcd 0000:00:1d.7: EHCI Host Controller > >>ehci_hcd 0000:00:1d.7: BIOS handoff failed (104, 1010001) > >>ehci_hcd 0000:00:1d.7: can't reset > >>ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -95 > >>ehci_hcd: probe of 0000:00:1d.7 failed with error -95 > >>USB Universal Host Controller Interface driver v2.2 > >> > > This is also what I see (on my Asus P4P800) more or less: > > ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 23 > ehci_hcd 0000:00:1d.7: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller > ehci_hcd 0000:00:1d.7: BIOS handoff failed (104, 1010001) > ehci_hcd 0000:00:1d.7: can't reset > ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -95 > ehci_hcd: probe of 0000:00:1d.7 failed with error -95 > > The funny thing is, it has happened with various kernel snapshots > (right term for the 2.6.7-bk??-patches?) but not all. > I thought I had one (2.6.7-bk17) which didn't give this response, > but now it does, and I suspect the problem is really something else. > (Some automatic irq assignment to usb-hardware?) > > I'm not into kernel source hacking so I can't really say much more. > > Jurriaan: > > > That is most probably something in your bios. My Epox 4PCA3+ (also i875 > > chipset) says: > > Then it's in mine also. As I said in previous mail, my p4c800-e dlx works fine: --- ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 193 ehci_hcd 0000:00:1d.7: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller PCI: Setting latency timer of device 0000:00:1d.7 to 64 ehci_hcd 0000:00:1d.7: irq 193, pci mem f9968c00 ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 PCI: cache line size of 128 is not supported by device 0000:00:1d.7 ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 --- You using the latest bios version? Maybe check if there is a beta bios available ? I saw somebody said newer bios versions do not work (Locks after ACPI init). I am not sure if this is related, but for our boards you do not want ISAPNP or PNPBIOS, just ACPI (it used to oops at some stage - either after ACPI init or PNP init), and I did enable CONFIG_PNP ... --- # grep PNP .config CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # CONFIG_ISAPNP is not set # CONFIG_PNPBIOS is not set # CONFIG_BLK_DEV_IDEPNP is not set # CONFIG_IP_PNP is not set --- -- Martin Schlemmer