Hello Alexandr, hello Alexander,
> does your box run also diff committed [1] by bluhm@ ~week ago?
No, I didn't. I missed that diff. I upgraded to a new snapshot yesterday. I
works fine as far.
OpenBSD 7.2-beta (GENERIC.MP) #712: Mon Aug 29 12:35:51 MDT 2022
[email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Thank you Alexander for your extensive explanation of the proper ddb commands
order.
Radek
On Mon, 29 Aug 2022 12:30:31 +0200
Alexander Bluhm <[email protected]> wrote:
> On Mon, Aug 29, 2022 at 04:42:45AM +0200, Radek wrote:
> > the same problem occurs on -current.
>
> It is not the same problem. Traces are different. But I guess
> your setup triggers some sort of race.
>
> Previous crashes with 7.1 were in route and IPsec, now it is in pf.
> Unfortunately you missed my pf fragment fix by a couple of hours.
> Please try a newer snapshot.
>
> OpenBSD 7.2-beta (GENERIC.MP) #705: Mon Aug 22 12:25:07 MDT 2022
> Changes by: [email protected] 2022/08/22 14:35:39
>
> I could not figure out what is wrong with 7.1-stable crashes. The
> register and ps output are not from the CPU where the crash happened.
> You have to run show register and ps before switching CPU with mach
> ddbcpu.
>
> So first run show panic. Then trace, show register, ps.
> Finally inspect the other CPU with mach ddbcpu.
>
> The number in ddb{2}> prompt shows the CPU you are currently on.
> If "show panic" mentions more than one CPU, the one with the * is
> the interresting one. Usually ddb drops to that initially. Traces
> from other CPU help to see if something was running concurrently.
>
> bluhm
>
Radek
