Hi Network Guru's-
I've been running 11-Release branch since 11 was well.... released. I think I'm on 11-RELEASE-p2. I compiled my own kernel to enable vimage and use iocage for jails. I am not using pf or doing anything "exotic" with networking (this is behind a separate firewall).
So far it's been mostly stable. But I have had 3 crashes, the 1st and third panic, I am pretty sure, were network related (savecore didn't work for panic #2 for some reason).
Both panic #1 and #3 messages were "Fatal trap 12: page fault while in kernel mode".
For panic #1 my best guess is something caused my mbufs to go crazy, netstat -m in my core.txt.0 file showed:
18446744073709549889/5011/3284/2035246 mbuf clusters in use (current/cache/total/max)
( "current" definitely looks suspicious ) But I could not determine *what* caused the mbuf madness.... assuming it was contributing factor.
For panic #3 the stack trace "seemed" to indicate problems with the netisr_dispatch(9) system call. But I could not determine more b/c nothing else looked out of the ordinary.
The stack trace is the same for both dumps.
Could this be related to Bug ID: 194515 ? But I'm not running pf...
Should I take this to the freebsd-net email alias?
Regardless, I am very interested in helping improve the vnet/vimage "feature".
What can I do to help improve vnet/vimage? Anything?
Bob
I've been running 11-Release branch since 11 was well.... released. I think I'm on 11-RELEASE-p2. I compiled my own kernel to enable vimage and use iocage for jails. I am not using pf or doing anything "exotic" with networking (this is behind a separate firewall).
So far it's been mostly stable. But I have had 3 crashes, the 1st and third panic, I am pretty sure, were network related (savecore didn't work for panic #2 for some reason).
Both panic #1 and #3 messages were "Fatal trap 12: page fault while in kernel mode".
For panic #1 my best guess is something caused my mbufs to go crazy, netstat -m in my core.txt.0 file showed:
18446744073709549889/5011/3284/2035246 mbuf clusters in use (current/cache/total/max)
( "current" definitely looks suspicious ) But I could not determine *what* caused the mbuf madness.... assuming it was contributing factor.
For panic #3 the stack trace "seemed" to indicate problems with the netisr_dispatch(9) system call. But I could not determine more b/c nothing else looked out of the ordinary.
The stack trace is the same for both dumps.
Could this be related to Bug ID: 194515 ? But I'm not running pf...
Should I take this to the freebsd-net email alias?
Regardless, I am very interested in helping improve the vnet/vimage "feature".
What can I do to help improve vnet/vimage? Anything?
Bob