(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-02-03
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-01-28 to 2019-02-03.
During this period, we have:
* 2220 builds (93.7% passed, 6.2%
BTW under 12.0-STABLE (built this afternoon after the advisories came
out, with the patches) it's MUCH worse. I get the same device resets
BUT it's followed by an immediate panic which I cannot dump as it
generates a page-fault (supervisor read data, page not present) in the
mps *driver* at
06.02.2019 3:55, Ian Lepore wrote:
> So your problem was most likely the gps receiver making a bad choice
> before it had enough info to make a good choice. It's one of many
> reasons why an ntp server should have at least 3 (really, at least 5)
> peers, so it can reject obviously-insane data
On Wed, 2019-02-06 at 03:46 +0700, Eugene Grosbein wrote:
> 06.02.2019 3:18, Ian Lepore wrote:
>
> > > 2019, of course. re@ does NOT make mistakes. What you fail to
> > > realize is that NIST was using kqueue to check their atomic
> > > clock, and
> > > they lost the race. Enjoy the rest of
06.02.2019 3:18, Ian Lepore wrote:
>> 2019, of course. re@ does NOT make mistakes. What you fail to
>> realize is that NIST was using kqueue to check their atomic clock, and
>> they lost the race. Enjoy the rest of 2020.
>> -Alan
>>
>
> I think you meant that as a joke, but the reality is
On Tue, 2019-02-05 at 13:00 -0700, Alan Somers wrote:
> On Tue, Feb 5, 2019 at 12:55 PM Shawn Webb wrote:
> >
> > On Wed, Jan 09, 2019 at 07:40:30PM +, FreeBSD Errata Notices wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > >
> > >
On Tue, Feb 5, 2019 at 12:55 PM Shawn Webb wrote:
>
> On Wed, Jan 09, 2019 at 07:40:30PM +, FreeBSD Errata Notices wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > =
> > FreeBSD-EN-19:05.kqueue
On Wed, Jan 09, 2019 at 07:40:30PM +, FreeBSD Errata Notices wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> =
> FreeBSD-EN-19:05.kqueue Errata Notice
>
On 2/5/2019 09:22, Karl Denninger wrote:
> On 2/2/2019 12:02, Karl Denninger wrote:
>> I recently started having some really oddball things happening under
>> stress. This coincided with the machine being updated to 11.2-STABLE
>> (FreeBSD 11.2-STABLE #1 r342918:) from 11.1.
>>
>> Specifically,
On 2/2/2019 12:02, Karl Denninger wrote:
> I recently started having some really oddball things happening under
> stress. This coincided with the machine being updated to 11.2-STABLE
> (FreeBSD 11.2-STABLE #1 r342918:) from 11.1.
>
> Specifically, I get "errors" like this:
>
>
> Hi,
>
> What branch and revision do you use? Can you install gdb and then obtain
> this information:
The branch and revision is 12.0-STABLE r343538 GENERIC
> # kgdb
>
> (kgdb) list *ether_output+0x6b6
trying to do this on the actual box is hard, as it panics, but on another
machine running
On 17.01.2019 15:19, Pete French wrote:
> so, having got a workaround for yesterdays problems, I now went to upgrade my
> other pair of boxes using CARP. No 'pf' on these, just one shared address.
> This is the setup I have tested in development and it works fine.
>
> I install the new kenel and
Just to get the subject correct, as I tested this disabling CARP and I
still see the panic when going multi-user. It netwprking related as the
panic is in the ARP code, and seems to happen when the network
interfaces are configured. The machine was using a mix of em and igb
interfaces, but
13 matches
Mail list logo
