Date: Fri, 05 Feb 1999 05:01:01 -0800 From: David Greenman <dg@root.com> To: John Hay <jhay@mikom.csir.co.za> Cc: julian@whistle.com (Julian Elischer), hackers@FreeBSD.ORG Subject: Re: Seen fxp or mbuf problems? Message-ID: <199902051301.FAA25497@implode.root.com> In-Reply-To: Your message of "Sat, 05 Feb 1999 08:47:15 %2B0200." <199902050647.IAA17011@zibbi.mikom.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902051301.FAA25497>