On Tue, 24 Jan 2006, Igor Yakushin wrote: > Alan, > > > > > ============= > > > Looks like some kind interaction between disk and USB drivers? > > > > Yes, it does. I suppose you never noticed it before because without the > > patch you weren't able to use your USB devices under this kernel. > > I do not think there was any messages about the disk before. It seems to > happen only once when I > used your patch. Somehow it makes the disk and USB drivers interact.
No, that's not possible. It might make the _devices_ interact, but the _drivers_ have nothing in common. > Also, I was able to use USB > with or without your patch in about the same way: 1) trouble to connect but > sometimes it does > connect when USB device is inserted; 2) when it is connected, after a few > minutes (the longest USB > uptime I had was 1 hour) either the communication slows down to the level > that it is almost > impossible to use or USB completely disconnects. Have you ever tried setting CONFIG_USB_STORAGE_DEBUG in the kernel configuration? > > What does /proc/interrupts say? > > Currently (I returned back to 2.6.15.1 unpatched kernel): > ============ > [EMAIL PROTECTED] ~]$ cat /proc/interrupts > CPU0 CPU1 > 0: 11445913 11454859 IO-APIC-edge timer > 1: 4707 4801 IO-APIC-edge i8042 > 7: 0 2 IO-APIC-edge parport0 > 8: 0 0 IO-APIC-edge rtc > 10: 17272 17387 IO-APIC-level acpi > 12: 230252 352966 IO-APIC-edge i8042 > 15: 1894590 1897709 IO-APIC-edge ide1 > 50: 9086 8209 IO-APIC-level VIA8237, VIA82XX-MODEM > 58: 988709 1025192 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb2, > uhci_hcd:usb3, > uhci_hcd:usb4, uhci_hcd:usb5 > 66: 257699 221991 IO-APIC-level nvidia > 185: 0 1 IO-APIC-level yenta > 225: 57957 44019 IO-APIC-level libata, ohci1394 > 233: 129272 5 IO-APIC-level eth0 > NMI: 646 562 > LOC: 22900990 22900968 > ERR: 0 > MIS: 0 IRQ #225 is the ata device. (Firewire also, but that probably isn't involved.) I can't imagine how the patch could have caused unhandled interrupts on that vector. > I wonder though if those crashes might damage hardware? Very unlikely. > Might it be that we are on the wrong track here and it is not a > kernel/module/driver but a > configuration problem? What are the relevant configuration files to check? There aren't any. > Also my system has so many different USB devices: webcam, bluetooth with > wireless, 4 USB ports, 10 > in 1 card reader (which I disabled in Bios for now) and probably something > else... Might they > interefere with each other somehow? Maybe some kernel parameters might help? No kernel parameters used by the USB stack will help. Maybe turning off ACPI will make a difference. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
