Re: Panic _at_r251745; i386, early in boot sequence

On 06/15/13 02:35, David Wolfskill wrote:
> Here's a hand-transcribed copy of the backtrace:
> 
> ... Timecounters tick every 1.000 msec panic: curvnet is NULL cpuid
> = 0 KDB: stack backtrace: 
> db_trace_self_wrapper(c1034c40,c102a482,c11b646c,c2020cbc,c1037f21,...)
> at 0xc051283d = db_trace_self_wrapper+0x2d/frame 0xc2020be8 
> kdb_backtrace(c10863e7,0,c102a482,c2020cbc,c102a482,...) at
> 0xc0aa9800 = kdb_backtrace+0x30/frame 0xc2020c50 
> vpanic(c11963a2,100,c102a482,c2020cbc,c2020cbc,...) at 0xc0a71e0f =
> vpanic+0x11f/frame 0xc2020c50 
> kassert_panic(c102a482,0,c102a450,10b,c1143100,...) at 0xc0a71cea =
> kassert_panic+0xea/frame 0xc2020cb0 
> hhook_head_register(1,0,c1358904,102,c116030c,...) at 0xc0a40132 =
> hhook_head_register+0x102/frame 0xc2020cd4 
> tcp_init(0,c103cac6,ce03d448,c112654c,c2020d58,...) at 0xc0c1fecc =
> tcp_init+0x2c/frame 0xc0c0d20 
> domain_init(c114305c,0,ce03d530,201e000,2025000,...) at 0xc0adf357
> = domain_init+0x27/frame 0xc2020d38 mi_startup() at 0xc0a1deb7 =
> mi_startup+0xf7/frame 0xc2020d58 begin() at 0xc0a1c07 = begin+0x2c 
> KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at	0xc0aa95fd
> = kdb_enter+0x3d:	movl	$0,0xc11b21c4 = kdb_why db>
> 
> Previous working head was _at_r251684 (from yesterday).  My build
> machine (where I have a serial console) is still building; above is
> from laptop (which lacks serial console, unfortunately).
> 
> I update build machine & laptop to same GRNs; here is build
> machine's "uname-a" output (showing yesterday's update, as today's
> is still in progress):
> 
> FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT
> #1191  r251684M/251684:1000035: Thu Jun 13 09:46:05 PDT 2013
> root_at_freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC
> i386
> 
> Any suggestions for what to hack?  :-}

My apologies for the brain fart. Committing a fix shortly.

Cheers,
Lawrence