Additional information. I own 3 devices that use usb_storage. 1) 128Mb Wrist watch (broken) (has never worked on this machine) 2) 64Mb Pen Drive (broken) (has definitely worked before but not now) 3) HP318 Digital Camera (works fine before and works fine now except it still prints a lot of data to dmesg though that just be the verbose usb debugging`)
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
