Works for me. With this diff I get armv7 regress results again.
http://bluhm.genua.de/regress/results/regress-ot7.html
OK bluhm@
On Tue, Jan 11, 2022 at 01:10:27PM +0100, Mark Kettenis wrote:
> > Date: Mon, 10 Jan 2022 15:40:34 +0100 (CET)
> > From: Mark Kettenis
> >
> > > Date: Mon, 10 Jan
Yes, increase it.
I am not surprised, there are many poor recoveries from resource shortage.
Mark Kettenis wrote:
> > Date: Mon, 10 Jan 2022 15:40:34 +0100 (CET)
> > From: Mark Kettenis
> >
> > > Date: Mon, 10 Jan 2022 14:40:50 +0100
> > > From: Alexander Bluhm
> > >
> > > On Thu, Jan 06,
> Date: Mon, 10 Jan 2022 15:40:34 +0100 (CET)
> From: Mark Kettenis
>
> > Date: Mon, 10 Jan 2022 14:40:50 +0100
> > From: Alexander Bluhm
> >
> > On Thu, Jan 06, 2022 at 03:59:55PM +0100, Alexander Bluhm wrote:
> > > My armv7 regress machine hangs every day in regress/sys/kern/fork-exit.
> >
> Date: Mon, 10 Jan 2022 14:40:50 +0100
> From: Alexander Bluhm
>
> On Thu, Jan 06, 2022 at 03:59:55PM +0100, Alexander Bluhm wrote:
> > My armv7 regress machine hangs every day in regress/sys/kern/fork-exit.
>
> Maybe a show uvm provides some information.
Not really. I can reproduce the
On Thu, Jan 06, 2022 at 03:59:55PM +0100, Alexander Bluhm wrote:
> My armv7 regress machine hangs every day in regress/sys/kern/fork-exit.
Maybe a show uvm provides some information.
Stopped at db_enter: ldrbr15, [r15, r15, ror r15]!
ddb> trace
db_enter
rlv=0xc06bd178
Hi,
My armv7 regress machine hangs every day in regress/sys/kern/fork-exit.
I can still break into ddb. Looks like an endless loop in
uvm_map_fix_space().
Note that it does not happen when I boot the machine and run only
the fork-exit test. This test hangs it when I run all regress tests
in a
