From owner-freebsd-hackers Fri Feb 5 05:03:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13303 for freebsd-hackers-outgoing; Fri, 5 Feb 1999 05:03:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13298 for ; Fri, 5 Feb 1999 05:03:26 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id FAA25497; Fri, 5 Feb 1999 05:01:01 -0800 (PST) Message-Id: <199902051301.FAA25497@implode.root.com> To: John Hay cc: julian@whistle.com (Julian Elischer), hackers@FreeBSD.ORG Subject: Re: Seen fxp or mbuf problems? In-reply-to: Your message of "Sat, 05 Feb 1999 08:47:15 +0200." <199902050647.IAA17011@zibbi.mikom.csir.co.za> From: David Greenman Reply-To: dg@root.com Date: Fri, 05 Feb 1999 05:01:01 -0800 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. :-) All mbuf allocations done through the MGET macros have inherent splimp protection. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message