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
Thank you for taking care of axen(4).
The problems with this driver have been known for some time.
On Tue, Aug 07, 2018 at 02:04:24PM +, sc.dy...@gmail.com wrote:
> - header: fix comments
> - header: fix unused L3 type mask definition
> - rxeof: Avoid allocating mbuf if checksum errors are
Hi,
The issue is reproducible with the latest available 6.4-beta snapshot as
i'm writing this mail.
kern.version=
OpenBSD 6.4-beta (GENERIC.MP) #829: Thu Aug 16 18:42:18 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
This time i'm joining a proper ddb trace and regi
Hi,
On 2018/08/18 07:37, Denis wrote:
> 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
Yes, netstat -in on em(4), fxp(4), xl(4) Ierrs=0 / Oerrs=0 for months.
axen4.diff has been applied. Testing.
On 8/18/2018 4:32 PM, sc.dy...@gmail.com wrote:
> Hi,
>
> On 2018/08/18 07:37, Denis wrote:
>> Hi,
>>
>> checksum err (pkt#1) appears in dmesg output only.
>>
>> Right now (after 43 hours
>Synopsis: Kernel panic in xhci.c when Android phone with ADB
> connected
>Category: kernel
>Environment:
System : OpenBSD 6.4
Details : OpenBSD 6.4-beta (GENERIC.MP) #224: Fri Aug 17 23:42:30
MDT 2018
dera...@amd64.openbsd
Hi,
I would like to amend the above bug report. When reproducing I
originally said it could be reproduced when the Android device was
just plugged in.
After going over my notes, and doing more testing, I found it only
occurs when 'adb start-server' is running AND the device is plugged in
via
Hi there
The system as below will suspend and resume OK (-S/-z/-Z) except for lingering
ACPI activity that never goes away and causes a bit of lagginess. The ACPI
interference doesn't occur after a normal boot. Output below from systat a few
minutes after resuming shows the large numer of ACPI