Kernel panics in tcp_twclose

[Palle Girgensohn]

> 23 sep 2015 kl. 23:25 skrev Navdeep Parhar <nparhar at gmail.com>:
> 
> On Wed, Sep 23, 2015 at 11:15:03PM +0200, Palle Girgensohn wrote:
> ...
>>> By the way Palle could you also run below Dtrace script to see where
>>> this tcp_close() in INP_TIMEWAIT comes from:
>>> 
>>> $ cat tcp-close-tw.d
>>> fbt::tcp_close:entry
>>> /args[0]->t_inpcb->inp_flags & 0x01000000/
>>> {
>>> @s1[stack()] = count()
>>> }
>>> 
>>> tick-1sec {
>>> printa(@s1);
>>> }
>>> $ sudo dtrace -s tcp-close-tw.d
>> 
>> # dtrace -s tcp-close-tw.d
>> dtrace: failed to compile script tcp-close-tw.d: line 2: t_inpcb is not a member of struct e1000_hw
>> 
>>> 
>> 
>> on one system...
>> 
>> and for the other two:
>> 
>> # dtrace -s tcp-close-tw.d
>> dtrace: failed to initialize dtrace: DTrace device not available on system
>> 
>> I'm adding
>> 
>> options         KDTRACE_HOOKS
>> 
>> to the kernels, I guess that will help?
> 
> Load the DTrace modules ("kldload dtraceall") before trying to run the
> DTrace script.
> 
> Regards,
> Navdeep


Ah, cool, thanks. I've downgraded the kernels in thw machines from stable to 10.2, hence som extra whining. 

So I don't need 

options         DDB_CTF
makeoptions	DEBUG=-g
makeoptions	WITH_CTF=1

like [https://www.freebsd.org/doc/handbook/dtrace-enable.html] claims?

Palle