On Sun, 16 Aug 2020 19:35:47 +0300
Andreas Gustafsson wrote:
> Tobias Nygren wrote:
> > Seems there is still something wrong with -current.
> > ./build.sh -j8 hangs in <10 seconds on a t3.2xlarge EC2 instance.
> > Reverting to a -D20200812 kernel makes it stable.
>
> FWIW, I successfully
Tobias Nygren wrote:
> Seems there is still something wrong with -current.
> ./build.sh -j8 hangs in <10 seconds on a t3.2xlarge EC2 instance.
> Reverting to a -D20200812 kernel makes it stable.
FWIW, I successfully completed a "build.sh -j 24 release" of 9.0
hosted on a -current built from
On Sun, 16 Aug 2020 13:58:46 +0200
Tobias Nygren wrote:
> Seems there is still something wrong with -current.
> ./build.sh -j8 hangs in <10 seconds on a t3.2xlarge EC2 instance.
> Reverting to a -D20200812 kernel makes it stable.
This is a known clean filesystem that was just fsck'ed:
panic:
On Sun, 16 Aug 2020 12:36:21 +0300
Andreas Gustafsson wrote:
> Chuck Silvers wrote:
> > this should be fixed now.
> > sorry about that, the problem did not happen for me and
> > it took me forever to find a way that I could reproduce it.
>
> This is not to pick on you specifically as almost
Chuck Silvers wrote:
> this should be fixed now.
> sorry about that, the problem did not happen for me and
> it took me forever to find a way that I could reproduce it.
This is not to pick on you specifically as almost everyone is doing
the same thing, but IMO, in cases like this it would
this should be fixed now.
sorry about that, the problem did not happen for me and
it took me forever to find a way that I could reproduce it.
-Chuck
On Sat, Aug 15, 2020 at 09:01:53PM +0300, Andreas Gustafsson wrote:
> Hi chs,
>
> At least i386, amd64, and sparc are all panicing on boot since
Hi chs,
At least i386, amd64, and sparc are all panicing on boot since this commit:
2020.08.14.09.06.14 chs src/sys/miscfs/genfs/genfs_io.c 1.100
2020.08.14.09.06.15 chs src/sys/uvm/uvm_extern.h 1.231
2020.08.14.09.06.15 chs src/sys/uvm/uvm_object.c 1.24
2020.08.14.09.06.15 chs
