Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 May 2017 17:29:53 +0100
From:      tech-lists <tech-lists@zyxst.net>
To:        freebsd-arm@freebsd.org
Subject:   Re: lock when building llvm37 on RPI3
Message-ID:  <c0f8bf1f-a163-26c8-f664-0704a1fe6943@zyxst.net>
In-Reply-To: <9d7569cd-e2fd-0e6b-225f-bf800eae3e25@bsd.com.br>
References:  <0b4b8a6f-f008-4892-a7c1-73fab2a79030@bsd.com.br> <4085737d-af52-3f21-c593-3be249b59d46@zyxst.net> <9d7569cd-e2fd-0e6b-225f-bf800eae3e25@bsd.com.br>

next in thread | previous in thread | raw e-mail | index | archive | help
On 02/05/2017 11:48, OtacĂ­lio wrote:
> Hello
> 
> 1. No, I not installed ccache previously. Thank you by your hint.
> 
> 2. Yes. I'm using a external USB hard disk (Seagate, 500 GB auto
> powered).  /usr/obj /usr/ports and /usr/src is mounted there.
> 
> 3. No. I will do it also.
> 
> Unhappily I was using a NODEBUG kernel and no hint about the deadlock
> was printed. Maybe the deadlock can be caused by the micro SD HC card
> used but I can not affirm.
> 
> I give another try and this time I got a kernel panic at
> reclaim_pv_chunk http://imgur.com/XLiziq1

I'm unable to parse stack traces, but I know that with microsd cards,
that they can go wrong in odd ways. If the kernel tries to read
something essential to itself and can't, that can cause a panic. So the
next thing i'd try is another, new, microsd card.

-- 
J.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c0f8bf1f-a163-26c8-f664-0704a1fe6943>