Re: FTDI-SIO hang on ftdi_close()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----linux-usb-owner@xxxxxxxxxxxxxxx wrote: -----

>Which of these three FTDI devices is the one that's hanging?

These two are causing problems.

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0403 ProdID=6001 Rev= 6.00
S:  Manufacturer=FTDI
S:  Product=FT232R USB UART
S:  SerialNumber=A600e2CA
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 90mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0403 ProdID=6001 Rev= 6.00
S:  Manufacturer=FTDI
S:  Product=FT232R USB UART
S:  SerialNumber=A600bjV2
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 90mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms


>> Server ~ # cat /sys/kernel/debug/usb/ohci/0000\:00\:02.0/async
>> cat: /sys/kernel/debug/usb/ohci/0000:00:02.0/async: Operation not
>permitted
>
>That's very suspicious.  In fact, I can't imagine how it happened.
>Does the file not have read permission?
>
>Probably the information we need is buried in that file...

Server ~ # cd /sys/kernel/debug/usb/
Server usb # ls -al
total 0
drwxr-xr-x  5 root root 0 Nov 17 20:46 .
drwxr-xr-x 13 root root 0 Nov 17 20:46 ..
-r--r--r--  1 root root 0 Nov 17 20:46 devices
drwxr-xr-x  4 root root 0 Nov 17 20:46 ehci
drwxr-xr-x  4 root root 0 Nov 17 20:46 ohci
drwxr-xr-x  2 root root 0 Nov 17 20:46 usbmon
Server usb # cd ohci/
Server ohci # ls -al
total 0
drwxr-xr-x 4 root root 0 Nov 17 20:46 .
drwxr-xr-x 5 root root 0 Nov 17 20:46 ..
drwxr-xr-x 2 root root 0 Nov 17 20:46 0000:00:02.0
drwxr-xr-x 2 root root 0 Nov 17 20:46 0000:00:04.0
Server ohci # ls -al 0000\:00\:02.0/
total 0
drwxr-xr-x 2 root root 0 Nov 17 20:46 .
drwxr-xr-x 4 root root 0 Nov 17 20:46 ..
-r--r--r-- 1 root root 0 Nov 17 20:46 async
-r--r--r-- 1 root root 0 Nov 17 20:46 periodic
-r--r--r-- 1 root root 0 Nov 17 20:46 registers
Server ohci # ls -al 0000\:00\:04.0/
total 0
drwxr-xr-x 2 root root 0 Nov 17 20:46 .
drwxr-xr-x 4 root root 0 Nov 17 20:46 ..
-r--r--r-- 1 root root 0 Nov 17 20:46 async
-r--r--r-- 1 root root 0 Nov 17 20:46 periodic
-r--r--r-- 1 root root 0 Nov 17 20:46 registers
Server ohci #

>Here's something else you can try as well.  Make sure CONFIG_USB_MON
>is enabled, and record a usbmon trace for the bus with the device
>that
>causes the hang.  Instructions are in the kernel source file
>Documentation/usb/usbmon.txt.

Okay. This is the trace while the port (Bus=03 Port=01) is already in the
"hang" state:
ffff880085eb4240 2800006305 S Co:3:003:0 s 40 09 0001 0000 0000 0
ffff880085eb4240 2805006485 C Co:3:003:0 -2 0
ffff880085eb4240 2805006514 S Co:3:003:0 s 40 00 0000 0000 0000 0
ffff880085eb4240 2810006333 C Co:3:003:0 -2 0
ffff880085eb4240 2810006365 S Co:3:003:0 s 40 04 1208 0000 0000 0
ffff880085eb4240 2811006302 C Co:3:003:0 -2 0
ffff880085eb4240 2811006337 S Co:3:003:0 s 40 03 809c 0000 0000 0
ffff880085eb4240 2812006271 C Co:3:003:0 -2 0
ffff880085eb4240 2812006304 S Co:3:003:0 s 40 02 0000 0000 0000 0
ffff880085eb4240 2817006112 C Co:3:003:0 -2 0
ffff880085eb4240 2817006135 S Co:3:003:0 s 40 01 0300 0000 0000 0
ffff880085eb4240 2822005959 C Co:3:003:0 -2 0
ffff88013e343840 2822005973 S Bi:3:003:1 -115 512 <
ffff880085eb4240 2822005984 S Co:3:003:0 s 40 01 0303 0000 0000 0
ffff880085eb4240 2827006818 C Co:3:003:0 -2 0
ffff880085eb4240 2827006880 S Co:3:003:0 s 40 04 1208 0000 0000 0
ffff880085eb4240 2828006776 C Co:3:003:0 -2 0
ffff880085eb4240 2828006807 S Co:3:003:0 s 40 03 809c 0000 0000 0
ffff880085eb4240 2829006744 C Co:3:003:0 -2 0
ffff880085eb4240 2829006762 S Co:3:003:0 s 40 02 0000 0000 0000 0
ffff880085eb4240 2834007599 C Co:3:003:0 -2 0
ffff880085eb4240 2834007638 S Co:3:003:0 s 40 01 0300 0000 0000 0
ffff880085eb4240 2839008447 C Co:3:003:0 -2 0
ffff880085eb4240 2839008502 S Co:3:003:0 s 40 04 1208 0000 0000 0
ffff880085eb4240 2840008416 C Co:3:003:0 -2 0
ffff880085eb4240 2840008452 S Co:3:003:0 s 40 03 809c 0000 0000 0
ffff880085eb4240 2841008386 C Co:3:003:0 -2 0
ffff880085eb4240 2841008420 S Co:3:003:0 s 40 02 0000 0000 0000 0
ffff880085eb4240 2846008225 C Co:3:003:0 -2 0
ffff880085eb4240 2846008249 S Co:3:003:0 s 40 01 0300 0000 0000 0
ffff880085eb4240 2851008071 C Co:3:003:0 -2 0
ffff880085eb4240 2851008098 S Ci:3:003:0 s c0 05 0000 0000 0002 2 <
ffff880085eb4240 2856007942 C Ci:3:003:0 -2 0
ffff88001ffcf3c0 2856007974 S Co:3:003:0 s 40 01 0300 0000 0000 0
ffff88001ffcf3c0 2861007768 C Co:3:003:0 -2 0
ffff880085e1f6c0 2861007807 S Ci:3:003:0 s c0 05 0000 0000 0002 2 <
ffff880085e1f6c0 2866008844 C Ci:3:003:0 -2 0
ffff880085f80c00 2866008868 S Co:3:003:0 s 40 01 0302 0000 0000 0
ffff880085f80c00 2871009470 C Co:3:003:0 -2 0
ffff880085f809c0 2871099598 S Ci:3:003:0 s c0 05 0000 0000 0002 2 <
ffff880085f809c0 2876099316 C Ci:3:003:0 -2 0
ffff880085f809c0 2876099360 S Co:3:003:0 s 40 01 0301 0000 0000 0
ffff880085f809c0 2881099153 C Co:3:003:0 -2 0
ffff880085f809c0 2881099187 S Ci:3:003:0 s c0 05 0000 0000 0002 2 <
ffff880085f809c0 2886099002 C Ci:3:003:0 -2 0
ffff880085f809c0 2886099026 S Co:3:003:0 s 40 01 0301 0000 0000 0
ffff880085f809c0 2891098850 C Co:3:003:0 -2 0

Regards.

David

--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux