Date: Sat, 27 Nov 1999 00:03:18 +0000 From: Mark Knight <markk@knigma.org> To: freebsd-isdn@freebsd.org Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI Message-ID: <czLmGEAG$xP4EwQ3@knigma.org> In-Reply-To: <199911262012.VAA14737@peedub.muc.de> References: <EpOAQFARnbP4EwyS@knigma.org> <199911262012.VAA14737@peedub.muc.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199911262012.VAA14737@peedub.muc.de>, Gary Jennejohn <garyj@peedub.muc.de> writes >Hmm, it looks like the HSCX isn't being deactivated. Can you try this patch >and report back ? > >===================================================================== >*** i4b_avm_fritz_pci.c Fri Nov 26 20:51:05 1999 >--- i4b_avm_fritz_pci.c.orig Fri Nov 26 20:48:55 1999 The buffer overruns in my earlier logs appear to be a function of the logging being enabled and my ageing Pentium 90 struggling to keep up. Apart from the obvious typo preventing your patch from compiling (brackets required around the logging macro), this has definitely improved things! With a single incoming call, with the caller clearing down, netstat -m now shows mbuf usage returning to the original level, and staying there. If BSD clears down this is also fine, as before. In my delight I've now taken the destruction test a stage further: If I make two incoming calls, both of which are answered and receive the outgoing message, even if I allow i4b to clear each call after the outbound message, I get back to a state of run away mbuf allocation and impending panic. This time, it's much harder to restore stability, although this can be done with about 3 or 4 incoming calls in rapid succession. I've tried setting isdndebug to record this new scenario, but my machine just can't service the interrupts quickly enough. Thanks for your patch - a major leap forward in that a single wrong number won't crash my box :) -- Mark Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?czLmGEAG$xP4EwQ3>