Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Feb 2018 20:30:34 +0100 (CET)
From:      =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no>
To:        FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: amd64 head -r329465 (non-debug build, but with symbols): "panic: spin lock held too long" during make check-old, reported during a sys_vfork
Message-ID:  <alpine.BSF.2.21.1802182023090.24158@mail.fig.ol.no>
In-Reply-To: <CAGudoHH5Yz6312QSADiOVx9kd17=WcatEB3qyNjTa5qh_hXASg@mail.gmail.com>
References:  <DA76F62D-3373-47CA-AD95-DE9BA580772B@yahoo.com> <6907E068-C80A-44B8-A8AD-3EF27D52D127@yahoo.com> <20832C61-AA5D-41A6-8BF9-90CC87D17219@yahoo.com> <CAGudoHH5Yz6312QSADiOVx9kd17=WcatEB3qyNjTa5qh_hXASg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Feb 2018 19:08+0100, Mateusz Guzik wrote:

> Can you please bisect this? There is another report stating that r329418
> works fine.

My problems started yesterday with r329464. I decided to go back to 
r329101 (ZFS BE), update the source tree, move forward to the latest 
revision, and so on. I even emptied /usr/obj and /var/cache/ccache and 
set WITHOUT_SYSTEM_COMPILER=yes in /etc/src.conf to get rid of any 
bias.

I have tried with success r329418, r329419, r329420, and r329422.

I'm now at r329448 and have not seen any spin lock problems so far.

Sooner or later I'll reach r329464 and by then it should be clear 
which revision is the likely culprit.

-- 
Trond.



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