On Wed, Jan 06, 2016 at 01:24:53PM -0500, Shawn Webb wrote:
S> That's what gets toggled via the sysctl. I think I figured out that I
S> need to call ip_initid() in the SYSINIT. Compiling and testing now.
Right, that's the problem. You actually want VNET_SYSINIT().
Please next time you report a pa
Yup, calling ip_initid() in the SYSINIT works! Thanks for the help.
Thanks,
Shawn
On Wed, Jan 06, 2016 at 01:24:53PM -0500, Shawn Webb wrote:
> That's what gets toggled via the sysctl. I think I figured out that I
> need to call ip_initid() in the SYSINIT. Compiling and testing now.
>
> Thanks,
That's what gets toggled via the sysctl. I think I figured out that I
need to call ip_initid() in the SYSINIT. Compiling and testing now.
Thanks,
Shawn
On Wed, Jan 06, 2016 at 10:15:08AM -0800, Adrian Chadd wrote:
> Why'd you condition the vimage definition? :)
>
>
>
> -a
>
>
> On 6 January
Why'd you condition the vimage definition? :)
-a
On 6 January 2016 at 06:46, Shawn Webb wrote:
> (kgdb) list *(0x80b5de9e)
> 0x80b5de9e is in ip_fillid (/usr/src/sys/netinet/ip_id.c:237).
> warning: Source file is more recent than executable.
>
> 232 new_id = 0;
>
(kgdb) list *(0x80b5de9e)
0x80b5de9e is in ip_fillid (/usr/src/sys/netinet/ip_id.c:237).
warning: Source file is more recent than executable.
232 new_id = 0;
233 do {
234 if (new_id != 0)
235 V_random_id_collis
try list *(0x[address]) .
That line is mtx_unlock(), which makes no sense (as mtx_lock succeeded fine.)
-a
On 5 January 2016 at 18:13, Shawn Webb wrote:
> Thanks for the quick reply! Here's some more debugging output:
>
> === Begin Log ===
> (kgdb) bt
> #0 doadump (textdump=0) at pcpu.h:221
Thanks for the quick reply! Here's some more debugging output:
=== Begin Log ===
(kgdb) bt
#0 doadump (textdump=0) at pcpu.h:221
#1 0x8037c78b in db_dump (dummy=, dummy2=false,
dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:533
#2 0x8037c57e in db_command (cmd_table=0x0
looks like a null pointer deference. What's kgdb show at that IP?
-a
On 5 January 2016 at 17:57, Shawn Webb wrote:
> Hey All,
>
> Here's a kernel panic I'm experiencing by enabling net.inet.ip.random_id
> at boot.
>
> I'm on latest HEAD on amd64 in bhyve. I'll soon-ish be testing on native
> h
Hey All,
Here's a kernel panic I'm experiencing by enabling net.inet.ip.random_id
at boot.
I'm on latest HEAD on amd64 in bhyve. I'll soon-ish be testing on native
hardware with VIMAGE enabled.
=== Begin Log ===
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex
