From owner-freebsd-isdn Fri Nov 26 10:22: 7 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 9DAD0150B4 for ; Fri, 26 Nov 1999 10:22:02 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id TAA14541; Fri, 26 Nov 1999 19:21:18 +0100 (CET) Message-Id: <199911261821.TAA14541@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mark Knight Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Panic caused by mbuf exhaustion in i4b with AVM PCI Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 25 Nov 1999 22:20:12 GMT." <65tPkBAcYbP4EwVg@knigma.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Nov 1999 19:21:18 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [changed -current to -isdn, it's more appropriate] Mark Knight writes: >In article <199911252210.XAA12659@peedub.muc.de>, Gary Jennejohn > writes >>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... > yes, but there's no correlation between the gdb output and what was going on in the kernel relative to the isdntrace output. All academic now that you've posted the kernel trace. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message