Date: Wed, 30 Sep 2020 12:33:22 -0400 From: Ed Maste <emaste@freebsd.org> To: Michal Meloun <mmel@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r366161 - head/sys/dev/extres/syscon Message-ID: <CAPyFy2C=psgFeHySYrdLov45vgNKjoBNqsG=rsthSwR9MA4MaQ@mail.gmail.com> In-Reply-To: <202009251644.08PGi2Qg041379@repo.freebsd.org> References: <202009251644.08PGi2Qg041379@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Sep 2020 at 12:44, Michal Meloun <mmel@freebsd.org> wrote: > > Author: mmel > Date: Fri Sep 25 16:44:01 2020 > New Revision: 366161 > URL: https://svnweb.freebsd.org/changeset/base/366161 The pine64 in CI is currently broken, panicking at boot with: panic: mutex aw_syscon0 owned at /usr/src/sys/dev/extres/syscon/syscon_generic.c:98 Log: https://ci.freebsd.org/hwlab/job/FreeBSD-device-head-pinea64-test/6480/artifact/device_tests/pinea64.boot.log It's possible there's an outdated dtb involved here, as there was with the BBB. Hopefully manu's change to report/check the dtb version makes it in and can be used to help track these issues down. Unfortunately the USB-serial interface connected to the pine64 was broken until yesterday so I'm not sure for how long this has been broken in this way. The last successful run was at r364130 almost 2 months ago; the first failure after that was because of an apparent hang at shutdown.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2C=psgFeHySYrdLov45vgNKjoBNqsG=rsthSwR9MA4MaQ>