From owner-freebsd-current Sun Feb 8 08:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09983 for current-outgoing; Sun, 8 Feb 1998 08:56:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp189.117.mmtl.videotron.net [207.253.117.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09973 for ; Sun, 8 Feb 1998 08:56:26 -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 LAA20734 for ; Sun, 8 Feb 1998 11:56:51 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DDE3D1.238B21EB@videotron.ca> Date: Sun, 08 Feb 1998 11:56:50 -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: <199802080747.AAA29050@usr02.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)? -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message