Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Jan 2018 17:41:41 +0100
From:      Matthias Apitz <guru@unixarea.de>
To:        Kurt Jaeger <pi@opsec.eu>
Cc:        <freebsd-current@freebsd.org>
Subject:   Re: panic: invalid bcd 194
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52f65ec7-af4e-4a80-950b-eada769d7430>