axen first-time problem/bug: "watchdog timeout" in dmesg and then unresponsive. After reattaching it, system crash.

[Tinker]

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

[Tinker]

Hi Stefan/bugs@,

(This one is also intended as followup on the
https://marc.info/?t=149137421500003&r=1&w=2 thread "Disable axen(4)'s
"checksum err (pkt#N)" console/dmes" with Stefan.)

The single system permanent freeze I experienced that can have been for
any complex reason but correlated the most with me seeing the axen stop
functioning and re-plugging it, freaked me out a bit, and made me
hesitate suggesting to remove its debug output.

The only clue re "complex reason" I have is that some USB memory stick
automatically times out on this machine, maybe hinting me that the USB
implementation on this hardware may be imperfect.

I have not seen any stop-responding (and nor any issue on replugging)
since however.


With my limited code reading skills, I can't see anything that looks
prone to cause a system freeze in axen's sources
(https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axen.c?rev=1.24&content-type=text/x-cvsweb-markup
,
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axenreg.h?rev=1.6&content-type=text/x-cvsweb-markup)
-

Firstly, there are no loops in there that could go on forever (which
would be relevant if the axen code runs under the big lock, which I
guess it does; package processing takes a 16bit counting integer, I
guess that's not enough to cause any long freeze, and apart from that
the only loop in the whole code is "while (enm != NULL) { ..
ETHER_NEXT_MULTI(step, enm); }", which I guess should be failsafe).

Second, when I detached the axen, I did get "rgephy0 detached" "axen0
detached" printed in the dmesg, which I interpret as that there should
have been no toxic state waiting in the axen driver at the time of
reattachment.

One could speculate that there was toxic state or some other form of
hickups in the USB subsystem, but that would really only be guesswork -


My only conclusion from this is that to analyze the problem further, the
problem would need to be reproduced and this time a system trace would
need to be taken from the kernel debugger.

Also one could try reattaching a bunch of times or otherwise stressing
the NIC to try to evoke the crash again.

And also of course, maybe a driver cannot be designed to keep up with
any exotic failure state within a hardware device, in particular in
combinations of devices (USB controller + axen), so maybe this was just
like the exception that proves the rule.

I didn't see any problems whatsoever with the RTL8153 though.

Thanks,
Tinker

Post by Tinker
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
axen0: watchdog timeout
axen0: usb error on tx: IN_PROGRESS
axen0: usb error on tx: TIMEOUT
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"
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
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
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

..

Post by Tinker

The axen(4) ( http://man.openbsd.org/axen.4 ) driver occasionally
prints a
"checksum err (pkt#N)" warning message to the console/dmesg. The rate
I'm
observing currently is about three per week, and what I see is that it
has

..

Post by Tinker
Yes, some cleanup is due here.
I suggest you send us a patch that makes it a DPRINTF. You could also
add
a line ifp->if_ierrors++;' at the same place so the error is counted
in
netstat -I axen0.
And there are some similar printfs in the same function that should get
the same treatment, such as this one: printf("rxeof: too large
transfer\n");

[Tinker]

Waait - indeed there was a specific hint when the axen malbehavior
started, and that was the

axen0: watchdog timeout
axen0: usb error on tx: IN_PROGRESS
axen0: usb error on tx: TIMEOUT

output in the dmesg.

After that, the axen did not receive or send any frames.

axen_watchdog()'s logics to handle this are

sc = ifp->if_softc;

ifp->if_oerrors++;
printf("axen%d: watchdog timeout\n", sc->axen_unit);

s = splusb();
c = &sc->axen_cdata.axen_tx_chain[0];
usbd_get_xfer_status(c->axen_xfer, NULL, NULL, NULL, &stat);
axen_txeof(c->axen_xfer, c, stat);

if (!IFQ_IS_EMPTY(&ifp->if_snd))
axen_start(ifp);
splx(s);


And that obviously did not reset the NIC to function again.

And "ifconfig axen0 down" + ".. up" also did not. (And then the system
froze.)


Is there any way that I could cause a "harder" reset, in that code, or
via command line utilities?

Tinker

Post by Tinker
(This one is also intended as followup on the
https://marc.info/?t=149137421500003&r=1&w=2 thread "Disable axen(4)'s
"checksum err (pkt#N)" console/dmes" with Stefan.)
The single system permanent freeze I experienced that can have been
for any complex reason but correlated the most with me seeing the axen
stop functioning and re-plugging it, freaked me out a bit, and made me
hesitate suggesting to remove its debug output.
The only clue re "complex reason" I have is that some USB memory stick
automatically times out on this machine, maybe hinting me that the USB
implementation on this hardware may be imperfect.
I have not seen any stop-responding (and nor any issue on replugging)
since however.
With my limited code reading skills, I can't see anything that looks
prone to cause a system freeze in axen's sources
(https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axen.c?rev=1.24&content-type=text/x-cvsweb-markup
,
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axenreg.h?rev=1.6&content-type=text/x-cvsweb-markup)
-
Firstly, there are no loops in there that could go on forever (which
would be relevant if the axen code runs under the big lock, which I
guess it does; package processing takes a 16bit counting integer, I
guess that's not enough to cause any long freeze, and apart from that
the only loop in the whole code is "while (enm != NULL) { ..
ETHER_NEXT_MULTI(step, enm); }", which I guess should be failsafe).
Second, when I detached the axen, I did get "rgephy0 detached" "axen0
detached" printed in the dmesg, which I interpret as that there should
have been no toxic state waiting in the axen driver at the time of
reattachment.
One could speculate that there was toxic state or some other form of
hickups in the USB subsystem, but that would really only be guesswork -
My only conclusion from this is that to analyze the problem further,
the problem would need to be reproduced and this time a system trace
would need to be taken from the kernel debugger.
Also one could try reattaching a bunch of times or otherwise stressing
the NIC to try to evoke the crash again.
And also of course, maybe a driver cannot be designed to keep up with
any exotic failure state within a hardware device, in particular in
combinations of devices (USB controller + axen), so maybe this was
just like the exception that proves the rule.
I didn't see any problems whatsoever with the RTL8153 though.
Thanks,
Tinker

Post by Tinker
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
axen0: watchdog timeout
axen0: usb error on tx: IN_PROGRESS
axen0: usb error on tx: TIMEOUT
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"
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
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
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

..

Post by Tinker

The axen(4) ( http://man.openbsd.org/axen.4 ) driver occasionally
prints a
"checksum err (pkt#N)" warning message to the console/dmesg. The rate
I'm
observing currently is about three per week, and what I see is that
it has

..

Post by Tinker
Yes, some cleanup is due here.
I suggest you send us a patch that makes it a DPRINTF. You could also
add
a line ifp->if_ierrors++;' at the same place so the error is counted
in
netstat -I axen0.
And there are some similar printfs in the same function that should get
the same treatment, such as this one: printf("rxeof: too large
transfer\n");

[Stefan Sperling]

Post by Tinker
And "ifconfig axen0 down" + ".. up" also did not. (And then the system
froze.)

While the system is frozen in X, does the system reboot if you type:
bo re<ENTER>

If you trigger the problem on ttyC0 outside of X, do you get a ddb prompt?

[Tinker]

Post by Stefan Sperling

Post by Tinker
And "ifconfig axen0 down" + ".. up" also did not. (And then the system
froze.)

bo re<ENTER>
If you trigger the problem on ttyC0 outside of X, do you get a ddb prompt?

Not in X.

No DDB but I may have configed it away. I should enable the DDB keyboard
shortcut.

Anyhow again it happened just once so can't analyze too much out of it,
when I have time I should attempt to simply stress it.

What was clear from this single crash I experienced though is 1) that a
watchdog timeout was detected and for whatever reason the NIC went
unresponsive after that, and 2) after detaching and reattaching the NIC,
the system froze.

So looking forward to debug it further, for instance by giving it crap
data, and reattaching it lots of times.

[Tinker]

Hi bugs@,

So here is followup on the AXEN malfunctioning thread started 5 April (
http://marc.info/?t=149141061800001&r=1&w=2 ), for my AXEN-based "Level1
USB-0401" http://global.level1.com/Network-Card/USB-0401/p-3209.htm
which *should* just be another generic. It automatically attaches as
axen0 when plugged in.

I left the AXEN for a couple of ways and got back to it last 3 days, and
it gave me all kinds of problems -
* Sometimes it works perfectly,
* Sometimes it stops suddenly, in particular ~30 seconds after boot,
* With no output to the console/dmesg,
* With a sparse "watchdog timeout" + "usb error on tx: IN_PROGRESS"
+ "usb error on tx: TIMEOUT" message,
* With an unending repeated printout of "checksum error (pkt#0)" +
"invalid buffer(pkt#65535), continue" in random constellations,
* Sometimes (though relatively rarely), system freeze.

To reduce the problem, I
* Tried attaching the AXEN on two different USB3 ports on the machine,
* I tried having the AXEN attached to two different ethernet devices (a
modem and a router), and
* I tried switching off and on the USB2 and USB3 "legacy mode":s in the
BIOS.

Maaybe there's less of the "stop working after ~30 seconds after boot"
thing after disabling USB legacy mode in BIOS, except for that no
difference in behavior between the different modes I tried.

Also whether the device was attached from boot or was reattached, does
not seem to affect whether the AXEN malfunctions/how much (despite my
initial choice of thread subject).

This leads me to believe that there's something universally wrong about
the AXEN device or driver - the only next thing to try would be to try
the AXEN on another computer.


I wanted to go deeper into the system freeze situation, so I enabled
ddb.console and got to reproduce the system freeze (by just rebooting a
couple of times and trying to communicate over the AXEN), and I had a
success with that within ~2 minutes.

The output of "trace" in ddb is:

Debugger() at Debugger+0x9
internal_command() at internal_command+0x155
wskbd_translate() at wskbd_translate+0x90
wskbd_input() at wskbd_input+0x55
pckbd_input() at pckbd_input+0xb4
pckbcintr_internal() at ckbcintr_internal+0x8e
intr_handler() at intr_handler+0x67
Xintr_ioapic_edge1() at Xintr_ioapic_edge1+0xc9
--- interrupt ---
memcpy() at memcpy+0xa
usb_transfer_complete() at usb_transfer_complete+0x26c
xhci_event_dequeue() at xhci_event_dequeue+0x65
xhci_softintr() at xhci_softintr+0x21
softintr_dispatch() at softintr_dispatch+0x8b
Xsoftnet() at Xsoftnet+0x1f
--- interrupt ---
end of kernel
end trace frame: 0x31, count: -14
0x8:


The other CPU cores were all in x86_ip_handler().


Freshly booted machine, no interesting processes running.

I can provide you with the "show register" output however since it was
in the wskbd_translate() already I guess it's not relevant.

I guess the above proves my hypothesis that the machine freeze did
indeed have to do with the AXEN device or driver.


This is OpenBSD 6.0, however if I am reading
*
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axenreg.h
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axen.c
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhci.c
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhcireg.h
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhcivar.h
right then nothing relating to this error has changed since.


I would be happy to donate this AXEN device to a developer for you to
either blacklist it as officially unsupported by OpenBSD, or figure
what's wrong and make it work. If so please let me know your postal
address.


Also one more thing I coud do, would be to do "c"(continue) in DDB and
catch more different traces, to profile the error further. Also, I could
try to run the system without the CDCE (USB RTL8153 ethernet) I have
plugged in to the system, to reduce fruther.


So to sum up, next steps I see relevant are:

* Anyone have a look at the above report

* I donate this AXEN to a developer, please let me know postal address

* I/anyone try this AXEN on another device

* I could try to reduce the case further by also removing the CDCE
device (an USB RTL8153 ethernet dongle)

* I/anyone reproduce the freeze and profile it further by doing
trace+"c"(continue) repeats in DDB.

Let me know next step.

Thanks!
Tinker

dmesg:
OpenBSD 6.0 (GENERIC.MP) #0: Thu Mar 23 03:06:38 GMT 2017
***@SNIP:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17121271808 (16328MB)
avail mem = 16597905408 (15828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xedd90 (20 entries)
bios0: vendor American Megatrends Inc. version "P3.30" date 06/04/2015
bios0: ASRock E3C226D2I
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT AAFT SSDT SSDT MCFG PRAD
HPET SSDT SSDT SPMI UEFI DMAR
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4)
PEG2(S4) CIR_(S4) PS2K(S4) PS2M(S4) UR11(S4) UR12(S4) PXSX(S4) BR11(S4)
RP01(S4) PXSX(S4) RP02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3293.27 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.65 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.65 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.65 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.65 MHz
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.65 MHz
cpu5:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
cpu6: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.64 MHz
cpu6:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 1, core 2, package 0
cpu7 at mainbus0: apid 7 (application processor)
cpu7: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 3292.65 MHz
cpu7:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 1, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 2 (RP01)
acpiprt5 at acpi0: bus -1 (RP02)
acpiprt6 at acpi0: bus -1 (RP03)
acpiprt7 at acpi0: bus -1 (RP04)
acpiprt8 at acpi0: bus -1 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus 3 (RP08)
acpiprt12 at acpi0: bus 4 (BR10)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu1 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu2 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu3 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu4 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu5 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu6 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpicpu7 at acpi0: C2(***@148 ***@0x31), C1(***@1 mwait.1), PSS
acpipwrres0 at acpi0: PG00, resource for PEG0
acpipwrres1 at acpi0: PG01, resource for PEG1
acpipwrres2 at acpi0: PG02, resource for PEG2
acpipwrres3 at acpi0: FN00, resource for FAN0
acpipwrres4 at acpi0: FN01, resource for FAN1
acpipwrres5 at acpi0: FN02, resource for FAN2
acpipwrres6 at acpi0: FN03, resource for FAN3
acpipwrres7 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"INT3F0D" at acpi0 not configured
"PNP0303" at acpi0 not configured
"PNP0501" at acpi0 not configured
"PNP0501" at acpi0 not configured
"IPI0001" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 3293 MHz: speeds: 3301, 3300, 3100, 2900, 2800,
2600, 2400, 2200, 2000, 1900, 1700, 1500, 1300, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Xeon E3-1200 v3 Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi
pci1 at ppb0 bus 1
nvme0 at pci1 dev 0 function 0 vendor "Samsung", unknown product 0xa804
rev 0x00: msi, NVMe 1.2
nvme0: Samsung SSD 960 EVO 1TB, firmware SNIP, serial SNIP
scsibus1 at nvme0: 1 targets
sd0 at scsibus1 targ 0 lun 0: <NVMe, Samsung SSD SNIP> SCSI4 0/direct
fixed
sd0: SNIP
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x05: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 1 not configured
ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 7 "Intel 8 Series PCIE" rev 0xd5: msi
pci3 at ppb2 bus 3
ppb3 at pci3 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x02
pci4 at ppb3 bus 4
vga1 at pci4 dev 0 function 0 "ASPEED Technology AST2000" rev 0x21
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 31 function 0 "Intel C226 LPC" rev 0x05
ahci0 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x05: msi,
AHCI 1.3
ahci0: port 3: 6.0Gb/s
scsibus2 at ahci0: 32 targets
sd1 at scsibus2 targ 3 lun 0: <ATA, Samsung SNIP> SCSI3 0/direct fixed
SNIP
sd1: SNIP
ichiic0 at pci0 dev 31 function 3 "Intel 8 Series SMBus" rev 0x05: apic
8 int 18
iic0 at ichiic0
sdtemp0 at iic0 addr 0x18: mcp98243
sdtemp1 at iic0 addr 0x1a: mcp98243
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM ECC PC3-12800 with thermal
sensor
spdmem1 at iic0 addr 0x52: 8GB DDR3 SDRAM ECC PC3-12800 with thermal
sensor
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
wbsio0 at isa0 port 0x2e/2: NCT6776F rev 0x33
lm1 at wbsio0 port 0x290/8: NCT6776F
uhub1 at uhub0 port 1 "American Megatrends Inc. Virtual Hub" rev
2.00/1.00 addr 2
uhidev0 at uhub1 port 4 configuration 1 interface 0 "American Megatrends
Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub1 port 4 configuration 1 interface 1 "American Megatrends
Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3
uhidev1: iclass 3/1
ums0 at uhidev1: 3 buttons, Z dir
wsmouse0 at ums0 mux 0
axen0 at uhub0 port 3 configuration 1 interface 0 "ASIX Elec. Corp.
AX88179" rev 2.10/1.00 addr 4
axen0: AX88179, address 00:11:6b:SNIP
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
cdce0 at uhub0 port 4 configuration 2 interface 0 "Linksys Linksys
USB3GIGV1" rev 2.10/30.00 addr 5
cdce0: address 14:91:82:SNIP
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
sd2 at scsibus4 targ 1 lun 0: (SNIP)
sd2: (SNIP)
root on sd2a (SNIP.a) swap on sd2b dump on sd2b

[Tinker]

Subsequently I realized that I had had the AXEN plugged in to a USB 2
port (together with an RTL8153 on the same root hub).

Now just minutes ago, I plugged it in to the USB 3 port (and the RTL8153
too) instead, and the AXEN appears to work well (!).


The related dmesg lines changed from showing them as being plugged in on
port "3" and "4" to now being plugged in to ports "16" and "17" on the
"Intel xHCI root hub" rev 3.00/1.00 addr 1:

axen0 at uhub0 port 16 configuration 1 interface 0 "ASIX Elec. Corp.
AX88179" rev 3.00/1.00 addr 4
axen0: AX88179, address 00:11:6b:SNIP
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
cdce0 at uhub0 port 17 configuration 2 interface 0 "Linksys Linksys
USB3GIGV1" rev 3.00/30.00 addr 5
cdce0: address 14:91:82:SNIP


I'll give it lots more testing and report back here in a couple of
weeks.

Tinker

Post by Tinker
So here is followup on the AXEN malfunctioning thread started 5 April
( http://marc.info/?t=149141061800001&r=1&w=2 ), for my AXEN-based
"Level1 USB-0401"
http://global.level1.com/Network-Card/USB-0401/p-3209.htm which
*should* just be another generic. It automatically attaches as axen0
when plugged in.
I left the AXEN for a couple of ways and got back to it last 3 days,
and it gave me all kinds of problems -
* Sometimes it works perfectly,
* Sometimes it stops suddenly, in particular ~30 seconds after boot,
* With no output to the console/dmesg,
IN_PROGRESS" + "usb error on tx: TIMEOUT" message,
* With an unending repeated printout of "checksum error (pkt#0)" +
"invalid buffer(pkt#65535), continue" in random constellations,
* Sometimes (though relatively rarely), system freeze.
To reduce the problem, I
* Tried attaching the AXEN on two different USB3 ports on the machine,
* I tried having the AXEN attached to two different ethernet devices
(a modem and a router), and
* I tried switching off and on the USB2 and USB3 "legacy mode":s in
the BIOS.
Maaybe there's less of the "stop working after ~30 seconds after boot"
thing after disabling USB legacy mode in BIOS, except for that no
difference in behavior between the different modes I tried.
Also whether the device was attached from boot or was reattached, does
not seem to affect whether the AXEN malfunctions/how much (despite my
initial choice of thread subject).
This leads me to believe that there's something universally wrong
about the AXEN device or driver - the only next thing to try would be
to try the AXEN on another computer.
I wanted to go deeper into the system freeze situation, so I enabled
ddb.console and got to reproduce the system freeze (by just rebooting
a couple of times and trying to communicate over the AXEN), and I had
a success with that within ~2 minutes.
Debugger() at Debugger+0x9
internal_command() at internal_command+0x155
wskbd_translate() at wskbd_translate+0x90
wskbd_input() at wskbd_input+0x55
pckbd_input() at pckbd_input+0xb4
pckbcintr_internal() at ckbcintr_internal+0x8e
intr_handler() at intr_handler+0x67
Xintr_ioapic_edge1() at Xintr_ioapic_edge1+0xc9
--- interrupt ---
memcpy() at memcpy+0xa
usb_transfer_complete() at usb_transfer_complete+0x26c
xhci_event_dequeue() at xhci_event_dequeue+0x65
xhci_softintr() at xhci_softintr+0x21
softintr_dispatch() at softintr_dispatch+0x8b
Xsoftnet() at Xsoftnet+0x1f
--- interrupt ---
end of kernel
end trace frame: 0x31, count: -14
The other CPU cores were all in x86_ip_handler().
Freshly booted machine, no interesting processes running.
I can provide you with the "show register" output however since it was
in the wskbd_translate() already I guess it's not relevant.
I guess the above proves my hypothesis that the machine freeze did
indeed have to do with the AXEN device or driver.
This is OpenBSD 6.0, however if I am reading
*
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axenreg.h
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axen.c
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhci.c
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhcireg.h
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhcivar.h
right then nothing relating to this error has changed since.
I would be happy to donate this AXEN device to a developer for you to
either blacklist it as officially unsupported by OpenBSD, or figure
what's wrong and make it work. If so please let me know your postal
address.
Also one more thing I coud do, would be to do "c"(continue) in DDB and
catch more different traces, to profile the error further. Also, I
could try to run the system without the CDCE (USB RTL8153 ethernet) I
have plugged in to the system, to reduce fruther.
* Anyone have a look at the above report
* I donate this AXEN to a developer, please let me know postal address
* I/anyone try this AXEN on another device
* I could try to reduce the case further by also removing the CDCE
device (an USB RTL8153 ethernet dongle)
* I/anyone reproduce the freeze and profile it further by doing
trace+"c"(continue) repeats in DDB.
Let me know next step.
Thanks!
Tinker
OpenBSD 6.0 (GENERIC.MP) #0: Thu Mar 23 03:06:38 GMT 2017
real mem = 17121271808 (16328MB)
avail mem = 16597905408 (15828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0: vendor American Megatrends Inc. version "P3.30" date 06/04/2015
bios0: ASRock E3C226D2I
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT AAFT SSDT SSDT MCFG PRAD
HPET SSDT SSDT SPMI UEFI DMAR
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4)
PEG2(S4) CIR_(S4) PS2K(S4) PS2M(S4) UR11(S4) UR12(S4) PXSX(S4)
BR11(S4) RP01(S4) PXSX(S4) RP02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 1, core 2, package 0
cpu7 at mainbus0: apid 7 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 1, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 2 (RP01)
acpiprt5 at acpi0: bus -1 (RP02)
acpiprt6 at acpi0: bus -1 (RP03)
acpiprt7 at acpi0: bus -1 (RP04)
acpiprt8 at acpi0: bus -1 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus 3 (RP08)
acpiprt12 at acpi0: bus 4 (BR10)
acpiec0 at acpi0: not present
acpipwrres0 at acpi0: PG00, resource for PEG0
acpipwrres1 at acpi0: PG01, resource for PEG1
acpipwrres2 at acpi0: PG02, resource for PEG2
acpipwrres3 at acpi0: FN00, resource for FAN0
acpipwrres4 at acpi0: FN01, resource for FAN1
acpipwrres5 at acpi0: FN02, resource for FAN2
acpipwrres6 at acpi0: FN03, resource for FAN3
acpipwrres7 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"INT3F0D" at acpi0 not configured
"PNP0303" at acpi0 not configured
"PNP0501" at acpi0 not configured
"PNP0501" at acpi0 not configured
"IPI0001" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 3293 MHz: speeds: 3301, 3300, 3100, 2900,
2800, 2600, 2400, 2200, 2000, 1900, 1700, 1500, 1300, 1200, 1000, 800
MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Xeon E3-1200 v3 Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi
pci1 at ppb0 bus 1
nvme0 at pci1 dev 0 function 0 vendor "Samsung", unknown product
0xa804 rev 0x00: msi, NVMe 1.2
nvme0: Samsung SSD 960 EVO 1TB, firmware SNIP, serial SNIP
scsibus1 at nvme0: 1 targets
sd0 at scsibus1 targ 0 lun 0: <NVMe, Samsung SSD SNIP> SCSI4 0/direct
fixed
sd0: SNIP
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x05: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 1 not configured
ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 7 "Intel 8 Series PCIE" rev 0xd5: msi
pci3 at ppb2 bus 3
ppb3 at pci3 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x02
pci4 at ppb3 bus 4
vga1 at pci4 dev 0 function 0 "ASPEED Technology AST2000" rev 0x21
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 31 function 0 "Intel C226 LPC" rev 0x05
ahci0 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x05: msi,
AHCI 1.3
ahci0: port 3: 6.0Gb/s
scsibus2 at ahci0: 32 targets
sd1 at scsibus2 targ 3 lun 0: <ATA, Samsung SNIP> SCSI3 0/direct fixed
SNIP
sd1: SNIP
ichiic0 at pci0 dev 31 function 3 "Intel 8 Series SMBus" rev 0x05: apic
8 int 18
iic0 at ichiic0
sdtemp0 at iic0 addr 0x18: mcp98243
sdtemp1 at iic0 addr 0x1a: mcp98243
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM ECC PC3-12800 with thermal
sensor
spdmem1 at iic0 addr 0x52: 8GB DDR3 SDRAM ECC PC3-12800 with thermal
sensor
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
wbsio0 at isa0 port 0x2e/2: NCT6776F rev 0x33
lm1 at wbsio0 port 0x290/8: NCT6776F
uhub1 at uhub0 port 1 "American Megatrends Inc. Virtual Hub" rev
2.00/1.00 addr 2
uhidev0 at uhub1 port 4 configuration 1 interface 0 "American
Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub1 port 4 configuration 1 interface 1 "American
Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3
uhidev1: iclass 3/1
ums0 at uhidev1: 3 buttons, Z dir
wsmouse0 at ums0 mux 0
axen0 at uhub0 port 3 configuration 1 interface 0 "ASIX Elec. Corp.
AX88179" rev 2.10/1.00 addr 4
axen0: AX88179, address 00:11:6b:SNIP
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
cdce0 at uhub0 port 4 configuration 2 interface 0 "Linksys Linksys
USB3GIGV1" rev 2.10/30.00 addr 5
cdce0: address 14:91:82:SNIP
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
sd2 at scsibus4 targ 1 lun 0: (SNIP)
sd2: (SNIP)
root on sd2a (SNIP.a) swap on sd2b dump on sd2b

[Tinker]

Not before long the AXEN would start malbehaving again.

Specifically, I would boot the machine - either from hard electricity
cut or just normal USB-on-CPU-off poweroff, the kernel would detect
AXEN0 on boot, and then the system would go into "starting network" and
run dhclient on the axen0.

This would lead to "checksum err (pkt#0)" + "invalid buffer(pkt#65535),
continue" kernel debug printouts around each DHCPREQUEST and
DHCPDISCOVER, and no data would go through, so eventually the dhclient
would fail.

The device produced the same behavior after replug.


(At one point the kernel printed out "arpresolve: unresolved and
rt_expire == 0" also however that may or may not have related to this.)

So this is on 6.0 generic (+ RTL8153 patch).

I talked to Yojiro and he said he'd generally check out how AXEN behaves
on latest OpenBSD now (the driver was implemented some while ago so the
USB subsystem may have changed a bit since he implemented it).


My impression is that the AXEN is a really nice piece of hardware,
better than the RTL8153, so it would be worthwhile to make it work
perfectly.

Not sure if these issues are local to my machine. Anyone else's
experience about how AXEN works or not works would be appreciated.

Tinker

Post by Tinker
Subsequently I realized that I had had the AXEN plugged in to a USB 2
port (together with an RTL8153 on the same root hub).
Now just minutes ago, I plugged it in to the USB 3 port (and the
RTL8153 too) instead, and the AXEN appears to work well (!).
The related dmesg lines changed from showing them as being plugged in
on port "3" and "4" to now being plugged in to ports "16" and "17" on
axen0 at uhub0 port 16 configuration 1 interface 0 "ASIX Elec. Corp.
AX88179" rev 3.00/1.00 addr 4
axen0: AX88179, address 00:11:6b:SNIP
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
cdce0 at uhub0 port 17 configuration 2 interface 0 "Linksys Linksys
USB3GIGV1" rev 3.00/30.00 addr 5
cdce0: address 14:91:82:SNIP
I'll give it lots more testing and report back here in a couple of
weeks.
Tinker

Post by Tinker
So here is followup on the AXEN malfunctioning thread started 5 April
( http://marc.info/?t=149141061800001&r=1&w=2 ), for my AXEN-based
"Level1 USB-0401"
http://global.level1.com/Network-Card/USB-0401/p-3209.htm which
*should* just be another generic. It automatically attaches as axen0
when plugged in.
I left the AXEN for a couple of ways and got back to it last 3 days,
and it gave me all kinds of problems -
* Sometimes it works perfectly,
* Sometimes it stops suddenly, in particular ~30 seconds after boot,
* With no output to the console/dmesg,
IN_PROGRESS" + "usb error on tx: TIMEOUT" message,
* With an unending repeated printout of "checksum error (pkt#0)" +
"invalid buffer(pkt#65535), continue" in random constellations,
* Sometimes (though relatively rarely), system freeze.
To reduce the problem, I
* Tried attaching the AXEN on two different USB3 ports on the machine,
* I tried having the AXEN attached to two different ethernet devices
(a modem and a router), and
* I tried switching off and on the USB2 and USB3 "legacy mode":s in
the BIOS.
Maaybe there's less of the "stop working after ~30 seconds after boot"
thing after disabling USB legacy mode in BIOS, except for that no
difference in behavior between the different modes I tried.
Also whether the device was attached from boot or was reattached, does
not seem to affect whether the AXEN malfunctions/how much (despite my
initial choice of thread subject).
This leads me to believe that there's something universally wrong
about the AXEN device or driver - the only next thing to try would be
to try the AXEN on another computer.
I wanted to go deeper into the system freeze situation, so I enabled
ddb.console and got to reproduce the system freeze (by just rebooting
a couple of times and trying to communicate over the AXEN), and I had
a success with that within ~2 minutes.
Debugger() at Debugger+0x9
internal_command() at internal_command+0x155
wskbd_translate() at wskbd_translate+0x90
wskbd_input() at wskbd_input+0x55
pckbd_input() at pckbd_input+0xb4
pckbcintr_internal() at ckbcintr_internal+0x8e
intr_handler() at intr_handler+0x67
Xintr_ioapic_edge1() at Xintr_ioapic_edge1+0xc9
--- interrupt ---
memcpy() at memcpy+0xa
usb_transfer_complete() at usb_transfer_complete+0x26c
xhci_event_dequeue() at xhci_event_dequeue+0x65
xhci_softintr() at xhci_softintr+0x21
softintr_dispatch() at softintr_dispatch+0x8b
Xsoftnet() at Xsoftnet+0x1f
--- interrupt ---
end of kernel
end trace frame: 0x31, count: -14
The other CPU cores were all in x86_ip_handler().
Freshly booted machine, no interesting processes running.
I can provide you with the "show register" output however since it was
in the wskbd_translate() already I guess it's not relevant.
I guess the above proves my hypothesis that the machine freeze did
indeed have to do with the AXEN device or driver.
This is OpenBSD 6.0, however if I am reading
*
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axenreg.h
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axen.c
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhci.c
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhcireg.h
* https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhcivar.h
right then nothing relating to this error has changed since.
I would be happy to donate this AXEN device to a developer for you to
either blacklist it as officially unsupported by OpenBSD, or figure
what's wrong and make it work. If so please let me know your postal
address.
Also one more thing I coud do, would be to do "c"(continue) in DDB and
catch more different traces, to profile the error further. Also, I
could try to run the system without the CDCE (USB RTL8153 ethernet) I
have plugged in to the system, to reduce fruther.
* Anyone have a look at the above report
* I donate this AXEN to a developer, please let me know postal address
* I/anyone try this AXEN on another device
* I could try to reduce the case further by also removing the CDCE
device (an USB RTL8153 ethernet dongle)
* I/anyone reproduce the freeze and profile it further by doing
trace+"c"(continue) repeats in DDB.
Let me know next step.
Thanks!
Tinker
OpenBSD 6.0 (GENERIC.MP) #0: Thu Mar 23 03:06:38 GMT 2017
real mem = 17121271808 (16328MB)
avail mem = 16597905408 (15828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0: vendor American Megatrends Inc. version "P3.30" date 06/04/2015
bios0: ASRock E3C226D2I
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT AAFT SSDT SSDT MCFG PRAD
HPET SSDT SSDT SPMI UEFI DMAR
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4)
PEG2(S4) CIR_(S4) PS2K(S4) PS2M(S4) UR11(S4) UR12(S4) PXSX(S4)
BR11(S4) RP01(S4) PXSX(S4) RP02(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 1, core 2, package 0
cpu7 at mainbus0: apid 7 (application processor)
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 1, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 2 (RP01)
acpiprt5 at acpi0: bus -1 (RP02)
acpiprt6 at acpi0: bus -1 (RP03)
acpiprt7 at acpi0: bus -1 (RP04)
acpiprt8 at acpi0: bus -1 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus 3 (RP08)
acpiprt12 at acpi0: bus 4 (BR10)
acpiec0 at acpi0: not present
acpipwrres0 at acpi0: PG00, resource for PEG0
acpipwrres1 at acpi0: PG01, resource for PEG1
acpipwrres2 at acpi0: PG02, resource for PEG2
acpipwrres3 at acpi0: FN00, resource for FAN0
acpipwrres4 at acpi0: FN01, resource for FAN1
acpipwrres5 at acpi0: FN02, resource for FAN2
acpipwrres6 at acpi0: FN03, resource for FAN3
acpipwrres7 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"INT3F0D" at acpi0 not configured
"PNP0303" at acpi0 not configured
"PNP0501" at acpi0 not configured
"PNP0501" at acpi0 not configured
"IPI0001" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 3293 MHz: speeds: 3301, 3300, 3100, 2900,
2800, 2600, 2400, 2200, 2000, 1900, 1700, 1500, 1300, 1200, 1000, 800
MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Xeon E3-1200 v3 Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi
pci1 at ppb0 bus 1
nvme0 at pci1 dev 0 function 0 vendor "Samsung", unknown product
0xa804 rev 0x00: msi, NVMe 1.2
nvme0: Samsung SSD 960 EVO 1TB, firmware SNIP, serial SNIP
scsibus1 at nvme0: 1 targets
sd0 at scsibus1 targ 0 lun 0: <NVMe, Samsung SSD SNIP> SCSI4 0/direct
fixed
sd0: SNIP
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x05: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 1 not configured
ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 7 "Intel 8 Series PCIE" rev 0xd5: msi
pci3 at ppb2 bus 3
ppb3 at pci3 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x02
pci4 at ppb3 bus 4
vga1 at pci4 dev 0 function 0 "ASPEED Technology AST2000" rev 0x21
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 31 function 0 "Intel C226 LPC" rev 0x05
ahci0 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x05: msi,
AHCI 1.3
ahci0: port 3: 6.0Gb/s
scsibus2 at ahci0: 32 targets
sd1 at scsibus2 targ 3 lun 0: <ATA, Samsung SNIP> SCSI3 0/direct fixed
SNIP
sd1: SNIP
apic 8 int 18
iic0 at ichiic0
sdtemp0 at iic0 addr 0x18: mcp98243
sdtemp1 at iic0 addr 0x1a: mcp98243
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM ECC PC3-12800 with thermal
sensor
spdmem1 at iic0 addr 0x52: 8GB DDR3 SDRAM ECC PC3-12800 with thermal
sensor
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
wbsio0 at isa0 port 0x2e/2: NCT6776F rev 0x33
lm1 at wbsio0 port 0x290/8: NCT6776F
uhub1 at uhub0 port 1 "American Megatrends Inc. Virtual Hub" rev
2.00/1.00 addr 2
uhidev0 at uhub1 port 4 configuration 1 interface 0 "American
Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub1 port 4 configuration 1 interface 1 "American
Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3
uhidev1: iclass 3/1
ums0 at uhidev1: 3 buttons, Z dir
wsmouse0 at ums0 mux 0
axen0 at uhub0 port 3 configuration 1 interface 0 "ASIX Elec. Corp.
AX88179" rev 2.10/1.00 addr 4
axen0: AX88179, address 00:11:6b:SNIP
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
cdce0 at uhub0 port 4 configuration 2 interface 0 "Linksys Linksys
USB3GIGV1" rev 2.10/30.00 addr 5
cdce0: address 14:91:82:SNIP
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
sd2 at scsibus4 targ 1 lun 0: (SNIP)
sd2: (SNIP)
root on sd2a (SNIP.a) swap on sd2b dump on sd2b