On Wed, 5 Jul 2006, Christopher Montgomery wrote:
> > Ah, okay. That's different from what I thought you meant -- the "Nobody
> > cared" message when the kernel disables an entire IRQ.
>
> Sorry; the last aside question I asked confused things because it was
> about the 'Nobody cared' message. The rest of the email was in the
> 'magic ten retries' case. I'd still like to know how to reenable a
> killed IRQ line, or rmmod usbcore. It would cut down significantly on
> reboots while debugging.
[Missed this the first time...]
I believe you can reenable a killed IRQ line simply by having a driver
request it. For example, rmmod a driver that's using the line and then
modprobe it back.
As for how to rmmod usbcore, there's nothing to it:
rmmod usbcore
The only catch is that you have to make sure usbcore isn't in use, because
the kernel won't let you unload modules that are being used. For usbcore,
this means you first have to unload all the other USB driver modules and
you have to unmount /proc/bus/usb.
Alan Stern
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
