From owner-freebsd-current@freebsd.org Sat Mar 4 17:44:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09372CF9818 for ; Sat, 4 Mar 2017 17:44:38 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D73181386 for ; Sat, 4 Mar 2017 17:44:37 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1ckDjQ-00070m-0b; Sat, 04 Mar 2017 09:44:36 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v24HiZG1026955; Sat, 4 Mar 2017 09:44:35 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Sat, 4 Mar 2017 09:44:34 -0800 From: Oleksandr Tymoshenko To: Adrian Chadd Cc: Matthias Apitz , freebsd-current Subject: Re: panic: invalid bcd xxx Message-ID: <20170304174434.GA26923@bluezbox.com> References: <20170228224739.167f2273@bsd64.grem.de> <226a00fa-5d04-0aa7-e0cc-6078edde6639@FreeBSD.org> <20170301002620.6a5e35ce@bsd64.grem.de> <80EC6EBB-8BF6-4990-9DEE-906EDCE69E06@grem.de> <673e2e0c-b3c8-42b7-a32d-1798eaf571f6@unixarea.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Adrian Chadd (adrian.chadd@gmail.com) wrote: > On 2 March 2017 at 01:31, Matthias Apitz wrote: > > On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin > > wrote: > >> > >> > >> > >>> On 2 Mar 2017, at 00:35, Adrian Chadd 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? [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: grem.de] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2017 17:44:38 -0000 Adrian Chadd (adrian.chadd@gmail.com) wrote: > On 2 March 2017 at 01:31, Matthias Apitz wrote: > > On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin > > wrote: > >> > >> > >> > >>> On 2 Mar 2017, at 00:35, Adrian Chadd 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