Hi, checksum err (pkt#1) appears in dmesg output only.
Right now (after 43 hours of testing) there are 15 rows with checksum err (pkt#1) message. Previously, that network segment was connected by em(4), fxp(4), xl(4) drivers w/o any issues. So the error appears for axen(4) driver exclusively. It seems axen(4) related issue. Denis On 8/17/2018 6:26 PM, sc dying wrote: > 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. >>>
