Hello Samuel,

I think you should give a chance to this commit:

https://github.com/openbsd/src/commit/73fb5aae645f3bc12746fd705a937dfc9f9abc01

I hope it works for you.

--
Valdrin
________________________________
From: owner-m...@openbsd.org <owner-m...@openbsd.org> on behalf of Samuel 
Jayden <samueljaydan1...@gmail.com>
Sent: Wednesday, January 31, 2024 10:29
To: misc@openbsd.org <misc@openbsd.org>
Subject: Re: DDB Crash Report About if_ether.c and arpinit() Gelen Kutusu

Hello again,

My device continues to crash almost every single day.
Unfortunately, due to the system freeze, I'm unable to generate a crash
report. These crashes typically result in the following errors:

kernel : protection fault trap, code=0
Stopped at arptimer+0x45: movq 0x10(%r15),%rdi
ddb{0}>

Is there a solution to this issue? What steps should I take?
Thanks.


On Sat, Jan 27, 2024 at 10:51 AM Samuel Jayden <samueljaydan1...@gmail.com>
wrote:

> Hello Misc,
>
> My OpenBSD 7.4 crash with this error messages;
>
> panic: kernel diagnostic assertion "ifp != NULL" failed: file
> "/usr/src/sys/net/inet/if_ether.c", line 758
>
> Stopped at         db_enter+0x14:     popq     %rbp
>    TID      PID     UID       PRFLAGS   PFLAGS   CPU    COMMAND
>  399412   73118    77       0x1000012         0   10    dhcpleased
>  360364   39155   115       0x1000012         0   11    slaacd
>  155433   90182     0        0x14000      0x200    2    softnet0
>  162438   45442     0        0x14000      0x200    4    systq
> * 37835   96688     0        0x14000 0x40000200    0    softclock
> db_enter() at db_enter+0x14
> panic(ffffffff820a8599) at panic+0xc3
> __assert(ffffffff821232bc,ffffffff8209baea,2f6,ffffffff820712c0) at
> __assert+0x29
> arpinit() at arpinit
> arptimer(ffffffff825a38e8) at arptimer+0x5f
> softclock_thread(ffffffff800021c1fd48) at softclock_thread+0x12b
> end trace frame: 0x0, count: 9
> https://www.openbsd.org/ddb.html describes the minimum info required in
> bug reports. Insufficient info makes it difficult to find and fix bugs.
> ddb{0}>
>
> Dmesg output of my device is in the attachment.
>
> Thank you in advance for your interest.
>

Reply via email to