Hi,
On OpenBSD 6.0 AMD64, I ran this axen device (a "Level1 USB-0401",
http://global.level1.com/Network-Card/USB-0401/p-3209.htm , not listed
as supported in axen(4) ) for several days and it worked well (only
unexpected behavior was some dmesg checksum err dmesg warnings).
The only unusual thing with this machine is that it may have a USB
storage device which self-deattaches, so if there's any overflow between
USB ports then this could perhaps be caused by that. Though that one was
on USB2 and this axen is on USB3, so that would surprise me.
When booting, the axen would initialize as usual i.e.,
axen0 at uhub0 port 16 configuration 1 interface 0 "ASIX Elec.
Corp. AX88179" rev 3.00/1.00 addr 5
axen0: AX88179, address 00:11:6b:MYMAC
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
and after dhclient I'd get the two normal checksum errors,
checksum err (pkt#3)
checksum err (pkt#1)
Now, after a couple of hours, I would suddenly get another 53
repetitions of "checksum err (pkt#1)", and then this:
axen0: watchdog timeout
axen0: usb error on tx: IN_PROGRESS
axen0: usb error on tx: TIMEOUT
"ifconfig axen0" printed:
axen0: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST>
mtu 1500
lladdr 00:11:6b:MYMAC
index 5 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (10baseT half-duplex)
status: no carrier
inet MYIP netmask 0xffffff00 broadcast MYIP24.255
"nslookup", "ping" etc. failed (nslookup: "unknown host: google.com" ,
ping: "ping: wrote 8.8.8.8 64 chars, ret=-1").
"dhclient" would go up to the "DHCPDISCOVER" step and no further.
"ifconfig axen0 down" caused no dmesg output. "ifconfig axen0 up" caused
this dmesg output:
axen0: usb errors on rx: IOERROR
I could not find any way using any system tools to force a reattachment
by software.
Detached the axen0 physically. Reattaching it, its status lights lit up
immediately, and the dmesg was populated with:
rgephy0 detached
axen0 detached
axen0 at uhub0 port 16 configuration 1 interface 0 "ASIX Elec.
Corp. AX88179" rev 3.00/1.00 addr 5
axen0: AX88179, address 00:11:6b:MYMAC
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
And, 1081 repetitions of this:
checksum err (pkt#0)
invalid buffer(pkt#65535), continue
..and then shortly after that, the system became unresponsive so that I
needed to reboot the machine, giving me a suspicion that some part of
the axen driver got stuck in an infinite loop.
Detaching and then reattaching the axen, its LED:s would not light up
anymore, indicating that the system is indeed really frozen. Also
neither keyboard nor network responded.
The dmsg that printed the 1081 repetitions above, did return to the
shell before the system froze though.
Any thoughts on how fix would be much appreciated.
If I see this happen again maybe I will be able to go into the kernel
console and force a kernel stack dump.
Thanks,
Tinker
