From owner-freebsd-current Sun Feb 8 15:36:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23837 for current-outgoing; Sun, 8 Feb 1998 15:36:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp187.245.mmtl.videotron.net [207.96.245.187]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23821 for ; Sun, 8 Feb 1998 15:36:01 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id SAA15411 for ; Sun, 8 Feb 1998 18:35:21 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DE4137.A2621124@videotron.ca> Date: Sun, 08 Feb 1998 18:35:19 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <199802082248.PAA21945@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > 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. Well, on my dump I've got mbstat.m_clfree == 39 and mbstat.m_clusters = 36 > Does "someplace in hyperspace", when you look at the resion in memory, > look like an ethernet hardware address? "someplace in hyperspace (mclfree)" == 0x30337a15and the ether address of my ed0 card is 00:00:c0:5c:24:d0 > Are you running IP firewall? Yes, it's an open one right new (as per rc.firewall definition) as I hadn't time to configure it yet. > Do you have a reject rule? No > Are you getting TCP packets in that match the rule? No. See above. > 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. Well, you never seem to be out of questions :) do you? Hope it will help you a little. right now, I'm still trying to figure out how m_clfree could have gotten higher that m_clusters. I'm gonna try with a kernel without IPFIREWALL enabled to check if that changes something. -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message