From owner-freebsd-hackers Thu Feb 4 22:47:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04469 for freebsd-hackers-outgoing; Thu, 4 Feb 1999 22:47:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04458 for ; Thu, 4 Feb 1999 22:47:47 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id IAA17011; Fri, 5 Feb 1999 08:47:15 +0200 (SAT) From: John Hay Message-Id: <199902050647.IAA17011@zibbi.mikom.csir.co.za> Subject: Re: Seen fxp or mbuf problems? In-Reply-To: <36BA4603.1CFBAE39@whistle.com> from Julian Elischer at "Feb 4, 99 05:14:43 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 5 Feb 1999 08:47:15 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone seen bugs in fxp driver or mbuf related code recently? > > Here is a crash dump from a system about 10 days old (3.x series) > > We are willing to believe that we've done this (we do enough > networking stuff but I'm just looking to see if there > is anyone else that has seen this. > I have seen something like this here while we were developing a piece of network code of our own. It was because there was a mbuf alloc that wasn't protected with at least splimp(). Remember that all the network driver interrupt routines will allocate mbufs and they run at splimp(), so all other places have to run at splimp() also. Anyway just a guess, it might not be your problem, but it was definitely ours. :-) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message