On Thu, 23 Nov 2000, Michael Elkins wrote:
Usb controller is sharing a interrupt with the emu10k1.
For what I know the emu10k1 driver doesn't have any problem
sharing irq's, so I would blame the usb driver...
Rui Sousa
> 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00
>[UHCI])
> 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: 64
> Interrupt: pin D routed to IRQ 9
> Region 4: I/O ports at 10c0 [size=32]
>
...
>
> 00:10.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev 07)
> Subsystem: Creative Labs CT4780 SBLive! Value
> 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: 64 (500ns min, 5000ns max)
> Interrupt: pin A routed to IRQ 9
> Region 0: I/O ports at 10e0 [size=32]
> Capabilities: [dc] Power Management version 1
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
>PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:10.1 Input device controller: Creative Labs SB Live! (rev 07)
> Subsystem: Creative Labs Gameport Joystick
> 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: 64
> Region 0: I/O ports at 1428 [size=8]
> Capabilities: [dc] Power Management version 1
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
>PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
...
>
> [X.] Other notes, patches, fixes, workarounds:
>
> Loading the usb-uhci module before the emu10k1 driver seems to work. I tested
> playing audio while accessing images from my digital camera via USB with
> no errors.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
