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.
In 2.4.21 I used the module uhci for my usb driver. (I think that was a question.) Is this possible to have my usb port be broken yet have it work for other types of devices? 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 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) uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 [ced0f270] link (0ed0f1e2) element (0eb7f100) 0: [ceb7f100] link (0eb7f140) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=00ef4e80) 1: [ceb7f140] link (0eb7f180) e3 SPD Active Length=0 MaxLen=1 DT1 EndPt=0 Dev=3, PID=69(IN) (buf=025996a0) 2: [ceb7f180] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=3, PID=e1(OUT) (buf=00000000) 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) usb-storage: Transport: Bulk usb-storage: Protocol: Transparent SCSI usb-storage: Endpoints: In: 0xc34efd74 Out: 0xc34efd60 Int: 0x00000000 (Period 0) usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1 uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 [ced0f270] link (0ed0f1e2) element (0eb7f100) 0: [ceb7f100] link (0eb7f140) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=0ee6e020) 1: [ceb7f140] link (0eb7f180) e3 SPD Active Length=0 MaxLen=0 DT1 EndPt=0 Dev=3, PID=69(IN) (buf=09447000) 2: [ceb7f180] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=3, PID=e1(OUT) (buf=00000000) usb-storage: GetMaxLUN command result is -110, data is 0 usb-storage: *** thread sleeping. scsi0 : SCSI emulation for USB Mass Storage devices usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command INQUIRY (6 bytes) usb-storage: 12 00 00 00 24 00 usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code -110; transferred 31/31 usb-storage: -- timeout or NAK usb-storage: Bulk command transfer result=4 usb-storage: -- transport indicates error, resetting usb-storage: usb_stor_Bulk_reset called usb-storage: usb_stor_control_msg: rq=ff rqtype=21 value=0000 index=00 len=0 uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 [ced0f270] link (0ed0f1e2) element (0eb7f080) 0: [ceb7f080] link (0eb7f0c0) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=0ee6e020) 1: [ceb7f0c0] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=3, PID=69(IN) (buf=00000000) usb-storage: Soft reset failed: -110 usb-storage: scsi cmd done, result=0x70000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command INQUIRY (6 bytes) usb-storage: 12 00 00 00 24 00 usb-storage: Bulk Command S 0x43425355 T 0x2 L 36 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code -110; transferred 31/31 usb-storage: -- timeout or NAK usb-storage: Bulk command transfer result=4 usb-storage: -- transport indicates error, resetting usb-storage: usb_stor_Bulk_reset called usb-storage: usb_stor_control_msg: rq=ff rqtype=21 value=0000 index=00 len=0 uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 [ced0f270] link (0ed0f1e2) element (0eb7f080) 0: [ceb7f080] link (0eb7f0c0) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=0ee6e020) 1: [ceb7f0c0] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=3, PID=69(IN) (buf=00000000) usb-storage: Soft reset failed: -110 usb-storage: scsi cmd done, result=0x70000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command INQUIRY (6 bytes) usb-storage: 12 00 00 00 24 00 usb-storage: Bulk Command S 0x43425355 T 0x3 L 36 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code -110; transferred 31/31 usb-storage: -- timeout or NAK usb-storage: Bulk command transfer result=4 usb-storage: -- transport indicates error, resetting usb-storage: usb_stor_Bulk_reset called usb-storage: usb_stor_control_msg: rq=ff rqtype=21 value=0000 index=00 len=0 uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 [ced0f270] link (0ed0f1e2) element (0eb7f080) 0: [ceb7f080] link (0eb7f0c0) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=0ee6e020) 1: [ceb7f0c0] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=3, PID=69(IN) (buf=00000000) usb-storage: Soft reset failed: -110 usb-storage: scsi cmd done, result=0x70000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (1:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (2:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (3:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (4:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (5:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (6:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Bad target number (7:0) usb-storage: scsi cmd done, result=0x40000 usb-storage: *** thread sleeping. WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 drivers/usb/core/usb.c: registered new driver usb-storage USB Mass Storage support registered. On Fri, 12 Mar 2004, Alan Stern wrote: > On Thu, 11 Mar 2004, Jerry Kilpatrick wrote: > > > Disclaimer: This is, at max, the second time I've ever submitted a bug, > > so I am doing the very best to do it all correctly. > > You did a good job, lots of useful information included. > > > I've attached my config.gz that was in /proc as well. Let me know if I > > can give you anything else to help. > > > > PROBLEM: > > When I plug my watch (a usb 128Mb flash drive) or any other > > similar devices into one machine, usb_storage spews out a bunch of data, > > and though I can mount the device, any writing and unmount does nothing > > but show errors and does not commit any changes. This happens in every > > 2.6.X kernel I've used, but worked perfect in 2.4.X, however it works > > fine in another similarly configured 2.6 machine. > > Do you still have a 2.4 kernel on that non-working machine, and does the > drive still operate correctly under 2.4? I ask because it's possible > that the USB interface on that computer is just broken. > > Also, which UHCI driver under 2.4 do you use? > > > FULL DESCRIPTION: > > While running 2.6.3 on two separate machines, the non-working one using > > the uhci_hcd driver and the working one using ohci_hcd though I'm not sure > > that makes a huge difference. I have removed all unneccessary modules, > > loaded simply uhci_hcd/ohci_hcd depending on the machine (and I'm not sure > > if I should be able to or not, but I can not switch those around, one > > machine only works with uhci the other only work with ohci. Then I load > > usb_storage and plug in the device. The working one send the following to > > dmesg: > > ... all looks normal ... > > > The bad one send this to dmesg: > > uhci_hcd 0000:00:07.2: UHCI Host Controller > > uhci_hcd 0000:00:07.2: irq 11, io base 0000fce0 > > uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 > > hub 1-0:1.0: USB hub found > > hub 1-0:1.0: 2 ports detected > > hub 1-0:1.0: over-current change on port 2 > > That line is suspect; it shouldn't occur and it's the only unexpected > thing here. > > > usb 1-1: new full speed USB device using address 2 > > SCSI subsystem initialized > > Initializing USB Mass Storage driver... > > usb-storage: USB Mass Storage device detected > > usb-storage: act_altsetting is 0, id_index is 117 > > usb-storage: -- associate_dev > > drivers/usb/core/message.c: error getting string descriptor 0 (error=-110) > > drivers/usb/core/message.c: error getting string descriptor 0 (error=-110) > > drivers/usb/core/message.c: error getting string descriptor 0 (error=-110) > > I'll omit the rest; it merely shows that every single attempt at further > communication with the drive failed. The question is, why should it fail > now when it must have succeeded during initial device detection and > enumeration? > > > On the good one, everything works as expected. On the uhci_hcd one that > > doesn't work. I can mount the device, and copy files off of it, but > > writing anything to it causes similar errors that just seem to flow like > > water. When I write any data I eventually get an IO error at the command > > line and when I umount the partition all changes I had made never get > > commited to the storage device. > > I can't believe you would have been able to read files from the drive > during the session when the system log above was created. The SCSI system > would not even have created a device node for it. Apart from that, > everything you describe as what one would expect given that the > usb-storage driver was unable to communicate with the drive. > > > All of this works fine in 2.4.X, and was > > broken by at LEAST 2.6.1 if not the 2.6.0-test series when I first > > switched over. > > Here's what you can do to get more information: Turn on USB debugging in > your kernel's configuration and rebuild the USB drivers. Then post the > dmesg log you get, with all its debugging messages. Never mind the > working computer, just concentrate on the one that doesn't work. > > One other thing. Before you load the usb-storage driver, and then again > after it fails, get a copy of the /proc/driver/uhci/0000:00:07.2 file, > and post the two sets of contents. > > 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
