Just a quick note about problems I observed with RC2 ... I don't have
time to track it down just yet unfortunately, so what we have here is
just some bug reporting.
0 Connect an FT232B based device to root hub, it's handed to OHCI.
(The problem has nothing to do with that device or its driver.)
1 Hotplugs to ftdi_sio, ok that's as expected. (But, advance notice
of a glitch: it uses address 3, not address 2, despite being the
first device connected to this root hub ...)
2 Now rmmod ftdi_sio, since this needs to use libftdi to bitbang
some stuff before rs232 connections can be useful.
3 Run userspace tool that connects via usbfs ... and now the
device instantly gets kicked off. The device can't be used
with usbfs any more !!
4 Hey, this sucks ... the device now has ftdi_sio bound to it,
completely the wrong result.
5 Goto 2 ... or if after disabling hotplug for the ftdi_sio driver,
just repeat 3 forever.
It seems that every time a device enumerates, it autosuspends until
a driver appears, then it's kicked off and must re-enumerate (hence
address 3 not 2).
The can't-work-with-this regression is that this means nothing
which needs usbfs can work with OHCI any more. That seems to be
a secondary failure though -- side effect of autosuspend bugs.
Now, the first clue I can offer is that when I looked at the OHCI
root hub in this "autosuspend" state, it was clearly in a bogus
state, since the root hub was not correctly suspended ... it was
not in the SUSPENDED state. (A regression.) I'm speculating
that's the root cause of the other regression, with usbfs.
Anyway, that's it for the moment ... annotated dmesg output is
attached, and I'm reverting to an older kernel for now.
- Dave
Port handed off from EHCI to OHCI, enumerates as address #2:
ohci_hcd 0000:00:02.1: wakeup
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00010101 CSC PPS CCS
hub 3-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: new full speed USB device using ohci_hcd and address 2
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.2_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.2_ep81
PM: Adding info for No Bus:usbdev3.2_ep02
drivers/usb/core/inode.c: creating file '002'
No driver yet, so ...
usb 3-1: usb auto-suspend
At which point -- based on later observation -- the problem
seems to be that the root hub is in a bogus state:
- port 1 enabled and suspended
- ports 2 and 3 unconnected
- root hub OPERATIONAL not SUSPENDED
I'm speculating that last is the root cause of the other issues
here ... it's a regression, since previously the driver would have
(properly) put the controller into its low power state.
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB
Serial Device
ftdi_sio 3-1:1.0: usb_probe_interface
ftdi_sio 3-1:1.0: usb_probe_interface - got id
... now there's a driver, so ...
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
That is, status == POWER, SUSPEND, ENABLE, CONNECTION.
The port was never resumed ... I'm guessing that the root hub
resume path never got executed since the root hub didn't get
suspended, it of course couldn't be resumed, ergo confusion ...
And in this case the confusion was _partially_ recovered
from by disconnecting the device:
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 2
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.2_ep81
usbdev3.2_ep81: ep_device_release called for usbdev3.2_ep81
PM: Removing info for No Bus:usbdev3.2_ep02
usbdev3.2_ep02: ep_device_release called for usbdev3.2_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.2_ep00
usbdev3.2_ep00: ep_device_release called for usbdev3.2_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
Dunno if this is a regression, but it's clearly wrong to have
a disconnect _not_ involve the port going back to EHCI ... it
may be because "logical" disconnect was (wrongly) invoked, and
that doesn't do the full dance.
At any rate, next we see a normal enumeration with the device
getting a NEW ADDRESS, and bound to ftdi_sio. Binding is fine,
the enumeration (and new address) is not.
usb 3-1: new full speed USB device using ohci_hcd and address 3
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.3_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
ftdi_sio 3-1:1.0: usb_probe_interface
ftdi_sio 3-1:1.0: usb_probe_interface - got id
ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT232BM
PM: Adding info for usb-serial:ttyUSB0
usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
PM: Adding info for No Bus:usbdev3.3_ep81
PM: Adding info for No Bus:usbdev3.3_ep02
drivers/usb/core/inode.c: creating file '003'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
rmmod ftdi_sio ...
usbcore: deregistering interface driver ftdi_sio
ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
PM: Removing info for usb-serial:ttyUSB0
ftdi_sio 3-1:1.0: device disconnected
PM: Removing info for No Bus:usbdev3.3_ep81
usbdev3.3_ep81: ep_device_release called for usbdev3.3_ep81
PM: Removing info for No Bus:usbdev3.3_ep02
usbdev3.3_ep02: ep_device_release called for usbdev3.3_ep02
PM: Adding info for No Bus:usbdev3.3_ep81
PM: Adding info for No Bus:usbdev3.3_ep02
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver FTDI USB
Serial Device
usb 3-1: usb auto-suspend
... start userspace program with usbfs, and the same
driver-bind-triggers-disconnect bug appears.
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 3
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.3_ep81
usbdev3.3_ep81: ep_device_release called for usbdev3.3_ep81
PM: Removing info for No Bus:usbdev3.3_ep02
usbdev3.3_ep02: ep_device_release called for usbdev3.3_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.3_ep00
usbdev3.3_ep00: ep_device_release called for usbdev3.3_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
... nope, not a NEW device, the same old one being mis-handled.
Of course since a NEW ADDRESS was assigned, the usbfs file
descriptor was invalidated; 003/003 stopped working almost
as soon as the userspace code had opened it.
usb 3-1: new full speed USB device using ohci_hcd and address 4
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.4_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.4_ep81
PM: Adding info for No Bus:usbdev3.4_ep02
drivers/usb/core/inode.c: creating file '004'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
usb 3-1: usb auto-suspend
So here usbfs has been kicked off, and there's no driver.
But we got a new hotplug event, so ftdi_sio is modprobed.
We've seen this re-enumerate-before-binding-driver before ...
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB
Serial Device
ftdi_sio 3-1:1.0: usb_probe_interface
ftdi_sio 3-1:1.0: usb_probe_interface - got id
usb 3-1: usb auto-resume
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
usb 3-1: finish resume
ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT232BM
PM: Adding info for usb-serial:ttyUSB0
usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
usbcore: deregistering interface driver ftdi_sio
ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
PM: Removing info for usb-serial:ttyUSB0
ftdi_sio 3-1:1.0: device disconnected
PM: Removing info for No Bus:usbdev3.4_ep81
usbdev3.4_ep81: ep_device_release called for usbdev3.4_ep81
PM: Removing info for No Bus:usbdev3.4_ep02
usbdev3.4_ep02: ep_device_release called for usbdev3.4_ep02
PM: Adding info for No Bus:usbdev3.4_ep81
PM: Adding info for No Bus:usbdev3.4_ep02
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver FTDI USB
Serial Device
usb 3-1: usb auto-suspend
... again bogus disconnect.
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 4
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.4_ep81
usbdev3.4_ep81: ep_device_release called for usbdev3.4_ep81
PM: Removing info for No Bus:usbdev3.4_ep02
usbdev3.4_ep02: ep_device_release called for usbdev3.4_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.4_ep00
usbdev3.4_ep00: ep_device_release called for usbdev3.4_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
... and bogus re-enumerate ...
usb 3-1: new full speed USB device using ohci_hcd and address 5
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.5_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.5_ep81
PM: Adding info for No Bus:usbdev3.5_ep02
drivers/usb/core/inode.c: creating file '005'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
usb 3-1: usb auto-suspend
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB
Serial Device
ftdi_sio 3-1:1.0: usb_probe_interface
ftdi_sio 3-1:1.0: usb_probe_interface - got id
usb 3-1: usb auto-resume
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
usb 3-1: finish resume
ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT232BM
PM: Adding info for usb-serial:ttyUSB0
usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
usbcore: registered new interface driver ftdi_sio
But I **still** don't want ftdi_sio bound to this device, at
least not until some bitbang operations complete.
rmmod ftdi_sio, and the whole ugly dance repeats forever.
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
usbcore: deregistering interface driver ftdi_sio
ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
PM: Removing info for usb-serial:ttyUSB0
ftdi_sio 3-1:1.0: device disconnected
PM: Removing info for No Bus:usbdev3.5_ep81
usbdev3.5_ep81: ep_device_release called for usbdev3.5_ep81
PM: Removing info for No Bus:usbdev3.5_ep02
usbdev3.5_ep02: ep_device_release called for usbdev3.5_ep02
PM: Adding info for No Bus:usbdev3.5_ep81
PM: Adding info for No Bus:usbdev3.5_ep02
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver FTDI USB
Serial Device
usb 3-1: usb auto-suspend
At this point /etc/modprobe.conf grew a new entry to maybe help,
me having noticed some of the pattern above:
alias ftdi_sio none
So from here on, it's only userspace trying to talk to the device
using /proc/bus/usb/003/... paths. With a total lack of success;
which is the more obvious of the two regressions shown here.
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 5
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.5_ep81
usbdev3.5_ep81: ep_device_release called for usbdev3.5_ep81
PM: Removing info for No Bus:usbdev3.5_ep02
usbdev3.5_ep02: ep_device_release called for usbdev3.5_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.5_ep00
usbdev3.5_ep00: ep_device_release called for usbdev3.5_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: new full speed USB device using ohci_hcd and address 6
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.6_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.6_ep81
PM: Adding info for No Bus:usbdev3.6_ep02
drivers/usb/core/inode.c: creating file '006'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
usb 3-1: usb auto-suspend
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 6
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.6_ep81
usbdev3.6_ep81: ep_device_release called for usbdev3.6_ep81
PM: Removing info for No Bus:usbdev3.6_ep02
usbdev3.6_ep02: ep_device_release called for usbdev3.6_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.6_ep00
usbdev3.6_ep00: ep_device_release called for usbdev3.6_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: new full speed USB device using ohci_hcd and address 7
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.7_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.7_ep81
PM: Adding info for No Bus:usbdev3.7_ep02
drivers/usb/core/inode.c: creating file '007'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
usb 3-1: usb auto-suspend
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 7
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.7_ep81
usbdev3.7_ep81: ep_device_release called for usbdev3.7_ep81
PM: Removing info for No Bus:usbdev3.7_ep02
usbdev3.7_ep02: ep_device_release called for usbdev3.7_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.7_ep00
usbdev3.7_ep00: ep_device_release called for usbdev3.7_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: new full speed USB device using ohci_hcd and address 8
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.8_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.8_ep81
PM: Adding info for No Bus:usbdev3.8_ep02
drivers/usb/core/inode.c: creating file '008'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
usb 3-1: usb auto-suspend
usb 3-1: usb auto-resume
hub 3-0:1.0: port 1 status 0000.0107 after resume, 0
hub 3-0:1.0: logical disconnect on port 1
hub 3-0:1.0: state 7 ports 3 chg 0002 evt 0000, resume root
usb 3-1: can't resume, status -19
hub 3-0:1.0: port 1, status 0107, change 0000, 12 Mb/s
usb 3-1: USB disconnect, address 8
usb 3-1: unregistering device
usb 3-1: usb_disable_device nuking all URBs
usb 3-1: unregistering interface 3-1:1.0
PM: Removing info for No Bus:usbdev3.8_ep81
usbdev3.8_ep81: ep_device_release called for usbdev3.8_ep81
PM: Removing info for No Bus:usbdev3.8_ep02
usbdev3.8_ep02: ep_device_release called for usbdev3.8_ep02
PM: Removing info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Removing info for No Bus:usbdev3.8_ep00
usbdev3.8_ep00: ep_device_release called for usbdev3.8_ep00
PM: Removing info for usb:3-1
usb 3-1: uevent
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS
PES CCS
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: new full speed USB device using ohci_hcd and address 9
ohci_hcd 0000:00:02.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS
PES CCS
usb 3-1: ep0 maxpacket = 8
usb 3-1: default language 0x0409
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: USB <-> Serial
usb 3-1: Manufacturer: FTDI
PM: Adding info for usb:3-1
usb 3-1: uevent
usb 3-1: usb_probe_device
PM: Adding info for No Bus:usbdev3.9_ep00
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: adding 3-1:1.0 (config #1, interface 0)
PM: Adding info for usb:3-1:1.0
usb 3-1:1.0: uevent
PM: Adding info for No Bus:usbdev3.9_ep81
PM: Adding info for No Bus:usbdev3.9_ep02
drivers/usb/core/inode.c: creating file '009'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0002, resume root
usb 3-1: usb auto-suspend
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
