Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Jan 2018 16:26:31 +0100
From:      Kurt Jaeger <pi@opsec.eu>
To:        Matthias Apitz <guru@unixarea.de>, freebsd-current@freebsd.org
Subject:   Re: panic: invalid bcd 194
Message-ID:  <20180102152631.GN2827@home.opsec.eu>
In-Reply-To: <20180102143737.GA2286@c720-r314251>
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
Hi!

> I've added one more printf to see what is coming as year from BCD. The code
> is attached below and bcd.year comes out as 24 (decimal) which is 0x18. I.e. it
> seems that the year from 2018 is stored in hex as 0x18, or?

It's actually BCD code:

https://en.wikipedia.org/wiki/Binary-coded_decimal

-- 
pi@opsec.eu            +49 171 3101372                         2 years to go !



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180102152631.GN2827>