On Sat, 14 Jan 2012, Tim Coote wrote: > On 13 Jan 2012, at 15:34, Alan Stern wrote: > [snip] > > > > It may be something like usb_modeswitch, or a program invoked by a udev > > rule. Or it could be a modem manager. > > > > Something that might help is to enable the usbfs_snoop module parameter > > for usbcore before plugging in the device: > > > > echo 1 >/sys/module/usbcore/parameters/usbfs_snoop > > > > That will add a bunch of output to the system log, including the names > > of programs that directly access USB devices. > Here's what I got: > Jan 14 10:50:49 pluto kernel: [ 4622.452049] usb 3-2: new full speed USB device number 2 using uhci_hcd > Jan 14 10:50:49 pluto kernel: [ 4622.684080] usb 3-2: New USB device found, idVendor=0451, idProduct=3410 > Jan 14 10:50:49 pluto kernel: [ 4622.684089] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Jan 14 10:50:49 pluto kernel: [ 4622.684097] usb 3-2: Product: TUSB3410 Boot Device > Jan 14 10:50:49 pluto kernel: [ 4622.684102] usb 3-2: Manufacturer: Texas Instruments > Jan 14 10:50:49 pluto kernel: [ 4622.684108] usb 3-2: SerialNumber: TUSB3410 > Jan 14 10:50:50 pluto kernel: [ 4623.150995] USB Serial support registered for TI USB 3410 1 port adapter > Jan 14 10:50:50 pluto kernel: [ 4623.151213] USB Serial support registered for TI USB 5052 2 port adapter > Jan 14 10:50:50 pluto kernel: [ 4623.151255] ti_usb_3410_5052 3-2:1.0: TI USB 3410 1 port adapter converter detected > Jan 14 10:50:51 pluto kernel: [ 4623.788052] usb 3-2: reset full speed USB device number 2 using uhci_hcd > Jan 14 10:50:51 pluto kernel: [ 4623.918079] usb 3-2: device firmware changed > Jan 14 10:50:51 pluto kernel: [ 4623.918117] usb 3-2: USB disconnect, device number 2 > Jan 14 10:50:51 pluto kernel: [ 4623.918144] ti_usb_3410_5052: probe of 3-2:1.0 failed with error -5 > Jan 14 10:50:51 pluto kernel: [ 4623.919413] usbcore: registered new interface driver ti_usb_3410_5052 > Jan 14 10:50:51 pluto kernel: [ 4623.919420] ti_usb_3410_5052: v0.10:TI USB 3410/5052 Serial Driver > Jan 14 10:50:51 pluto kernel: [ 4624.023049] usb 3-2: new full speed USB device number 3 using uhci_hcd > Jan 14 10:50:51 pluto kernel: [ 4624.232076] usb 3-2: New USB device found, idVendor=0451, idProduct=3410 > Jan 14 10:50:51 pluto kernel: [ 4624.232086] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Jan 14 10:50:51 pluto kernel: [ 4624.232094] usb 3-2: Product: TUSB3410 Boot Device > Jan 14 10:50:51 pluto kernel: [ 4624.232100] usb 3-2: Manufacturer: Texas Instruments > Jan 14 10:50:51 pluto kernel: [ 4624.232106] usb 3-2: SerialNumber: TUSB3410 > Jan 14 10:50:51 pluto kernel: [ 4624.235195] ti_usb_3410_5052 3-2:1.0: TI USB 3410 1 port adapter converter detected > Jan 14 10:50:51 pluto kernel: [ 4624.235223] ti_usb_3410_5052: probe of 3-2:1.0 failed with error -5 > Jan 14 10:50:51 pluto kernel: [ 4624.239194] ti_usb_3410_5052 3-2:2.0: TI USB 3410 1 port adapter converter detected > Jan 14 10:50:51 pluto kernel: [ 4624.239743] usb 3-2: TI USB 3410 1 port adapter converter now attached to ttyUSB0 That's all perfectly normal. Do you have a wireshark or usbmon trace for this test? > > Also, if you unplug the device, reboot, and plug the device back in > > then the system log may include the name of a driver module that was > > automatically loaded to handle the device. > the diff between lsmod of a cleanly booted machine and then plugging in the fully powered up Inverter is: > < tcp_lp 2211 0 > < ti_usb_3410_5052 21110 0 > > So, I'd guess that the offending driver is ti_usb_3410_5052. Yes. tcp_lp has to do with networking, no connection with this. > If I > understand your description of the initiation process, that driver is > being installed as a result of some other program that I've yet to > track down. That program is udev. The driver is installed normally, just as any other driver is installed when needed. > And dbus is a likely starting point for running the > program, possibly related to tcp_lp (whatever that is, and I note > that it's not dependant on the other driver). I think that > ti_usb_3410_5052 does try to load firmware. Yes, it does. And it switches to config 2. But as far as I can tell, it doesn't send anything else to the device (like those requests for string descriptor 0xee) until the ttyUSB device is opened. dbus isn't your problem. Some other program must be trying to communicate with the device. Did you enable the usbfs_snoop parameter before collecting the log above? Alan Stern -- 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
