Just a "me too", with a different panic after this commit:
Assertion (key.to) > 0 && (key.to) <= w_max_used_index && (key.to) <
witness_count failed at sys/kern/subr_witness.c:2961
db_trace_self_wrapper()
vpanic()
kassert_panic()
witness_checkorder()
__mtx_lock_flags()
vmem_xalloc()
vmem_alloc
On Thursday, September 14, 2017 03:19:29 PM Stephen Hurd wrote:
> John Baldwin wrote:
> > igb0: port 0xe020-0xe03f mem
> > 0xfb22-0xfb23,0xfb244000-0xfb247fff irq 43 at device 0.0 on pci6
> > igb0: attach_pre capping queues at 8
> > igb0: using 1024 tx descriptors and 1024 rx descriptors
John Baldwin wrote:
igb0: port 0xe020-0xe03f mem
0xfb22-0xfb23,0xfb244000-0xfb247fff irq 43 at device 0.0 on pci6
igb0: attach_pre capping queues at 8
igb0: using 1024 tx descriptors and 1024 rx descriptors
igb0: msix_init qsets capped at 8
igb0: pxm cpus: 4 queue msgs: 9 admincnt: 1
ig
On Wednesday, September 13, 2017 07:08:26 PM Jung-uk Kim wrote:
> 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.c
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
> 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
