From owner-freebsd-current Sun Feb 8 14:48:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17004 for current-outgoing; Sun, 8 Feb 1998 14:48:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16998 for ; Sun, 8 Feb 1998 14:48:15 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA20263; Sun, 8 Feb 1998 15:48:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd020247; Sun Feb 8 15:48:13 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA21945; Sun, 8 Feb 1998 15:48:12 -0700 (MST) From: Terry Lambert Message-Id: <199802082248.PAA21945@usr05.primenet.com> Subject: Re: Current dying horribly when using lp0 To: sepotvin@videotron.ca Date: Sun, 8 Feb 1998 22:48:11 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <34DDE3D1.238B21EB@videotron.ca> from "Stephane E. Potvin" at Feb 8, 98 11:56:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do this again with a radix of 16. When you find the damaged pointer > > in memory, then examine the region of memory before it and after it > > (again in hex). > > Found out that mclfree is causing the trap12. It's pointing somewhere in > hyperspace when it makes my kernel crash. While I was digging around, I > noticed something I find weird. Is it possible to have more free clusters > than obtained clusers (mbstat.m_clfree > mbstat.m_clusters)? No. Does "someplace in hyperspace", when you look at the resion in memory, look like an ethernet hardware address? Are you running IP firewall? Do you have a reject rule? Are you getting TCP packets in that match the rule? There is (was?) a bug in the IP firewall code that resulted in an input ehter address structure being written to, effectively, random locations on the kernel stack. This is because the stack was used for a structure, and the calling code returned before the scheduled code completed. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message