Date: Sat, 4 Mar 2017 09:44:34 -0800 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: Matthias Apitz <guru@unixarea.de>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: panic: invalid bcd xxx Message-ID: <20170304174434.GA26923@bluezbox.com> In-Reply-To: <CAJ-VmokdNkL6Yn_65in16=E30VZTnmVDMO9Y9BoiEt7M3PvuuA@mail.gmail.com> References: <20170228224739.167f2273@bsd64.grem.de> <226a00fa-5d04-0aa7-e0cc-6078edde6639@FreeBSD.org> <CAG6CVpXGQds1NYOOd1trYBTE8KNm=VYA3mq9yK3gjjVMt3NNpA@mail.gmail.com> <b753effa-aa7f-ff20-d127-28e1e827f304@FreeBSD.org> <20170301002620.6a5e35ce@bsd64.grem.de> <CAJ-Vmo=-0g7bcU3uq_U0Lc%2B0%2B=-SUiHH02OChjXt=RK6kezDmw@mail.gmail.com> <80EC6EBB-8BF6-4990-9DEE-906EDCE69E06@grem.de> <673e2e0c-b3c8-42b7-a32d-1798eaf571f6@unixarea.de> <CAJ-VmokdNkL6Yn_65in16=E30VZTnmVDMO9Y9BoiEt7M3PvuuA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adrian Chadd (adrian.chadd@gmail.com) wrote: > On 2 March 2017 at 01:31, Matthias Apitz <guru@unixarea.de> wrote: > > On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin <freebsd@grem.de> > > wrote: > >> > >> > >> > >>> On 2 Mar 2017, at 00:35, Adrian Chadd <adrian.chadd@gmail.com> wrote: > >>> > >>> This is an emulated BIOS though, right? > >>> > >>> I don't know if we're going to get the RTC 'bugfixed'... > >>> > >> > >> > >> It's SeaBIOS, yes. I feel like this might end up in another > >> quirk/workaround solution. > >> > > > > I'm one of the C720 owners and apart of Michael, I only know two users more > > running FreeBSD. The SeaBIOS in our devices. is outdated, mine from 2013 > > IIRC. I dont know if there is an easy way to update this. > > We're not; we need to cope with crappy BIOS emulations and not crash :) > > What's Linux doing instead? Ignoring the RTC? I believe I saw the same problem on either my NUC or Minnowboard. I just hacked around it to work on something else and didn't have time to get back to the device since then. But it's not just emulation BIOS. I think the right way to go is to perform sanity check on RTC data and refuse to use it if it's not valid. -- gonzo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170304174434.GA26923>