On Wed, 6 Oct 2004, Steve Krulewitz wrote: > David & Alan -- > > Thanks for all of your comments on my problem so fat. Sorry for the > delay but I have been away. Below is the debug output when I plug my > iPod in after removing the ehci module. Now I can't even mount it at > all (which used to work after removing ehci), but this could be due to > the fs corruption, even though the iPod still works OK. > > Here is the debug log starting with me removing the ehci module:
The log shows that the first connection attempt failed because the iPod didn't respond to the SET ADDRESS command. > Oct 6 09:10:12 doolittle kernel: uhci_hcd 0000:00:1d.1: port 2 portsc 0082 > Oct 6 09:10:12 doolittle kernel: hub 2-0:1.0: port 2, status 0100, > change 0001, 12 Mb/s > Oct 6 09:10:12 doolittle kernel: hub 2-0:1.0: debounce: port 2: total > 100ms stable 100ms status 0x100 > Oct 6 09:10:13 doolittle kernel: uhci_hcd 0000:00:1d.1: suspend_hc Then the iPod really did disconnect itself from the bus. > Oct 6 09:10:13 doolittle kernel: uhci_hcd 0000:00:1d.1: wakeup_hc > Oct 6 09:10:13 doolittle kernel: uhci_hcd 0000:00:1d.1: port 2 portsc 0083 > Oct 6 09:10:13 doolittle kernel: hub 2-0:1.0: port 2, status 0101, > change 0001, 12 Mb/s > Oct 6 09:10:13 doolittle kernel: hub 2-0:1.0: debounce: port 2: total > 100ms stable 100ms status 0x101 > Oct 6 09:10:13 doolittle kernel: usb 2-2: new device strings: Mfr=51, > Product=70, SerialNumber=57 > Oct 6 09:10:13 doolittle kernel: usb 2-2: default language 0x0409 > Oct 6 09:10:13 doolittle kernel: usb 2-2: hotplug > Oct 6 09:10:13 doolittle kernel: usb 2-2: adding 2-2:1.0 (config #1, > interface 0) > Oct 6 09:10:13 doolittle kernel: usb 2-2:1.0: hotplug > Oct 6 09:10:14 doolittle kernel: ub 2-2:1.0: usb_probe_interface > Oct 6 09:10:14 doolittle kernel: ub 2-2:1.0: usb_probe_interface - got id The second connect attempt worked correctly. > Below are the messages I'm seeing in dmesg which seems to have to do > with the inablity now to mount the iPod: > > uba: device 4 capacity nsec 50 bsize 512 > uba: made changed > uba: device 4 capacity nsec 50 bsize 512 > uba: device 4 capacity nsec 50 bsize 512 > uba:end_request: I/O error, dev uba, sector 0 > Buffer I/O error on device uba, logical block 0 > end_request: I/O error, dev uba, sector 2 What happens if you use the usb-storage driver rather than the ub driver? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
