On 09/13/2017 11:21, Sean Bruno wrote:
>> Previous successful build was:
>> FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #398
>> r323483M/323489:1200044: Tue Sep 12 04:31:08 PDT 2017
>> r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64
>>
>> The usual his
On Wed, Sep 13, 2017 at 09:21:57AM -0600, Sean Bruno wrote:
> ...
> When you get a chance, let me know what em(4) device is in your machine
> (pciconf -lvbc). I'll see if I have one around here to test.
stable/11 says:
em0@pci0:0:25:0:class=0x02 card=0x05cc1028 chip=0x153a8086 rev=0x
On Tue, Sep 12, 2017 at 10:34:00AM +0200, Raphael Kubo da Costa wrote:
> Mark Johnston writes:
>
> > I think the bug is that keg_large_init() doesn't take
> > sizeof(struct uma_slab) into account when setting uk_ppera for the keg.
> > In particular, the bug isn't specific to the bootup process; i
> Previous successful build was:
> FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #398
> r323483M/323489:1200044: Tue Sep 12 04:31:08 PDT 2017
> r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64
>
> The usual historical information, including a verbose-boo
Well, we know it's due to r323516, but unfortunately can't have you
bisect from there because it was committed as a giant lump. If it
can't be fixed quickly, maybe it should be reverted?
Best,
Conrad
On Wed, Sep 13, 2017 at 6:10 AM, David Wolfskill wrote:
> My build machine didn't have the prob
My build machine didn't have the problem -- unfortunately (as I have a
serial console on it). The laptop did The panic occurs immediately
after probing the NICs (so the good news is that it didn't have a chance
yet to mount any filesystems; the bad news is that there's no dump
available). (I
