[lkml]   [2006]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.15-mm3 [USB lost interrupt bug]

    On 12/01/2006 5:33 p.m., Andrew Morton wrote:

    >> hub 5-0:1.0: USB hub found
    >> hub 5-0:1.0: 2 ports detected
    >> Initializing USB Mass Storage driver...
    >> irq 193: nobody cared (try booting with the "irqpoll" option)
    >> [<c01041d9>] dump_stack+0x17/0x19
    >> [<c0139f47>] __report_bad_irq+0x27/0x83
    >> [<c013a021>] note_interrupt+0x7e/0x21d
    >> [<c0139af4>] __do_IRQ+0xd3/0xef
    >> [<c0105038>] do_IRQ+0x3d/0x57
    >> =======================
    >> [<c0103686>] common_interrupt+0x1a/0x20
    >> [<c0101bc4>] cpu_idle+0x63/0x78
    >> [<c0100615>] rest_init+0x23/0x2e
    >> [<c03d070f>] start_kernel+0x2ca/0x34b
    >> [<c0100210>] 0xc0100210
    >> handlers:
    >> [<c027017e>] (usb_hcd_irq+0x0/0x56)
    >> Disabling IRQ #193
    > USB lost its interrupt. Could be USB, more likely ACPI.

    I've seen this one happen nearly every boot since then including bootups that
    are otherwise OK (no oopses), so it's probably worth more looking into rather
    than being written off as a 'once off':

    uhci_hcd 0000:00:1d.3: Unlink after no-IRQ? Controller is probably using the
    wrong IRQ.



    ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
    PCI: Setting latency timer of device 0000:00:1d.3 to 64
    uhci_hcd 0000:00:1d.3: UHCI Host Controller
    uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
    uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800

    lspci -vv

    00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
    USB UHCI #4 (rev 03) (prog-if 00 [UHCI])
    Subsystem: Intel Corporation Unknown device 4356
    Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    Stepping- SERR- FastB2B-
    Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
    <TAbort- <MAbort- >SERR- <PERR-
    Latency: 0
    Interrupt: pin D routed to IRQ 169
    Region 4: I/O ports at d800 [size=32]

    It's a new regression to -mm3.

    For the ACPI people - I can't test with ACPI off because the machine won't boot
    without ACPI :( [see for what happens
    with acpi=off].
    I'm not even sure if inability to boot with acpi=off is a bug or not - would
    appreciate if someone can let me know.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-01-12 09:57    [W:0.041 / U:7.092 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site