From owner-freebsd-current@freebsd.org  Tue Mar  7 17:26:41 2017
Return-Path: <owner-freebsd-current@freebsd.org>
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 2474CD016EE
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  7 Mar 2017 17:26:41 +0000 (UTC)
 (envelope-from vangyzen@FreeBSD.org)
Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146])
 by mx1.freebsd.org (Postfix) with ESMTP id 0B638114D
 for <freebsd-current@freebsd.org>; Tue,  7 Mar 2017 17:26:40 +0000 (UTC)
 (envelope-from vangyzen@FreeBSD.org)
Received: from sweettea.beer.town (unknown [76.164.8.130])
 by smtp.vangyzen.net (Postfix) with ESMTPSA id D539E5646A;
 Tue,  7 Mar 2017 11:26:33 -0600 (CST)
Subject: Re: panic: invalid bcd xxx
To: Oleksandr Tymoshenko <gonzo@bluezbox.com>,
 Adrian Chadd <adrian.chadd@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+0+=-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>
 <20170304174434.GA26923@bluezbox.com>
Cc: Matthias Apitz <guru@unixarea.de>,
 freebsd-current <freebsd-current@freebsd.org>
From: Eric van Gyzen <vangyzen@FreeBSD.org>
Message-ID: <f81dec70-289c-4ef3-69bc-eaa2cdd69ff7@FreeBSD.org>
Date: Tue, 7 Mar 2017 11:26:32 -0600
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <20170304174434.GA26923@bluezbox.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 17:26:41 -0000

On 03/04/2017 11:44, Oleksandr Tymoshenko wrote:
> Adrian Chadd (adrian.chadd@gmail.com) wrote:
>> 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.

cem@ posted this patch:

	http://dpaste.com/1K2W05E

If someone can test it, I'll gladly commit it.  The real-time clock will 
likely be wrong, but it won't panic with INVARIANTS.

Eric