Am Donnerstag, 10. September 2009 15:13:44 schrieb Greg Heinrich: > I am hoping that you can make something out of it. There does not seem > to be traces related with running the "dhclient" command. Instead, the > device seems to remain in suspend state. It resumes here: Sep 10 14:53:30 icera-pool6 kernel: [ 263.976289] usb 1-1: usb wakeup-resume Sep 10 14:53:30 icera-pool6 kernel: [ 263.976295] usb 1-1: finish resume Sep 10 14:53:30 icera-pool6 kernel: [ 263.976565] usb0: rxqlen 0 --> 10 Sep 10 14:53:30 icera-pool6 kernel: [ 263.976582] usb0: rxqlen 10 --> 20 Sep 10 14:53:30 icera-pool6 kernel: [ 263.976599] usb0: rxqlen 20 --> 30 Sep 10 14:53:30 icera-pool6 kernel: [ 263.976618] usb0: rxqlen 30 --> 40 Sep 10 14:53:30 icera-pool6 kernel: [ 263.976634] usb0: rxqlen 40 --> 50 Sep 10 14:53:30 icera-pool6 kernel: [ 263.976649] usb0: rxqlen 50 --> 59 Sep 10 14:53:30 icera-pool6 kernel: [ 263.977202] ehci_hcd 0000:00:1d.7: reused qh df23d200 schedule Sep 10 14:53:30 icera-pool6 kernel: [ 263.977208] usb 1-1: link qh2-0001/df23d200 start 1 [2/0 us] Sep 10 14:53:30 icera-pool6 kernel: [ 263.977230] hub 1-0:1.0: resume on port 1, status 0 Sep 10 14:53:33 icera-pool6 kernel: [ 266.816347] usb 1-1: unlink qh2-0001/df23d200 start 1 [2/0 us] Sep 10 14:53:33 icera-pool6 kernel: [ 266.818675] usb0: rxqlen 0 --> 10 Sep 10 14:53:33 icera-pool6 kernel: [ 266.818711] usb0: rxqlen 10 --> 20 Sep 10 14:53:33 icera-pool6 kernel: [ 266.818746] usb0: rxqlen 20 --> 30 Sep 10 14:53:33 icera-pool6 kernel: [ 266.818785] usb0: rxqlen 30 --> 40 Sep 10 14:53:33 icera-pool6 kernel: [ 266.818822] usb0: rxqlen 40 --> 50 Sep 10 14:53:33 icera-pool6 kernel: [ 266.818856] usb0: rxqlen 50 --> 59 Sep 10 14:53:33 icera-pool6 kernel: [ 266.818876] usb 1-1: usb auto-suspend So autoresume basically works. > Besides, dhclient is just telling me: > > DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 16 > No DHCPOFFERS received. OK, this says that dhclient thinks it's transmitting but gets no answer. For testing can you please a) repeat the test with ehci-hcd unloaded (I don't link the errors it reports) b) run "strace dhclient -d 2>/tmp/log" to get an strace of dhclient c) run lsusb -v while dhclient is running Regards Oliver PS: Please omit the log before device plugging and carve the log up into pieces at each point you do something -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
