http://bugzilla.kernel.org/show_bug.cgi?id=8572
------- Additional Comments From [EMAIL PROTECTED] 2007-06-04 00:16 ------- Created an attachment (id=11658) --> (http://bugzilla.kernel.org/attachment.cgi?id=11658&action=view) dmesg-acpi=force-apic.txt the fast case: ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 18 (level, low) -> IRQ 16 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:02:0c.0: 3Com PCI 3c905C Tornado at f881ac00. ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:00:1f.2 to 64 uhci_hcd 0000:00:1f.2: UHCI Host Controller uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1f.2: irq 17, io base 0x0000ff80 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected hda: cache flushes supported hda: hda1 hda2 hda3 hda4 <<6>ACPI: PCI Interrupt 0000:00:1f.4[C] -> GSI 23 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:1f.4 to 64 uhci_hcd 0000:00:1f.4: UHCI Host Controller uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1f.4: irq 18, io base 0x0000ff60 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected GSI 18 0000:02:0c.0[A] (eth0) 19 0000:00:1f.2[D] (usb1) (front) 23 0000:00:1f.4[C] (usb2) (rear) eth0 looks sane -- it is on IRQ18 in Legacy mode, and is on GSI18 in ACPI mode, and presumably it is working fine in both modes. usb1 also looks sane -- it is on IRQ19 in Legacy mode, and it is on GSI 19 in ACPI mode. usb2 looks broken -- it is on GSI23 in ACPI mode, and is on IRQ18 in Legacy mode. In ACPI mode there are no programmable interrupt links for this device - it is hard-coded in the _PRT, so one would expect it to have the same interrupt wire in both ACPI and Legacy mode. The other puzzle is that the issue is with the front usb ports, which were identified via e-mail as usb1, not as usb2. Please connfirm that in "acpi=off" mode, the issue is with 19: 38 IO-APIC-fasteoi uhci_hcd:usb1 and not with 18: 74 IO-APIC-fasteoi uhci_hcd:usb2, eth0 because it would make more sense if the issue were with usb2, for if usb2 were mis-configured in legacy mode such that it was taking interrupts on irq23 but looking for them on irq18, then it would only be working because the system happened to poll it when ethernet interrupts occurred. Indeed, if this were the case, you'd find that it worked better under conditions of high ethernet interrupt load, and didn't work at all if you disconnected the ethernet cable. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
