In article <[EMAIL PROTECTED]>, Gary Jennejohn
<[EMAIL PROTECTED]> writes
>Are you using the code in -current or one of the releases ? Makes a
>difference.
cvsup'd current from Saturday morning.
>Can you a) increase the size of the message buffer in your config file
>(options MSGBUF_SIZE=81920, for example) b) turn on ALL the
>trace in the kernel with isdndebug c) cause the panic to happen again
>and get a crash dump ?
I'll give this a go.
>It would also be good if you could run isdntrace in parallel so that
>there's some correlation between the kernel messages and the trace times.
I did include that in my earlier post - in case you missed it...
>I can only guess, but it looks like the user-land process isn't told
>about the hangup and keeps sending packets down the line. The packets
>never go out (no connection), so the mbufs eventually run out. The
>raw interface evidently doesn't have the safety belts that the other
>interfaces (like ipr, isppp) have.
I've tried killing the user land daemon and the growth continues.
Latest finding. Once the run-away has started, another incoming call
allowed to complete with FreeBSD performing the clear down results in
all mbufs being freed and stability returning.
--
Mark Knight
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
