Re: panic: invalid bcd xxx

2017-03-08 Thread Oleksandr Tymoshenko
Eric van Gyzen (vangy...@freebsd.org) wrote: > On 03/04/2017 11:44, Oleksandr Tymoshenko wrote: > > Adrian Chadd (adrian.ch...@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

Re: panic: invalid bcd xxx

2017-03-07 Thread Eric van Gyzen
On 03/04/2017 11:44, Oleksandr Tymoshenko wrote: Adrian Chadd (adrian.ch...@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

Re: panic: invalid bcd xxx

2017-03-04 Thread Oleksandr Tymoshenko
Adrian Chadd (adrian.ch...@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: > >>>

Re: panic: invalid bcd xxx

2017-03-03 Thread Adrian Chadd
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

Re: panic: invalid bcd xxx

2017-03-02 Thread Matthias Apitz
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

Re: panic: invalid bcd xxx

2017-03-01 Thread Michael Gmelin
> 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. -m > > -adrian > >>

Re: panic: invalid bcd xxx

2017-03-01 Thread Adrian Chadd
This is an emulated BIOS though, right? I don't know if we're going to get the RTC 'bugfixed'... -adrian On 28 February 2017 at 15:26, Michael Gmelin wrote: > On Tue, 28 Feb 2017 17:16:02 -0600 > Eric van Gyzen wrote: > >> On 02/28/2017 16:57, Conrad

Re: panic: invalid bcd xxx

2017-02-28 Thread Michael Gmelin
On Tue, 28 Feb 2017 17:16:02 -0600 Eric van Gyzen wrote: > On 02/28/2017 16:57, Conrad Meyer wrote: > > On Tue, Feb 28, 2017 at 2:31 PM, Eric van Gyzen > > wrote: > >> Your system's real-time clock is returning garbage. r312702 added > >> some

Re: panic: invalid bcd xxx

2017-02-28 Thread Eric van Gyzen
On 02/28/2017 16:57, Conrad Meyer wrote: On Tue, Feb 28, 2017 at 2:31 PM, Eric van Gyzen wrote: Your system's real-time clock is returning garbage. r312702 added some input validation a few weeks ago. Previously, the kernel was reading beyond the end of an array and

Re: panic: invalid bcd xxx

2017-02-28 Thread Conrad Meyer
On Tue, Feb 28, 2017 at 2:31 PM, Eric van Gyzen wrote: > Your system's real-time clock is returning garbage. r312702 added some > input validation a few weeks ago. Previously, the kernel was reading beyond > the end of an array and either complaining about the clock or

Re: panic: invalid bcd xxx

2017-02-28 Thread Eric van Gyzen
On 02/28/2017 15:47, Michael Gmelin wrote: Booting r313561[0] I get the following panic: mountroot: waiting for device /dev/ufs/FreeBSD_install panic: invalid bcd 177 (also 254, 255 etc.) cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper... vpanic()... kassert_panic()... atrtc_gettime()...

Re: panic: invalid bcd xxx

2017-02-28 Thread Konstantin Belousov
On Tue, Feb 28, 2017 at 10:47:39PM +0100, Michael Gmelin wrote: > Booting r313561[0] I get the following panic: > > mountroot: waiting for device /dev/ufs/FreeBSD_install > panic: invalid bcd 177 (also 254, 255 etc.) > cpuid = 1 > KDB: stack backtrace: > db_trace_self_wrapper... > vpanic()... >

panic: invalid bcd xxx

2017-02-28 Thread Michael Gmelin
Booting r313561[0] I get the following panic: mountroot: waiting for device /dev/ufs/FreeBSD_install panic: invalid bcd 177 (also 254, 255 etc.) cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper... vpanic()... kassert_panic()... atrtc_gettime()... inittodr()... vfs_mountroot()...