(It's easier to follow the conversation if you insert your replies in-line with the previous message, like I do in this reply. Don't top-post.)
On Fri, 12 Mar 2004, Jerry Kilpatrick wrote: > I hate coincidences, but I'm still confused. > > I reverted back to last 2.4 kernel which happened to be 2.4.21 with the > preempt patch and software suspend patch installed. I plugged in my usb > storage device and it did the same thing. I was able to mount it and read > from it, but was unable to write or anything to it. So it appears that > something had happened to my uhci? However, I can plug other devices such > as keyboards, mice, and usb/serial cable and they work perfectly fine. Maybe there's something wrong with the device, not the computer's interface. > In 2.4.21 I used the module uhci for my usb driver. (I think that was a > question.) Yes. Less relevant now that we know it behaves the same way as the 2.6 driver. > Is this possible to have my usb port be broken yet have it work for other > types of devices? It's pretty unlikely. Much more probably your storage device is broken. That could easily explain, for instance, why reads work but writes fail. > Thanks again for the help. > > In case there still may be some problem here is the rest of the > information you had requested. > > /proc/driver/uhci/00:00:07.2 BEFORE FAILURE: > HC status > usbcmd = 00c1 Maxp64 CF RS > usbstat = 0000 > usbint = 000f > usbfrnum = (1)030 > flbaseadd = 0e510030 > sof = 40 > stat1 = 0095 Enabled Connected > stat2 = 0480 OverCurrent > Frame List > Skeleton QH's > > /proc/driver/uhci/00:00:07.2 AFTER FAILURE: > HC status > usbcmd = 00c1 Maxp64 CF RS > usbstat = 0000 > usbint = 000f > usbfrnum = (1)bb0 > flbaseadd = 0e510bb0 > sof = 40 > stat1 = 0095 Enabled Connected > stat2 = 0480 OverCurrent > Frame List > Skeleton QH's No significant changes (the usbfrnum and flbaseadd values constantly update during normal use). I'm still concerned about that overcurrent indicator on the stat2 lines. Does your computer have two USB ports or only one? I ask because with some models (laptops mostly) the manufacturer only puts in a single port, even though the USB controller is capable of handling two ports. Sometimes in a misguided attempt to disable the unused second port, they hardwire the overcurrent input on. (HP in particular has been known to do this.) Just out of curiousity, what does this file say before you plug in your storage device? > USB-STORAGE WITH USB DEBUGGING: > Initializing USB Mass Storage driver... > usb-storage 1-1:1.0: usb_probe_interface > usb-storage 1-1:1.0: usb_probe_interface - got id > usb-storage: USB Mass Storage device detected > usb-storage: act_altsetting is 0, id_index is 117 > usb-storage: -- associate_dev > uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 > [ced0f240] link (0ed0f1e2) element (0eb7f040) > 0: [ceb7f040] link (0eb7f080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 > EndPt=0 Dev=3, PID=2d(SETUP) (buf=00ef4e80) > 1: [ceb7f080] link (0eb7f0c0) e3 SPD Active Length=0 MaxLen=1 DT1 > EndPt=0 Dev=3, PID=69(IN) (buf=025996a0) > 2: [ceb7f0c0] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 > EndPt=0 Dev=3, PID=e1(OUT) (buf=00000000) Same as before, I'll skip the rest. It's still not clear why these requests fail when similar ones must have succeeded at the time you plugged in the device. However it is clear that during the session where you recorded that log, you would not have been able to read from the device. Do you have a debugging log from a session where you could read but couldn't write? Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
