Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Apr 2018 08:27:23 -0700
From:      bob prohaska <fbsd@www.zefox.net>
To:        tech-lists <tech-lists@zyxst.net>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: More problems self-hosting -current on RPi3
Message-ID:  <20180404152722.GA74214@www.zefox.net>
In-Reply-To: <b0a011c9-f8a2-33d9-3b54-b50e872130ec@zyxst.net>
References:  <20180330235039.GA53786@www.zefox.net> <b0a011c9-f8a2-33d9-3b54-b50e872130ec@zyxst.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 04, 2018 at 01:50:13PM +0100, tech-lists wrote:
> Hi,
> 
> On 31/03/2018 00:50, bob prohaska wrote:
> > Here's a strange buildworld failure with -current on an RPI3. 
> >  
> > 
> > Details are at http://www.zefox.net/~fbsd/rpi3/crashes/20180330/
> > 
> 
> Do you think the following might be related to the swap problems you've
> been having:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356
> 
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088467.html
> 

I don't understand either report well enough to be certain, but I think
the answer is "no". Both are relatively old compared to -current as of
a few days ago. If what I'm seeing turned up in 11-stable I suspect there'd
be a much greater reaction in the FreeBSD community. The second refers to
a warning that has been present on armv7 for over a year and seems harmless.

The troubles I'm seeing were not evident when I first started playing with
a Pi3 in January and became manifest only in the last month or so. 

Thanks for writing!

bob prohaska
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180404152722.GA74214>