Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-09-12 Thread Mark Millard
On 2022-Sep-12, at 05:10, Dmitry Salychev wrote: > > Hi, > > It seems that the recent 14-CURRENT/aarch64 (866e021) with DPAA2 drivers > panics under network throughtput stress test in random places 3 of your examples get a signal handler called at the exact same instruction: #6

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-09-12 Thread Dmitry Salychev
(kgdb) bt #0 breakpoint () at /usr/src/sys/arm64/include/cpufunc.h:36 #1 kdb_enter (why=, msg=) at /usr/src/sys/kern/subr_kdb.c:508 #2 0x00460268 in vpanic (fmt=, ap=...) at /usr/src/sys/kern/kern_shutdown.c:967 #3 0x00460018 in panic (fmt=0x12 ) at

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-08 Thread bob prohaska
On Mon, Mar 07, 2022 at 11:45:02AM -0500, Mark Johnston wrote: > On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote: > > > > > On 7 Mar 2022, at 15:13, Mark Johnston wrote: > > > ... > > > A (the?) problem is that the compiler is treating "pc" as an alias > > > for x18, but the rmlock

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-08 Thread Andrew Turner
> On 7 Mar 2022, at 19:04, Mark Johnston wrote: > > On Mon, Mar 07, 2022 at 10:03:51AM -0800, Mark Millard wrote: >> >> >> On 2022-Mar-7, at 08:45, Mark Johnston wrote: >> >>> On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote: > On 7 Mar 2022, at 15:13, Mark Johnston

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Johnston
On Mon, Mar 07, 2022 at 09:54:26PM +0100, Ronald Klop wrote: > > Van: Mark Johnston > Datum: maandag, 7 maart 2022 16:13 > Aan: Ronald Klop > CC: bob prohaska , Mark Millard , > freebsd-...@freebsd.org, freebsd-current > > I haven't been able to reproduce any crashes running poudriere in an

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Millard
On 2022-Mar-7, at 12:54, Ronald Klop wrote: > Van: Mark Johnston > Datum: maandag, 7 maart 2022 16:13 > Aan: Ronald Klop > CC: bob prohaska , Mark Millard , > freebsd-...@freebsd.org, freebsd-current > Onderwerp: Re: panic: data abort in critical section or under mutex (was: Re: > panic:

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Ronald Klop
Van: Mark Johnston Datum: maandag, 7 maart 2022 16:13 Aan: Ronald Klop CC: bob prohaska , Mark Millard , freebsd-...@freebsd.org, freebsd-current Onderwerp: Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 200 (on

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Johnston
On Mon, Mar 07, 2022 at 10:03:51AM -0800, Mark Millard wrote: > > > On 2022-Mar-7, at 08:45, Mark Johnston wrote: > > > On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote: > >> > >>> On 7 Mar 2022, at 15:13, Mark Johnston wrote: > >>> ... > >>> A (the?) problem is that the

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Millard
On 2022-Mar-7, at 08:45, Mark Johnston wrote: > On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote: >> >>> On 7 Mar 2022, at 15:13, Mark Johnston wrote: >>> ... >>> A (the?) problem is that the compiler is treating "pc" as an alias >>> for x18, but the rmlock code assumes that

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Johnston
On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote: > > > On 7 Mar 2022, at 15:13, Mark Johnston wrote: > > ... > > A (the?) problem is that the compiler is treating "pc" as an alias > > for x18, but the rmlock code assumes that the pcpu pointer is loaded > > once, as it dereferences

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Andrew Turner
> On 7 Mar 2022, at 15:13, Mark Johnston wrote: > ... > A (the?) problem is that the compiler is treating "pc" as an alias > for x18, but the rmlock code assumes that the pcpu pointer is loaded > once, as it dereferences "pc" outside of the critical section. On > arm64, if a context switch

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Johnston
On Mon, Mar 07, 2022 at 02:46:09PM +0100, Ronald Klop wrote: > Dear Mark Johnston, > > I did some binary search in the kernels and came to the conclusion that > https://cgit.freebsd.org/src/commit/?id=1517b8d5a7f58897200497811de1b18809c07d3e > still works and >

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Mark Millard
On 2022-Mar-7, at 05:46, Ronald Klop wrote: > Dear Mark Johnston, > > I did some binary search in the kernels and came to the conclusion that > https://cgit.freebsd.org/src/commit/?id=1517b8d5a7f58897200497811de1b18809c07d3e > still works and >

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Ronald Klop
Dear Mark Johnston, I did some binary search in the kernels and came to the conclusion that https://cgit.freebsd.org/src/commit/?id=1517b8d5a7f58897200497811de1b18809c07d3e still works and https://cgit.freebsd.org/src/commit/?id=407c34e735b5d17e2be574808a09e6d729b0a45a panics. I suspect

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-07 Thread Ronald Klop
Yes, I spoke to soon too. Often it crashes as soon as I start a parallel poudriere build. But this time it went very far. As soon as nightly backups kicked in it was game over again. I had read the mail of Bob on the arm@ ML. But I wanted to let the conclusion that it is about the same problem

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-06 Thread Mark Millard
From: Ronald Klop wrote on Date: Sun, 6 Mar 2022 23:22:42 +0100 (CET) : > Did some binary search with kernels from artifact.ci.freebsd.org. > > I suspect "rmlock: Micro-optimize read locking" as cause. > > https://cgit.freebsd.org/src/commit/?id=c84bb8cd771ce4bed58152e47a32dda470bef23a > > >

Re: panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-06 Thread Ronald Klop
Hi, Did some binary search with kernels from artifact.ci.freebsd.org. I suspect "rmlock: Micro-optimize read locking" as cause. https://cgit.freebsd.org/src/commit/?id=c84bb8cd771ce4bed58152e47a32dda470bef23a And "rmlock: Add required compiler barriers to _rm_runlock()" as solution.

panic: data abort in critical section or under mutex (was: Re: panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb 28))

2022-03-05 Thread Ronald Klop
Hi, Another panic while building world/kernel. Different panic message and trace. x0: 1f5e152c32cc x1: b630a000 (g_ctx + b4c4a254)