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
(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
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
> 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
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
(was: Re:
> panic: Unknown kernel exception 0 esr_el1 200 (on 14-CURRENT/aarch64 Feb
> 28))
>
> 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 t
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 14-CURRENT
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
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
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
> 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
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
>
r_demux() at ether_demux+0x178
> ether_nh_input() at ether_nh_input+0x3e8
> netisr_dispatch_src() at netisr_dispatch_src+0xe4
> ether_input() at ether_input+0x80
> if_input() at if_input+0xc
> gen_intr() at gen_intr+0x444
> ithread_loop() at ithread_loop+0x2a0
> fork_exit() at
tex (was: Re:
panic: Unknown kernel exception 0 esr_el1 2000000 (on 14-CURRENT/aarch64 Feb
28))
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 m
ection or under mutex (was: Re:
panic: Unknown kernel exception 0 esr_el1 200 (on 14-CURRENT/aarch64 Feb
28))
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-o
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
>
>
>
>
Regards,
Ronald.
Van: Ronald Klop
Datum: zaterdag, 5 maart 2022 12:16
Aan: FreeBSD Current
Onderwerp: panic: Unknown kernel exception 0 esr_el1 200 (on
14-CURRENT/aarch64 Feb 28)
Hi,
Repeated panics on 14-CURRENT/aarch64. This happens e.g. when the nigthly
backup is started.
# una
nic: Unknown kernel exception 0 esr_el1 2000000 (on
14-CURRENT/aarch64 Feb 28)
Hi,
Repeated panics on 14-CURRENT/aarch64. This happens e.g. when the nigthly
backup is started.
# uname -a
FreeBSD rpi4 14.0-CURRENT FreeBSD 14.0-CURRENT #22 main-5f702d6d9a: Mon Feb 28
06:12:48 CET 2022
ron
Hi,
Repeated panics on 14-CURRENT/aarch64. This happens e.g. when the nigthly
backup is started.
# uname -a
FreeBSD rpi4 14.0-CURRENT FreeBSD 14.0-CURRENT #22 main-5f702d6d9a: Mon Feb 28
06:12:48 CET 2022
19 matches
Mail list logo
