From owner-freebsd-current Thu Nov 25 14:20:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from shrewd.knigma.org (shrewd.demon.co.uk [212.229.151.45]) by hub.freebsd.org (Postfix) with ESMTP id EF57714DCB for ; Thu, 25 Nov 1999 14:20:27 -0800 (PST) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lap.knigma.org [10.128.148.202]) by shrewd.knigma.org (8.9.3/8.9.3) with SMTP id WAA00553 for ; Thu, 25 Nov 1999 22:20:37 GMT (envelope-from markk@knigma.org) Message-ID: <65tPkBAcYbP4EwVg@knigma.org> Date: Thu, 25 Nov 1999 22:20:12 +0000 To: freebsd-current@freebsd.org From: Mark Knight Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI References: <199911252210.XAA12659@peedub.muc.de> In-Reply-To: <199911252210.XAA12659@peedub.muc.de> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 4.02 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199911252210.XAA12659@peedub.muc.de>, Gary Jennejohn 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message