From owner-freebsd-current@freebsd.org  Tue Jan  2 16:41:46 2018
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 927C7EAE32A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  2 Jan 2018 16:41:46 +0000 (UTC)
 (envelope-from guru@unixarea.de)
Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5A92D683F1
 for <freebsd-current@freebsd.org>; Tue,  2 Jan 2018 16:41:45 +0000 (UTC)
 (envelope-from guru@unixarea.de)
Received: from [2.247.253.86] (helo=[10.250.117.86])
 by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.86_2) (envelope-from <guru@unixarea.de>)
 id 1eWPdG-0000PX-Kb; Tue, 02 Jan 2018 17:41:42 +0100
From: Matthias Apitz <guru@unixarea.de>
To: Kurt Jaeger <pi@opsec.eu>
Cc: <freebsd-current@freebsd.org>
Subject: Re: panic: invalid bcd 194
Date: Tue, 02 Jan 2018 17:41:41 +0100
User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; 
MIME-Version: 1.0
Message-ID: <52f65ec7-af4e-4a80-950b-eada769d7430@unixarea.de>
In-Reply-To: <20180102152631.GN2827@home.opsec.eu>
References: <20171230210711.GA75976@c720-r314251>
 <20171230211154.GT1684@kib.kiev.ua> <20171230214819.GA2191@c720-r314251>
 <20171231083624.GA2175@c720-r314251> <1514740790.12000.20.camel@freebsd.org>
 <20180101085425.GA2301@c720-r314251> <1514851362.1759.8.camel@freebsd.org>
 <20180102130020.GA2236@c720-r314251> <20180102143737.GA2286@c720-r314251>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Con-Id: 51246
X-Con-U: 0-guru
X-Originating-IP: 2.247.253.86
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
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, 02 Jan 2018 16:41:46 -0000

On Tuesday, 2 January 2018 16:26:31 CET, Kurt Jaeger <pi@opsec.eu> wrote:
> Hi!
>=20
>> I've added one more printf to see what is coming as year from=20
>> BCD. The code
>> is attached below and bcd.year comes out as 24 (decimal) which=20
>> is 0x18. I.e. it
>> seems that the year from 2018 is stored in hex as 0x18, or?
>=20
> It's actually BCD code:
>=20
> https://en.wikipedia.org/wiki/Binary-coded_decimal
>=20

So something must be wrong in the conversion into binary because the date=20
ends up as in year 1970.





--=20
Sent from my Ubuntu phone
http://www.unixarea.de/