Re: Possible hacking project-- axe driver

[Hal Pomeranz]

 watchdog timeouts are more often than not problems with interrupt
 routing.  Can you include the rest of your dmesg?

Sure thing.  See below.  Not much there, unfortunately.

The last two lines are from when I physically removed the device
from the USB port.

--Hal


# dmesg
OpenBSD 5.1 (GENERIC) #160: Sun Feb 12 09:46:33 MST 2012
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Celeron(R) CPU 1.80GHz (GenuineIntel 686-class) 1.80 GHz
cpu0: 
FPU,V86,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
real mem  = 267911168 (255MB)
avail mem = 253435904 (241MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/02/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS 
rev. 2.3 @ 0xfae50 (77 entries)
bios0: vendor Dell Computer Corporation version A03 date 06/02/2003
bios0: Dell Computer Corporation PowerEdge 650
acpi0 at bios0: rev 0
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR
acpi0: wakeup devices PCI0(S5) PCI1(S5) PCI2(S5)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 16 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
ioapic1 at mainbus0: apid 2 pa 0xfec01000, version 11, 16 pins
ioapic1: misconfigured as apic 0, remapped to apid 2
ioapic2 at mainbus0: apid 3 pa 0xfec02000, version 11, 16 pins
ioapic2: misconfigured as apic 0, remapped to apid 3
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PCI1)
acpiprt2 at acpi0: bus 2 (PCI2)
acpicpu0 at acpi0
bios0: ROM list: 0xc/0x8000 0xc8000/0x6a00 0xec000/0x4000!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 ServerWorks GCNB-LE Host rev 0x32
pchb1 at pci0 dev 0 function 1 ServerWorks GCNB-LE Host rev 0x00
pci1 at pchb1 bus 1
em0 at pci1 dev 3 function 0 Intel PRO/1000MT (82546EB) rev 0x01: apic 2 int 
3, address 00:04:23:5f:20:98
em1 at pci1 dev 3 function 1 Intel PRO/1000MT (82546EB) rev 0x01: apic 2 int 
4, address 00:04:23:5f:20:99
ahc0 at pci0 dev 3 function 0 Adaptec AHA-3960D U160 rev 0x01: apic 2 int 1
scsibus0 at ahc0: 16 targets, initiator 7
sd0 at scsibus0 targ 0 lun 0: IBM, IC35L036UWDY10-0, S27F SCSI3 0/direct 
fixed naa.5005076718c7a08f
sd0: 34732MB, 512 bytes/sector, 71132959 sectors
ahc1 at pci0 dev 3 function 1 Adaptec AHA-3960D U160 rev 0x01: apic 2 int 2
scsibus1 at ahc1: 16 targets, initiator 7
vga1 at pci0 dev 4 function 0 ATI Rage XL rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
piixpm0 at pci0 dev 15 function 0 ServerWorks CSB6 rev 0xa0: SMBus disabled
pciide0 at pci0 dev 15 function 1 ServerWorks CSB6 RAID/IDE rev 0xa0: DMA
atapiscsi0 at pciide0 channel 0 drive 0
scsibus2 at atapiscsi0: 2 targets
cd0 at scsibus2 targ 0 lun 0: TEAC, CD-224E, K.9A ATAPI 5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2
ohci0 at pci0 dev 15 function 2 ServerWorks CSB6 USB rev 0x05: apic 1 int 10, 
version 1.0, legacy support
pcib0 at pci0 dev 15 function 3 ServerWorks GCLE-2 Host rev 0x00
pchb2 at pci0 dev 16 function 0 ServerWorks CIOB-E rev 0x12
pchb3 at pci0 dev 16 function 2 ServerWorks CIOB-E rev 0x12
pci2 at pchb3 bus 2
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 ServerWorks OHCI root hub rev 1.00/1.00 addr 1
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
mtrr: Pentium Pro MTRR support
ahc0: target 0 using 16bit transfers
ahc0: target 0 synchronous at 80.0MHz DT, offset = 0x7f
axe0 at uhub0 port 2 configuration 1 interface 0 ASIX Electronics AX88178 rev 
2.00/0.01 addr 2
axe0: AX88178, address 00:0e:c6:88:e0:ec
rgephy0 at axe0 phy 2: RTL8169S/8110S PHY, rev. 2
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
root on sd0a swap on sd0b dump on sd0b
axe0: watchdog timeout
axe0: usb error on tx: TIMEOUT
rgephy0 detached
axe0 detached

Re: Possible hacking project-- axe driver

[Jonathan Gray]

On Sun, Jun 10, 2012 at 07:46:20AM -0700, Hal Pomeranz wrote:
  watchdog timeouts are more often than not problems with interrupt
  routing.  Can you include the rest of your dmesg?
 
 Sure thing.  See below.  Not much there, unfortunately.
 
 The last two lines are from when I physically removed the device
 from the USB port.

Perhaps it is related to the ohci (USB1) controller it is plugged
in to.  Do you have another machine with ehci/USB2 you can try
the adapter with?

Possible hacking project-- axe driver

[Hal Pomeranz]

I purchased one of these USB ethernet adaptors to add an extra
interface to one of my OpenBSD devices:

http://www.amazon.com/Plugable-Gigabit-Ethernet-Network-Adapter/dp/B003VSTDFG

It's an AX88178 chipset device, and so should be supported by the
axe driver.  Indeed, when plugged into my OpenBSD 5.1 system it
is recognized:

axe0 at uhub0 port 2 configuration 1 interface 0 ASIX Electronics 
AX88178 rev 2.00/0.01 addr 2
axe0: AX88178, address 00:0e:c6:88:e0:ec
rgephy0 at axe0 phy 2: RTL8169S/8110S PHY, rev. 2

The interface is configured during the normal boot process and I can
even view packets via the network interface with tcpdump.  However,
the device never successfully transmits packets.  tcpdump on the OpenBSD
machine shows the device attempting to send packets, but tcpdump on
other network hosts shows no packets actually being emitted onto the wire.

dmesg shows the following errors:

axe0: watchdog timeout
axe0: usb error on tx: TIMEOUT

So the packets are getting queued up on the outgoing interface but
never actually getting transmitted?  Odd problem.

I'm happy to donate the device I purchased to whoever would like to
take a shot at fixing the problem.  Could be a fun hacking project,
but I personally just don't have time to work on it.  Contact me
off-list and I'll arrange to have the dongle shipped to you.

Cheers!

Hal Pomeranz

Re: Possible hacking project-- axe driver

[Jonathan Gray]

watchdog timeouts are more often than not problems with interrupt
routing.  Can you include the rest of your dmesg?

On Sat, Jun 09, 2012 at 03:57:40PM -0700, Hal Pomeranz wrote:
 I purchased one of these USB ethernet adaptors to add an extra
 interface to one of my OpenBSD devices:
 
 http://www.amazon.com/Plugable-Gigabit-Ethernet-Network-Adapter/dp/B003VSTDFG
 
 It's an AX88178 chipset device, and so should be supported by the
 axe driver.  Indeed, when plugged into my OpenBSD 5.1 system it
 is recognized:
 
   axe0 at uhub0 port 2 configuration 1 interface 0 ASIX Electronics 
 AX88178 rev 2.00/0.01 addr 2
   axe0: AX88178, address 00:0e:c6:88:e0:ec
   rgephy0 at axe0 phy 2: RTL8169S/8110S PHY, rev. 2
 
 The interface is configured during the normal boot process and I can
 even view packets via the network interface with tcpdump.  However,
 the device never successfully transmits packets.  tcpdump on the OpenBSD
 machine shows the device attempting to send packets, but tcpdump on
 other network hosts shows no packets actually being emitted onto the wire.
 
 dmesg shows the following errors:
 
   axe0: watchdog timeout
   axe0: usb error on tx: TIMEOUT
 
 So the packets are getting queued up on the outgoing interface but
 never actually getting transmitted?  Odd problem.
 
 I'm happy to donate the device I purchased to whoever would like to
 take a shot at fixing the problem.  Could be a fun hacking project,
 but I personally just don't have time to work on it.  Contact me
 off-list and I'll arrange to have the dongle shipped to you.
 
 Cheers!
 
 Hal Pomeranz