Date: Wed, 1 Mar 2017 00:23:59 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Michael Gmelin <freebsd@grem.de> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, cem@freebsd.org Subject: Re: panic: invalid bcd xxx Message-ID: <20170228222359.GM2092@kib.kiev.ua> In-Reply-To: <20170228224739.167f2273@bsd64.grem.de> References: <20170228224739.167f2273@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 28, 2017 at 10:47:39PM +0100, Michael Gmelin wrote: > Booting r313561[0] I get the following panic: > > mountroot: waiting for device /dev/ufs/FreeBSD_install > panic: invalid bcd 177 (also 254, 255 etc.) > cpuid = 1 > KDB: stack backtrace: > db_trace_self_wrapper... > vpanic()... > kassert_panic()... > atrtc_gettime()... > inittodr()... > vfs_mountroot()... > start_init()... > fork_exit()... > fork_trampoline()... > (copied from a screenshot, hence the ellipsis) > > This is on an Acer C720 Chromebook, confirmed on two devices (one with > cyapa touchpad, one with elan touchpad). Same problem happened with a > CURRENT checked out about 10 hours ago. Previous versions of 12-CURRENT > worked ok (last version I tested personally was back in > November/December though). > > -m > > > [0] > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170210-r313561-memstick.img > This is most likely due to r312702. But then it means that your RTC returns garbage.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170228222359.GM2092>