On Mon, 28 Jun 2004, Zan Lynx wrote: > I don't have any other systems with VIA USB controllers to try. > > I have not been able to get the USB controller onto its own IRQ, but I > might have another clue. The problem seems to get especially bad under > heavy disk load. That would mean a lot of shared interrupts happening. > > I've never tried using BK before, but I'm always willing to learn new > things. How can I find what patch sets were applied to the USB and > Input systems, so I can track down exactly what changed between 2.6.5 > and 2.6.7? Once I track down the patch that causes this, the problem > should become more obvious.
It's not actually all that easy. The difficulty is that the change sets aren't neatly divided up into "before 2.6.7" and "after 2.6.5" categories. An easier way to start might be to take the entire USB stack from 2.6.5 and put it into 2.6.7. That is, everything below drivers/usb plus include/linux/usb*. If you do that and the mouse still doesn't work right, that proves the problem lies outside the USB domain, quite likely in the interrupt management code. Of course, if the mouse does work then you can try mixing and matching sub-pieces. For instance, you could try the UHCI driver (drivers/usb/host/uhci*) from 2.6.5 and everything else from 2.6.7. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
