Re: axen Ethernet device errors on both USB3.0 and USB2.0 ports
Hi, On 2018/08/17 07:40, Denis wrote: > Hi, > > 24 hour full load testing shows positive results. Good news. > > After axen3.diff has been implemented there is no TX/RX error present at > all. But 'checksum err (pkt#1)' appears repeatedly like this: > > ... > checksum err (pkt#1) > checksum err (pkt#1) > checksum err (pkt#1) > ... > > You're right DHCP client is working for axen0: > > # cat /etc/hostname.axen0 > dhcp lladdr yy.yy.yy.yy.yy > > What can cause 'checksum err (pkt#1)' for axen? It might be another bug of axen(4), or someone on your ethernet segment really sends bogus packets. In latter case I don't think axen should report each error to the console. > > Denis > > On 8/15/2018 2:29 AM, sc.dy...@gmail.com wrote: >> Hi, >> >> On 2018/08/14 08:19, Denis wrote: >>> I have 6.3 kernel compiled with option XHCI_debug and axen2.diff >>> implemented. >>> >>> I'm using lladdr option for /etc/hostname.axen0 to have the same IP addr >>> each session for different Ehternet adapters. >>> >>> Here is debug output when axen is connected: >> >> Thank you for sending report. >> >> It looks someone (maybe DHCP) makes the interface down and up repeatedly. >> That causes TXERR (transaction error) on RX pipe. >> I guess there is something inconsistent between the state of xhci and >> the device. xhci spec 1.1 sec 4.3.5 requires the driver shall do >> set_config and configure endpoint. >> >> I added set_config part to axen2.diff and attached as axen3.diff. >> Can you try attached axen3.diff? >> >> Thanks. >>
Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)
I realized after the fact that was from the last bsd.rd boot. Here is the latest dmesg after a regular boot. On Wed, 15 Aug 2018 at 15:10, geannie wrote: > > dmesg.txt is attached. > On Wed, 15 Aug 2018 at 10:41, Stuart Henderson wrote: > > > > On 2018/08/15 10:28, geannie wrote: > > > >Have you tried older versions as well or just 6.3 / 6.4-beta? If you've > > > >tried older, are they also failing on this machine? Or, if older ones are > > > >working, what's the first one that fails? > > > > > > Working backwards, I wound up trying 5.5 and 5.6, but I was unable to > > > type at the install prompt. > > > > > > Next, I successfully installed 5.7 through 6.2. Each of these then > > > panicked on mii_phy_setmedia on first boot. > > > > Thanks for testing those, if one of them had booted it would point us > > in the direction of a commit that broke things. > > > > > >Did bsd.rd work? Or did you do the install some other way (not directly > > > >on the machine, or with bge disabled)? > > > > > > bsd.rd worked. > > > > > > Booting without hostname.bge0 is enough to boot normally, but dhclient > > > or ifconfig causes panic. > > > > Next suggestion is to boot -current (without hostname.bge0) and get > > a dmesg that you can copy into an email (either transferring it via > > USB stick or another NIC if you have one - USB NICs are often handy > > for this) so we can see what the hardware is. > > > > I think the NIC you mentioned as being "Broadcom 762" is actually > > BCM5762 but the dmesg would give more accurate information about this. > > OpenBSD 6.4-beta (GENERIC.MP) #213: Wed Aug 15 00:01:00 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16070709248 (15326MB) avail mem = 15574458368 (14852MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe879c (49 entries) bios0: vendor Hewlett-Packard version "L06 v02.17" date 12/11/2014 bios0: Hewlett-Packard HP EliteDesk 705 G1 DM acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SLIC TCPA UEFI IVRS SSDT SSDT CRAT SSDT SSDT acpi0: wakeup devices X16K(S4) X04K(S4) SBAZ(S4) PS2K(S3) PS2M(S3) ECIR(S4) P0PC(S4) X11_(S4) LOM_(S4) X12_(S4) BNIC(S4) OHC1(S3) EHC1(S3) OHC2(S3) EHC2(S3) OHC3(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD A8 PRO-7600B R7, 10 Compute Cores 4C+6G, 3095.54 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu0: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD A8 PRO-7600B R7, 10 Compute Cores 4C+6G, 3094.22 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu1: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD A8 PRO-7600B R7, 10 Compute Cores 4C+6G, 3094.22 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu2: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD A8 PRO-7600B R7, 10 Compute Cores 4C+6G, 3094.22 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT
Re: axen Ethernet device errors on both USB3.0 and USB2.0 ports
Hi, 24 hour full load testing shows positive results. After axen3.diff has been implemented there is no TX/RX error present at all. But 'checksum err (pkt#1)' appears repeatedly like this: ... checksum err (pkt#1) checksum err (pkt#1) checksum err (pkt#1) ... You're right DHCP client is working for axen0: # cat /etc/hostname.axen0 dhcp lladdr yy.yy.yy.yy.yy What can cause 'checksum err (pkt#1)' for axen? Denis On 8/15/2018 2:29 AM, sc.dy...@gmail.com wrote: > Hi, > > On 2018/08/14 08:19, Denis wrote: >> I have 6.3 kernel compiled with option XHCI_debug and axen2.diff >> implemented. >> >> I'm using lladdr option for /etc/hostname.axen0 to have the same IP addr >> each session for different Ehternet adapters. >> >> Here is debug output when axen is connected: > > Thank you for sending report. > > It looks someone (maybe DHCP) makes the interface down and up repeatedly. > That causes TXERR (transaction error) on RX pipe. > I guess there is something inconsistent between the state of xhci and > the device. xhci spec 1.1 sec 4.3.5 requires the driver shall do > set_config and configure endpoint. > > I added set_config part to axen2.diff and attached as axen3.diff. > Can you try attached axen3.diff? > > Thanks. > >> >> xhci0: port=2 change=0x04 >> xhci0: port=2 change=0x04 >> xhci0: xhci_cmd_slot_control >> xhci0: dev 1, input=0xff0001988000 slot=0xff0001988020 >> ep0=0xff0001988040 >> xhci0: dev 1, setting DCBAA to 0x01989000 >> xhci_pipe_init: pipe=0x80a8d000 addr=0 depth=1 port=2 speed=4 >> dev 1 dci 1 (epAddr=0x0) >> xhci0: xhci_cmd_set_address BSR=1 >> xhci0: xhci_cmd_set_address BSR=0 >> xhci0: dev 1 addr 1 >> axen0 at uhub0 port 2 configuration 1 interface 0 "ASIX Elec. Corp. >> AX88179" rev 3.00/1.00 addr 2 >> axen0: AX88179, address xx:xx:xx:xx:xx:xx >> ukphy0 at axen0 phy 3: Generic IEEE 802.3u media interface, rev. 5: OUI >> 0x000732, model 0x0011 >> xhci_pipe_init: pipe=0x80b38000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 5 (epAddr=0x82) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x80bfc000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 6 (epAddr=0x3) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_abort_xfer: xfer=0xff044e6aee10 status=IN_PROGRESS >> err=CANCELLED actlen=0 len=65536 idx=0 >> xhci0: xhci_cmd_stop_ep dev 1 dci 5 >> xhci_event_xfer: stopped xfer=0xff044e6aee10 >> xhci0: xhci_cmd_set_tr_deq_async dev 1 dci 5 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x80b3a000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 5 (epAddr=0x82) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x80b3e000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 6 (epAddr=0x3) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_abort_xfer: xfer=0xff044e6aed20 status=IN_PROGRESS >> err=CANCELLED actlen=0 len=65536 idx=42 >> xhci0: xhci_cmd_stop_ep dev 1 dci 5 >> xhci_event_xfer: stopped xfer=0xff044e6aed20 >> xhci0: xhci_cmd_set_tr_deq_async dev 1 dci 5 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x8079 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 5 (epAddr=0x82) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x80791000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 6 (epAddr=0x3) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: txerr? code 4 >> axen0: usb errors on rx: IOERROR >> xhci_abort_xfer: xfer=0xff044e6aee10 status=NOT_STARTED >> err=CANCELLED actlen=0 len=65536 idx=-1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x807a9000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 5 (epAddr=0x82) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x807aa000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 6 (epAddr=0x3) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: txerr? code 4 >> axen0: usb errors on rx: IOERROR >> xhci0: txerr? code 4 >> axen0: usb error on tx: IOERROR >> axen0: watchdog timeout >> axen0: usb error on tx: IOERROR >> xhci_abort_xfer: xfer=0xff044e6aed20 status=NOT_STARTED >> err=CANCELLED actlen=0 len=65536 idx=-1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x80865000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 5 (epAddr=0x82) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x80866000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 6 (epAddr=0x3) >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: txerr? code 4 >> axen0: usb errors on rx: IOERROR >> xhci0: txerr? code 4 >> axen0: usb error on tx: IOERROR >> xhci_abort_xfer: xfer=0xff044e6aee10 status=NOT_STARTED >> err=CANCELLED actlen=0 len=65536 idx=-1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci0: xhci_cmd_configure_ep dev 1 >> xhci_pipe_init: pipe=0x8087e000 addr=2 depth=1 port=2 speed=4 >> dev 1 dci 5 (epAddr=0x82) >> xhci0: xhci_cmd_configur
