Re: axen(4) usb ethernet problems

[gwes]

On 10/14/2016 03:35, Mark Carroll wrote:

On 13 Oct 2016, Ilya Kaliman wrote:


I have a "Plugable USB 3.0 ethernet adapter" with ASIX AX88179
chipset. The device is successfully recognized by axen(4) driver but
behaves strangely. When I plug in the ethernet cable the ifconfig
axen0 status says active and the leds start blinking. But after a
second or two both leds turn off and status says: no carrier.
Re-plugging the cable have no effect. Re-plugging the adapter itself
brings it up again for a second or two.

The device itself seems to be fine as it works in other OSes without
problems. I suspect it has to do with OpenBSD driver.


I'm afraid that I can't offer any useful help but I can at least confirm
the problem: I also have one of these devices (actually, maybe a couple)
and see exactly the same issue with OpenBSD, at least with 5.9, I didn't
try since with 6.0. At the time I chatted to a competent-seeming vendor
guy and apparently they've seen the same problem at their end with
OpenBSD and have no idea what the issue is. So, at least I can say:
you're correct, it's probably indeed not just that you have a bad
adapter. I don't know if any developers might like to have one of these
mailed to them.

-- Mark


I have this:
Oct 15 00:01:57 river /bsd: axe0 at uhub1
Oct 15 00:01:57 river /bsd:  port 3 configuration 1 interface 0 "Belkin 
Components F5D5055" rev 2.00/0.01 addr 6

Oct 15 00:01:57 river /bsd: axe0: AX88178, address 00:22:75:d7:1c:6d
Oct 15 00:01:57 river /bsd: ukphy0 at axe0 phy 1: Generic IEEE 802.3u 
media interface, rev. 4: OUI 0x00a0bc, model 0x0001


which had similar symptoms under 5.8. It seems to be usable under 5.9

the FreeBSD driver definitely works. Porting it or adapting it without 
the data sheet looks difficult and comments in the FreeBSD driver say 
that there are undocumented problems. Haven't looked at Linux drivers. 
They have worked for several years.


One clue from looking at the drivers is that the physical interface 
number in the OpenBSD driver was fixed at 0 and it appears that other 
drivers searched for the active one.


geoff steckel

Re: axen(4) usb ethernet problems

[Ilya Kaliman]

I've tried both 6.0 and current with same results. Here is a dmesg:
=
OpenBSD 6.0-current (GENERIC.MP) #10: Mon Oct 10 14:42:44 PDT 2016
i...@puffy.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 80
real mem = 8468033536 (8075MB)
avail mem = 8206884864 (7826MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6a80 (27 entries)
bios0: vendor Insyde Corp. version "V2.12" date 05/20/2014
bios0: Acer Aspire S7-392
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP TCPA UEFI FPDT MSDM ASF! HPET APIC MCFG SSDT
BOOT ASPT DBGP SSDT SSDT SSDT SSDT SSDT DMAR
acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3)
HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4)
PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.71 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADL
INE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BM
I1,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.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADL
INE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BM
I1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADL
INE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BM
I1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADL
INE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BM
I1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus -1 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus 1 (RP03)
acpiprt5 at acpi0: bus -1 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus -1 (RP07)
acpiprt9 at acpi0: bus -1 (RP08)
acpiprt10 at acpi0: bus -1 (PEG0)
acpiprt11 at acpi0: bus -1 (PEG1)
acpiprt12 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 99 degC
acpitz1 at acpi0: critical temperature is 98 degC
acpials0 at acpi0: ALSD
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model "AP13F3N" serial  2358 type LION oem
acpibtn0 at acpi0: PWRB
"10250759" at acpi0 not configured
"SYN1B78" at acpi0 not configured
"PNP0C14" at acpi0 not configured
dwiic0 at acpi0: I2C1 addr 0xfe105000/0x1000 irq 7
iic0 at dwiic0
"BCM2E4E" at acpi0 not configured
acpibtn1 at acpi0: LID0
acpibtn2 at acpi0: SLPB
"PNP0C14" at acpi0 not configured
"INT340E" at acpi0 not configured
"INT33A0" at acpi0 not configured
tpm0 at acpi0: TPM_ addr 0xfed4/0x5000: Infineon SLB9635 1.2 rev 0x10
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 1596 MHz: speeds: 2401

Re: axen(4) usb ethernet problems

[Remi Locherer]

On Thu, Oct 13, 2016 at 05:40:18PM -0700, Ilya Kaliman wrote:
> Hi!
> 
> I have a "Plugable USB 3.0 ethernet adapter" with ASIX AX88179
> chipset. The device is successfully recognized by axen(4) driver but
> behaves strangely. When I plug in the ethernet cable the ifconfig
> axen0 status says active and the leds start blinking. But after a
> second or two both leds turn off and status says: no carrier.
> Re-plugging the cable have no effect. Re-plugging the adapter itself
> brings it up again for a second or two.
> 
> The device itself seems to be fine as it works in other OSes without
> problems. I suspect it has to do with OpenBSD driver.
> 
> I have axen(4) driver compiled with debug - it prints a lot of stuff,
> but nothing that seem to indicate an error. Can anyone give some
> pointers on how to diagnose the problem?
> 
> Thanks,
> Ilya

What version of OpenBSD are you running? Usually it's best to add the
output of dmesg to such a mail to give others an idea what you are
running.

There was a change to axen in March this year that made my adapter
work reliably. It ships with 6.0.

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_axen.c

Remi

Re: axen(4) usb ethernet problems

[Mark Carroll]

On 13 Oct 2016, Ilya Kaliman wrote:

> I have a "Plugable USB 3.0 ethernet adapter" with ASIX AX88179
> chipset. The device is successfully recognized by axen(4) driver but
> behaves strangely. When I plug in the ethernet cable the ifconfig
> axen0 status says active and the leds start blinking. But after a
> second or two both leds turn off and status says: no carrier.
> Re-plugging the cable have no effect. Re-plugging the adapter itself
> brings it up again for a second or two.
>
> The device itself seems to be fine as it works in other OSes without
> problems. I suspect it has to do with OpenBSD driver.

I'm afraid that I can't offer any useful help but I can at least confirm
the problem: I also have one of these devices (actually, maybe a couple)
and see exactly the same issue with OpenBSD, at least with 5.9, I didn't
try since with 6.0. At the time I chatted to a competent-seeming vendor
guy and apparently they've seen the same problem at their end with
OpenBSD and have no idea what the issue is. So, at least I can say:
you're correct, it's probably indeed not just that you have a bad
adapter. I don't know if any developers might like to have one of these
mailed to them.

-- Mark