port-i386/57662: StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub fails on Alix with NetBSD/i386 9.3

To: port-i386-maintainer%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost
Subject: port-i386/57662: StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub fails on Alix with NetBSD/i386 9.3
From: als%thangorodrim.ch@localhost
Date: Sun, 15 Oct 2023 20:45:01 +0000 (UTC)
>Number:         57662
>Category:       port-i386
>Synopsis:       StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub fails on Alix with NetBSD/i386 9.3
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Oct 15 20:45:01 +0000 2023
>Originator:     Alexander Schreiber
>Release:        
>Organization:
>Environment:
NetBSD khazad-dum 9.3 NetBSD 9.3 (KHAZAD_DUM) #3: Wed Aug 17 18:46:46 UTC 2022  root@khazad-dum:/net/build/khazad-dum/obj/sys/arch/i386/compile/KHAZAD_DUM i386

>Description:
I have acquired a StarTech 8-Port USB-to-Serial Adapter Hub, model number ICUSB23208FD with the intent of setting up a serial console server. Choosen machine is an alix2f13 (https://www.pcengines.ch/alix2f13.htm, LX800 AMD Geode CPU, Pentium Class).

Upon plugging in, the USB-to-Serial Adapter Hub is recognized:

Oct 15 14:48:59 khazad-dum /netbsd: [ 14167442.4086486] fatal breakpoint trap in supervisor mode
Oct 15 14:48:59 khazad-dum /netbsd: [ 14167442.4086486] trap type 1 code 0 eip 0xc0114bf4 cs 0x8 eflags 0x200202 cr2 0xb83d7860 ilevel 0x8 esp 0xcc8a9f6c
Oct 15 14:48:59 khazad-dum /netbsd: [ 14167442.4086486] curlwp 0xc0e80020 pid 0 lid 2 lowest kstack 0xcca062c0
Oct 15 14:48:59 khazad-dum /netbsd: uhub2 at uhub1 port 1: Terminus Technology (0x1a40) USB 2.0 Hub [MTT] (0x101), class 9/0, rev 2.00/1.00, addr 2
Oct 15 14:48:59 khazad-dum /netbsd: [ 14404697.6109689] uhub2: multiple transaction translators
Oct 15 14:48:59 khazad-dum /netbsd: [ 14404697.6109689] uhub2: 4 ports with 4 removable, self powered
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9188070] uftdi0 at uhub2 port 2 configuration 1 interface 0
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9295400] uftdi0: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 3
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9409797] ucom0 at uftdi0 portno 1
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9409797] uftdi1 at uhub2 port 2 configuration 1 interface 1
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9488820] uftdi1: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 3
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9597156] ucom1 at uftdi1 portno 2
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9597156] uftdi2 at uhub2 port 2 configuration 1 interface 2
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9690499] uftdi2: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 3
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9690499] ucom2 at uftdi2 portno 3
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9815384] uftdi3 at uhub2 port 2 configuration 1 interface 3
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9888359] uftdi3: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 3
Oct 15 14:49:01 khazad-dum /netbsd: [ 14404698.9888359] ucom3 at uftdi3 portno 4
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404699.9689657] uftdi4 at uhub2 port 3 configuration 1 interface 0
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404699.9804221] uftdi4: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 4
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404699.9918598] ucom4 at uftdi4 portno 1
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404699.9918598] uftdi5 at uhub2 port 3 configuration 1 interface 1
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404699.9992033] uftdi5: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 4
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0106410] ucom5 at uftdi5 portno 2
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0106410] uftdi6 at uhub2 port 3 configuration 1 interface 2
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0199490] uftdi6: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 4
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0293960] ucom6 at uftdi6 portno 3
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0293960] uftdi7 at uhub2 port 3 configuration 1 interface 3
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0399267] uftdi7: FTDI (0x403) USB <-> Serial Cable (0x6011), rev 2.00/8.00, addr 4
Oct 15 14:49:02 khazad-dum /netbsd: [ 14404700.0399267] ucom7 at uftdi7 portno 4


(and yes, the "fatal breakpoint trap in supervisor mode" smells)

I can then connect via "cu -l /dev/ttyU0 -s 115200" to an attached device,
and disconnect via the "~." sequence. This works 1-2 times and then any further attempts to do so only yield "cu: link down" and then cu exiting.

I've trace cu and the relevant section from the trace dumped with
"kdump -R" is:

 12400      1 cu       0.000009779 CALL  open(0xbfb4b77a,6,0)
 12400      1 cu       0.000009779 NAMI  "/dev/ttyU0"
 12400      1 cu       12.994282345 RET   open -1 errno 5 Input/output error

Unplugging the device results in the USB devices disconnecting with some
delay:

Oct 15 18:38:57 khazad-dum /netbsd: [ 14418495.3727440] ucom0: detached
Oct 15 18:38:57 khazad-dum /netbsd: [ 14418495.3727440] uftdi0: detached
Oct 15 18:38:57 khazad-dum /netbsd: [ 14418495.3727440] uftdi0: at uhub2 port 2 (addr 3) disconnected
Oct 15 18:38:59 khazad-dum /netbsd: [ 14418497.3830518] ucom1: detached
Oct 15 18:38:59 khazad-dum /netbsd: [ 14418497.3830518] uftdi1: detached
Oct 15 18:38:59 khazad-dum /netbsd: [ 14418497.3830518] uftdi1: at uhub2 port 2 (addr 3) disconnected
Oct 15 18:39:01 khazad-dum /netbsd: [ 14418499.3933598] ucom2: detached
Oct 15 18:39:01 khazad-dum /netbsd: [ 14418499.3933598] uftdi2: detached
Oct 15 18:39:01 khazad-dum /netbsd: [ 14418499.3933598] uftdi2: at uhub2 port 2 (addr 3) disconnected
Oct 15 18:39:03 khazad-dum /netbsd: [ 14418501.4036678] ucom3: detached
Oct 15 18:39:03 khazad-dum /netbsd: [ 14418501.4036678] uftdi3: detached
Oct 15 18:39:03 khazad-dum /netbsd: [ 14418501.4036678] uftdi3: at uhub2 port 2 (addr 3) disconnected
Oct 15 18:39:06 khazad-dum /netbsd: [ 14418504.4141291] ucom4: detached
Oct 15 18:39:06 khazad-dum /netbsd: [ 14418504.4141291] uftdi4: detached
Oct 15 18:39:06 khazad-dum /netbsd: [ 14418504.4141291] uftdi4: at uhub2 port 3 (addr 4) disconnected
Oct 15 18:39:08 khazad-dum /netbsd: [ 14418506.4244371] ucom5: detached
Oct 15 18:39:08 khazad-dum /netbsd: [ 14418506.4244371] uftdi5: detached
Oct 15 18:39:08 khazad-dum /netbsd: [ 14418506.4244371] uftdi5: at uhub2 port 3 (addr 4) disconnected
Oct 15 18:39:10 khazad-dum /netbsd: [ 14418508.4347451] ucom6: detached
Oct 15 18:39:10 khazad-dum /netbsd: [ 14418508.4347451] uftdi6: detached
Oct 15 18:39:10 khazad-dum /netbsd: [ 14418508.4347451] uftdi6: at uhub2 port 3 (addr 4) disconnected
Oct 15 18:39:12 khazad-dum /netbsd: [ 14418510.4450534] ucom7: detached
Oct 15 18:39:12 khazad-dum /netbsd: [ 14418510.4450534] uftdi7: detached
Oct 15 18:39:12 khazad-dum /netbsd: [ 14418510.4450534] uftdi7: at uhub2 port 3 (addr 4) disconnected
Oct 15 18:39:15 khazad-dum /netbsd: [ 14418513.4555144] uhub2: detached
Oct 15 18:39:15 khazad-dum /netbsd: [ 14418513.4555144] uhub2: at uhub1 port 1 (addr 2) disconnected


Plugging it back in only yields an error after some time:

Oct 15 18:40:43 khazad-dum /netbsd: [ 14418601.0689389] uhub1: autoconfiguration error: device problem, disabling port 1


I've reinstalled the same machine with Linux (Debian bookworm) and it
works with no apparent issues. 

relevant dmesg snippet from that setup (mostly for h/w id):
[   46.587001] usbserial: USB Serial support registered for FTDI USB Serial Device
[   46.630146] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
[   46.650945] usb 2-2: Detected FT232R
[   46.668978] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0
[   46.704109] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[   46.927654] usb 1-1.2: Detected FT4232H
[   46.944386] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB1
[   46.964563] ftdi_sio 1-1.2:1.1: FTDI USB Serial Device converter detected
[   46.987101] usb 1-1.2: Detected FT4232H
[   46.998834] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB2
[   47.023395] ftdi_sio 1-1.2:1.2: FTDI USB Serial Device converter detected
[   47.043118] usb 1-1.2: Detected FT4232H
[   47.054859] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB3
[   47.079375] ftdi_sio 1-1.2:1.3: FTDI USB Serial Device converter detected
[   47.099113] usb 1-1.2: Detected FT4232H
[   47.111007] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB4
[   47.134324] ftdi_sio 1-1.3:1.0: FTDI USB Serial Device converter detected
[   47.154893] usb 1-1.3: Detected FT4232H
[   47.170720] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB5
[   47.191453] ftdi_sio 1-1.3:1.1: FTDI USB Serial Device converter detected
[   47.211397] usb 1-1.3: Detected FT4232H
[   47.226716] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB6
[   47.246908] ftdi_sio 1-1.3:1.2: FTDI USB Serial Device converter detected
[   47.266903] usb 1-1.3: Detected FT4232H
[   47.282737] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB7
[   47.303569] ftdi_sio 1-1.3:1.3: FTDI USB Serial Device converter detected
[   47.322895] usb 1-1.3: Detected FT4232H
[   47.338747] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB8


I've tried the same USB-to-Serial Adapter Hub on an APU (https://www.pcengines.ch/apu2.htm, AMD GX-412TC, amd64) running NetBSD/amd64 9.3 and it works without any apparent problems.

I currently have no other machine types running NetBSD/i386 to crosstest.

So it looks like this is confined to the combination of
- PCEngines Alix
- NetBSD/i386

I do not realistically expect a fix and this PR is just intended as documentation if someone else wants to use that device combo.

Note: while the NetBSD logs come from a machine running a (slightly, mostly
enabling diagnostics and dropping unneeded stuff) custom kernel, the initial installation having the same issues ran GENERIC from a fresh install.

>How-To-Repeat:
- acquire PEngines Alix
- install NetBSD/i386 9.3
- acquire StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub 
- plug above device into Alix
- try to use the above device as a serial console interface
  (e.g.: "cu -l /dev/ttyU8 -s 115200")


>Fix:
none
Follow-Ups:
- Re: port-i386/57662: StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub fails on Alix with NetBSD/i386 9.3
  - From: Manuel Bouyer
Prev by Date: NetBSD Nightly Trouble Ticket Report
Next by Date: Re: port-i386/57662: StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub fails on Alix with NetBSD/i386 9.3
Previous by Thread: PR/57659 CVS commit: src/tests/kernel
Next by Thread: Re: port-i386/57662: StarTech ICUSB23208FD 8-Port USB-to-Serial Adapter Hub fails on Alix with NetBSD/i386 9.3
Indexes:
Home | Main Index | Thread Index | Old Index