Disabling IRQ #11 when loading ehci-hcd !!

Submitted by deb75

on June 30, 2004 - 2:37am

Linux kernel

hello,

I currently run the 2.6.7 kernel,
my ship is nvidia nforce2,

I have an USB2.0 printer, when loading ehci-hcd USB2.0 driver
it answered "Disabling IRQ #11", it did not hang, and the module was effectively loaded, but I could not reach my printer ( although it worked with 2.6.6 kernel )

I discovered that I had also the ethernet driver (forcedeth)
that was on IRQ 11, and after loading ehci-hcd I could
not reach the net anymore too

It seems there is an IRQ conflict, I wonder why this
did not appear before,

does someone know how to fix it ??
is it possible to assign to either forcedeth or ehci-hcd
a different IRQ so that they do not clash ?

I heard that this could be also done in bios, but not
sure

every piece of advice are welcome

thanks in advance
deb75

I've had a similar issue with

Anonymous

July 2, 2004 - 6:16pm

I've had a similar issue with my computer of late:

motherboard: MSI K7N2-ILSR (nforce2 chipset)
kernel: Fedora Core (2.6.6-1.435.2.1)

it seems that if I have my MS Natural keyboard (which has a USB hub on board) plugged in to one particular port on the motherboard I get this issue (IRQ #11 disabled when loading ehci-hcd) and the onboard sound stops working. The keyboard has my printer (epson C63) plugged into the on-board USB hub.

What I've found for now (I'm not suggesting this as a permanent solution) is that disabling USB2 support in the BIOS (limiting it to 1.1) solves the problem and things start working again. Plugging the keyboard's USB hub into another port on the motherboard also solved the problem.

I suspect I've had similar problems with win2k as well, although in windows it manifested itself as strange intermittent failures to communicate with USB devices rather than actually telling me that IRQ11 was getting hammered when the USB2 drivers were loaded :]

Anyway,

Good luck finding out what's actually happening here.. Sorry I couldn't be more help :)

Try the Gentoo forums

Hydroxides

July 3, 2004 - 7:07am

There has been a discussion about what seems to be the same / very similar issue to your problems on the Gentoo forums.

http://forums.gentoo.org/viewtopic.php?t=188410

I did have a notice in dmesg at one point about disabling interrupts (#11 I think) but this was solved by disabling IEEE 1394 in BIOS as I had no drivers built for it Linux.

HTH.

thanks for answeering, I w

deb75

July 5, 2004 - 5:13am

thanks for answeering,

I went around internet, looking for the trouble ...

finally it seemed to be rather a kernel issue ( especially of ehci_hcd )
than a hardware or bios issue,

this trouble does not show up any more with 2.6.7-bk16 kernel,
and one can read the changelog to see what the trouble was