Re: USB: ftdi_sio: not detecting
On Tue, Aug 14, 2018 at 7:33 PM, Alan Stern wrote: > On Tue, 14 Aug 2018, Muni Sekhar wrote: > >> On Mon, Aug 13, 2018 at 7:52 PM, Muni Sekhar wrote: >> > On Mon, Aug 13, 2018 at 6:57 PM, Oliver Neukum wrote: >> >> On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: >> >>> [ Please keep me in CC as I'm not subscribed to the list] >> >>> >> >>> Hello All, >> >>> >> >>> I’ve a FTDI serial device and it is not recognized if I connect >> >>> directly to computer. However if I connect via an external USB hub >> >>> it’s fine and I can see the FTDI serial device. What could be the >> >>> issue and how to resolve this? >> If I connect the FTDI device directly to computer I don't see any >> dmesg log, but after enabling the dynamic debugging for usbcore and >> hcd's driver then I see kernel log flooded with the below mentioned >> logs. Is it a bug in the hcd's driver? The same device works fine if I >> connect via an external USB hub. >> >> [14045.942047] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >> [14045.942156] usb usb2-port2: status 0100, change 0001, 12 Mb/s >> [14046.102357] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 >> [14046.158579] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >> [14046.158692] usb usb2-port2: status 0100, change 0001, 12 Mb/s >> [14046.318662] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 >> [14046.374689] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >> [14046.374798] usb usb2-port2: status 0100, change 0001, 12 Mb/s >> [14046.535001] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 >> [14046.591050] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >> [14046.591161] usb usb2-port2: status 0100, change 0001, 12 Mb/s >> [14046.751382] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 >> [14046.807415] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >> [14046.807527] usb usb2-port2: status 0100, change 0001, 12 Mb/s >> [14046.967725] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 >> [14047.023761] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >> [14047.023872] usb usb2-port2: status 0100, change 0001, 12 Mb/s >> [14047.184025] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 >> [14047.240078] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > > These messages indicate the device is electronically detaching itself > from the bus and then reattaching itself, over and over again, about > four times per second. Thanks for this information. > > Have you tried using this device on another computer? Do you have > another full-speed device you can try plugging into that port? It connects perfectly to my virtual box running Linux. Right now I don't have any other full-speed device to verify this. > > Alan Stern > -- Thanks, Sekhar
Re: USB: ftdi_sio: not detecting
On Tue, 14 Aug 2018, Muni Sekhar wrote: > On Mon, Aug 13, 2018 at 7:52 PM, Muni Sekhar wrote: > > On Mon, Aug 13, 2018 at 6:57 PM, Oliver Neukum wrote: > >> On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: > >>> [ Please keep me in CC as I'm not subscribed to the list] > >>> > >>> Hello All, > >>> > >>> I’ve a FTDI serial device and it is not recognized if I connect > >>> directly to computer. However if I connect via an external USB hub > >>> it’s fine and I can see the FTDI serial device. What could be the > >>> issue and how to resolve this? > If I connect the FTDI device directly to computer I don't see any > dmesg log, but after enabling the dynamic debugging for usbcore and > hcd's driver then I see kernel log flooded with the below mentioned > logs. Is it a bug in the hcd's driver? The same device works fine if I > connect via an external USB hub. > > [14045.942047] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14045.942156] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.102357] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.158579] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.158692] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.318662] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.374689] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.374798] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.535001] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.591050] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.591161] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.751382] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.807415] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.807527] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.967725] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.023761] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14047.023872] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14047.184025] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.240078] hub 2-0:1.0: state 7 ports 6 chg evt 0004 These messages indicate the device is electronically detaching itself from the bus and then reattaching itself, over and over again, about four times per second. Have you tried using this device on another computer? Do you have another full-speed device you can try plugging into that port? Alan Stern
Re: USB: ftdi_sio: not detecting
On Di, 2018-08-14 at 14:49 +0530, Muni Sekhar wrote: > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M > > |__ Port 2: Dev 91, If 0, Class=Hub, Driver=hub/4p, 480M > > |__ Port 2: Dev 100, If 0, Class=Hub, Driver=hub/3p, 480M > > |__ Port 1: Dev 101, If 0, Class=Vendor Specific Class, > Driver=ftdi_sio, 12M > > |__ Port 2: Dev 102, If 0, Class=Vendor Specific Class, > Driver=ftdi_sio, 12M > > |__ Port 3: Dev 103, If 0, Class=Vendor Specific Class, > Driver=ftdi_sio, 12M In this case XHCI. But you need the failing case. Presumably also XHCI, but that is not guaranteed. In case lsusb -t fails in the failure case, attach another device into the port your serial devices fails at. Regards Oliver
Re: USB: ftdi_sio: not detecting
On Tue, Aug 14, 2018 at 2:39 PM, Oliver Neukum wrote: > On Di, 2018-08-14 at 14:29 +0530, Muni Sekhar wrote: >> >> Is there any way to know which HC I’m is using? I checked the >> /sys/kernel/debug/usb/devices file and I see three HC’s. >> >> >> >> T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1 > > Match the 'Bus' number or use 'lsusb -t' $ lsusb -t /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 2: Dev 91, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 100, If 0, Class=Hub, Driver=hub/3p, 480M |__ Port 1: Dev 101, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M |__ Port 2: Dev 102, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M |__ Port 3: Dev 103, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M |__ Port 4: Dev 2, If 0, Class=Communications, Driver=cdc_acm, 480M |__ Port 4: Dev 2, If 1, Class=CDC Data, Driver=cdc_acm, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 5: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M > > HTH > Oliver > -- Thanks, Sekhar
Re: USB: ftdi_sio: not detecting
On Di, 2018-08-14 at 14:29 +0530, Muni Sekhar wrote: > > Is there any way to know which HC I’m is using? I checked the > /sys/kernel/debug/usb/devices file and I see three HC’s. > > > > T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1 Match the 'Bus' number or use 'lsusb -t' HTH Oliver
Re: USB: ftdi_sio: not detecting
On Tue, Aug 14, 2018 at 2:02 PM, Oliver Neukum wrote: > On Di, 2018-08-14 at 12:17 +0530, Muni Sekhar wrote: >> On Mon, Aug 13, 2018 at 7:52 PM, Muni Sekhar wrote: >> > On Mon, Aug 13, 2018 at 6:57 PM, Oliver Neukum wrote: >> > > On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: >> > > > [ Please keep me in CC as I'm not subscribed to the list] >> > > > >> > > > Hello All, >> > > > >> > > > I’ve a FTDI serial device and it is not recognized if I connect >> > > > directly to computer. However if I connect via an external USB hub >> > > > it’s fine and I can see the FTDI serial device. What could be the >> > > > issue and how to resolve this? >> >> If I connect the FTDI device directly to computer I don't see any >> dmesg log, but after enabling the dynamic debugging for usbcore and >> hcd's driver then I see kernel log flooded with the below mentioned >> logs. Is it a bug in the hcd's driver? The same device works fine if I >> connect via an external USB hub. > > Hi, > > you are looking at an issue with the HC driver. Unfortunately you have > castrated the logs to an extent that prevents me from telling which > HC you are using. However, in any case, you need to find out and > contact its driver's maintainer. Is there any way to know which HC I’m is using? I checked the /sys/kernel/debug/usb/devices file and I see three HC’s. T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev= 4.04 S: Manufacturer=Linux 4.4.0-28-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 4.04 S: Manufacturer=Linux 4.4.0-28-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 4.04 S: Manufacturer=Linux 4.4.0-28-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms > > HTH > Oliver > -- Thanks, Sekhar
Re: USB: ftdi_sio: not detecting
On Di, 2018-08-14 at 12:17 +0530, Muni Sekhar wrote: > On Mon, Aug 13, 2018 at 7:52 PM, Muni Sekhar wrote: > > On Mon, Aug 13, 2018 at 6:57 PM, Oliver Neukum wrote: > > > On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: > > > > [ Please keep me in CC as I'm not subscribed to the list] > > > > > > > > Hello All, > > > > > > > > I’ve a FTDI serial device and it is not recognized if I connect > > > > directly to computer. However if I connect via an external USB hub > > > > it’s fine and I can see the FTDI serial device. What could be the > > > > issue and how to resolve this? > > If I connect the FTDI device directly to computer I don't see any > dmesg log, but after enabling the dynamic debugging for usbcore and > hcd's driver then I see kernel log flooded with the below mentioned > logs. Is it a bug in the hcd's driver? The same device works fine if I > connect via an external USB hub. Hi, you are looking at an issue with the HC driver. Unfortunately you have castrated the logs to an extent that prevents me from telling which HC you are using. However, in any case, you need to find out and contact its driver's maintainer. HTH Oliver
Re: USB: ftdi_sio: not detecting
On Mon, Aug 13, 2018 at 7:52 PM, Muni Sekhar wrote: > On Mon, Aug 13, 2018 at 6:57 PM, Oliver Neukum wrote: >> On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: >>> [ Please keep me in CC as I'm not subscribed to the list] >>> >>> Hello All, >>> >>> I’ve a FTDI serial device and it is not recognized if I connect >>> directly to computer. However if I connect via an external USB hub >>> it’s fine and I can see the FTDI serial device. What could be the >>> issue and how to resolve this? If I connect the FTDI device directly to computer I don't see any dmesg log, but after enabling the dynamic debugging for usbcore and hcd's driver then I see kernel log flooded with the below mentioned logs. Is it a bug in the hcd's driver? The same device works fine if I connect via an external USB hub. [14045.942047] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14045.942156] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.102357] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.158579] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.158692] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.318662] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.374689] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.374798] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.535001] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.591050] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.591161] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.751382] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.807415] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.807527] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.967725] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.023761] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14047.023872] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14047.184025] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.240078] hub 2-0:1.0: state 7 ports 6 chg evt 0004 >>> >>> >>> Also one more behaviour, when I ran “lsusb” it hangs forever and ‘ps’ >>> command output shows the state as “Dl+”. Any reasons for this >>> behaviour? >> >> Impossible to tell. Switch on dynamic debugging for usbcore and your >> hcd's driver and post dmesg. >> Sysrq-T during the hang would also help. > After enabling the dynamic debugging, I'm getting the below mentioned log: > > [14045.942047] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14045.942156] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.102357] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.158579] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.158692] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.318662] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.374689] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.374798] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.535001] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.591050] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.591161] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.751382] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14046.807415] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14046.807527] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14046.967725] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.023761] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14047.023872] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14047.184025] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.240078] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14047.240189] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14047.400373] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.456425] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14047.456537] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14047.616685] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.672654] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14047.672749] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14047.833074] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14047.888951] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14047.889006] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14048.049388] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14048.105450] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14048.105560] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14048.265730] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 > [14048.321776] hub 2-0:1.0: state 7 ports 6 chg evt 0004 > [14048.321892] usb usb2-port2: status 0100, change 0001, 12 Mb/s > [14048.482047] usb usb2-port2: debounce total 125ms
Re: USB: ftdi_sio: not detecting
On Mon, Aug 13, 2018 at 6:57 PM, Oliver Neukum wrote: > On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: >> [ Please keep me in CC as I'm not subscribed to the list] >> >> Hello All, >> >> I’ve a FTDI serial device and it is not recognized if I connect >> directly to computer. However if I connect via an external USB hub >> it’s fine and I can see the FTDI serial device. What could be the >> issue and how to resolve this? >> >> >> Also one more behaviour, when I ran “lsusb” it hangs forever and ‘ps’ >> command output shows the state as “Dl+”. Any reasons for this >> behaviour? > > Impossible to tell. Switch on dynamic debugging for usbcore and your > hcd's driver and post dmesg. > Sysrq-T during the hang would also help. After enabling the dynamic debugging, I'm getting the below mentioned log: [14045.942047] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14045.942156] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.102357] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.158579] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.158692] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.318662] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.374689] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.374798] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.535001] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.591050] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.591161] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.751382] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14046.807415] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14046.807527] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14046.967725] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.023761] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14047.023872] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14047.184025] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.240078] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14047.240189] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14047.400373] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.456425] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14047.456537] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14047.616685] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.672654] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14047.672749] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14047.833074] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14047.888951] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14047.889006] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14048.049388] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14048.105450] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14048.105560] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14048.265730] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14048.321776] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14048.321892] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14048.482047] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14048.538083] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14048.538193] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14048.698410] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14048.754471] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14048.754581] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14048.914753] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14048.970807] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14048.970916] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14049.131055] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14049.187091] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14049.187200] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14049.347454] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14049.403500] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14049.403610] usb usb2-port2: status 0100, change 0001, 12 Mb/s [14049.563813] usb usb2-port2: debounce total 125ms stable 100ms status 0x101 [14049.619721] hub 2-0:1.0: state 7 ports 6 chg evt 0004 [14049.619778] usb usb2-port2: status 0100, change 0001, 12 Mb/s > > Regards > Oliver > -- Thanks, Sekhar
Re: USB: ftdi_sio: not detecting
On Mo, 2018-08-13 at 18:44 +0530, Muni Sekhar wrote: > [ Please keep me in CC as I'm not subscribed to the list] > > Hello All, > > I’ve a FTDI serial device and it is not recognized if I connect > directly to computer. However if I connect via an external USB hub > it’s fine and I can see the FTDI serial device. What could be the > issue and how to resolve this? > > > Also one more behaviour, when I ran “lsusb” it hangs forever and ‘ps’ > command output shows the state as “Dl+”. Any reasons for this > behaviour? Impossible to tell. Switch on dynamic debugging for usbcore and your hcd's driver and post dmesg. Sysrq-T during the hang would also help. Regards Oliver
