Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works]

2017-02-28 Thread Mateusz Guzik
On Sat, Feb 25, 2017 at 08:31:04PM +0100, Mateusz Guzik wrote: > On Sat, Feb 25, 2017 at 09:58:39AM -0800, Mark Millard wrote: > > Thus the PowerMac G5 so-called "Quad Core" is back to > > -r313254 without your patches. (The "Quad Core" really has > > two processors, each with 2 cores.) > > > >

Re: HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

2017-02-28 Thread Mark Linimon
On Tue, Feb 28, 2017 at 11:24:27PM +0100, Ed Schouten wrote: > 2017-02-28 21:00 GMT+01:00 Konstantin Belousov : > > Ideally, ports should stop shipping mangled system includes, or even better, > > gcc stop doing fixincludes. > > Amen. Please let me know the magic wand you

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: HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

2017-02-28 Thread Ed Schouten
2017-02-28 21:00 GMT+01:00 Konstantin Belousov : > Ideally, ports should stop shipping mangled system includes, or even better, > gcc stop doing fixincludes. Amen. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717

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()...

Re: HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

2017-02-28 Thread Konstantin Belousov
On Tue, Feb 28, 2017 at 11:42:48AM -0800, Steve Kargl wrote: > r313194 defined vm_ooffset_t and vm_pindex_t in sys/types.h. > I believe that forces a recompile of lang/gcc ports, and > probably anything built with the lang/gcc port to avoid > dependency issue. Neither "pkg audit -q" nor "pkg

HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

2017-02-28 Thread Steve Kargl
r313194 defined vm_ooffset_t and vm_pindex_t in sys/types.h. I believe that forces a recompile of lang/gcc ports, and probably anything built with the lang/gcc port to avoid dependency issue. Neither "pkg audit -q" nor "pkg version -vl '<'" pick up this issue. % make gcc6 -o hex -O2 -pipe