On Sat, 5 Nov 2005, Charles Shannon Hendrix wrote:
> Sat, 05 Nov 2005 @ 15:54 -0500, Alan Stern said:
>
> > You still have a syslog configuration problem. You're sending the
> > debug-level messages to /var/log/debug and everything else to
> > /var/log/syslog, or something like that?
>
> It's Slackware's default setup.
>
> I understand it isn't your preference, but personally I like it this
> way.
It's bad because there's no way to tell the relative order of lines
between the different files. If each log file has a line timestamped
16:34:41, which one came first?
Not to mention that you need to read through three different places in the
email message concurrently to see what's going on.
> Here are the messages generated by plugging the iPod into the USB port,
> and then removing it.
>
> When I plug the device in, these log entries are generated:
> ==> debug <==
> Nov 5 16:34:40 daydream kernel: hub 1-0:1.0: state 5 ports 8 chg 0000 evt
> 0100
> Nov 5 16:34:40 daydream kernel: ehci_hcd 0000:00:10.4: GetStatus port 8
> status 001803 POWER sig=j CSC CONNECT
> Nov 5 16:34:40 daydream kernel: hub 1-0:1.0: port 8, status 0501, change
> 0001, 480 Mb/s
> Nov 5 16:34:40 daydream kernel: hub 1-0:1.0: debounce: port 8: total 100ms
> stable 100ms status 0x501
> Nov 5 16:34:40 daydream kernel: ehci_hcd 0000:00:10.4: port 8 high speed
> Nov 5 16:34:40 daydream kernel: ehci_hcd 0000:00:10.4: GetStatus port 8
> status 001005 POWER sig=se0 PE CONNECT
> Nov 5 16:34:40 daydream kernel: ehci_hcd 0000:00:10.4: devpath 8 ep0in
> 3strikes
> Nov 5 16:34:40 daydream last message repeated 2 times
This means the iPod is failing to reply to a packet. Possibly it needs a
longer delay after plugging in before it's ready to operate. You could
try an experiment to see if that's the problem. Edit the kernel source
file drivers/usb/core/hub.c. In the hub_port_init routine, following each
of the calls to hub_port_reset, add a call to
msleep(500);
(substitute however many milliseconds you think the iPod may require in
place of the 500).
> ==> syslog <==
> Nov 5 16:34:41 daydream kernel: usb 1-8: device descriptor read/64, error -71
> Nov 5 16:34:41 daydream last message repeated 3 times
> Nov 5 16:34:42 daydream kernel: usb 1-8: device not accepting address 18,
> error -71
> Nov 5 16:34:42 daydream kernel: usb 1-8: device not accepting address 19,
> error -71
These messages indicate which packets the iPod wasn't responding to.
See what I mean about it being better to have these inline with the
others?
> ...and these are the messages logged when removing the iPod:
>
> ==> messages <==
> Nov 5 16:34:52 daydream shannon: REMOVING IPOD FROM PORT 5
>
> ==> debug <==
> Nov 5 16:34:42 daydream kernel: ehci_hcd 0000:00:10.4: devpath 8 ep0out
> 3strikes
> Nov 5 16:34:54 daydream kernel: hub 1-0:1.0: state 5 ports 8 chg 0000 evt
> 0100
> Nov 5 16:34:54 daydream kernel: ehci_hcd 0000:00:10.4: GetStatus port 8
> status 001002 POWER sig=se0 CSC
> Nov 5 16:34:54 daydream kernel: hub 1-0:1.0: port 8, status 0100, change
> 0001, 12 Mb/s
> Nov 5 16:34:54 daydream kernel: hub 1-0:1.0: debounce: port 8: total 100ms
> stable 100ms status 0x100
These messages are normal for an unplug.
Alan Stern
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
