From owner-freebsd-hackers  Thu Dec 18 13:44:48 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA24913
          for hackers-outgoing; Thu, 18 Dec 1997 13:44:48 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA24906
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 18 Dec 1997 13:44:39 -0800 (PST)
          (envelope-from ken@panzer.plutotech.com)
Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125])
          by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA22567;
          Thu, 18 Dec 1997 14:44:34 -0700 (MST)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.8.8/8.8.5) id OAA27429;
          Thu, 18 Dec 1997 14:44:30 -0700 (MST)
Message-Id: <199712182144.OAA27429@panzer.plutotech.com>
Subject: Re: panic: blkfree: freeling free block/frag
In-Reply-To: <199712182011.NAA13788@usr05.primenet.com> from Terry Lambert at "Dec 18, 97 08:11:14 pm"
To: tlambert@primenet.com (Terry Lambert)
Date: Thu, 18 Dec 1997 14:44:30 -0700 (MST)
Cc: ivt@gamma.ru, tlambert@primenet.com, mike@smith.net.au,
        sclawson@bottles.cs.utah.edu, freebsd-hackers@FreeBSD.ORG
From: Kenneth Merry <ken@plutotech.com>
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert wrote...
> > Terry Lambert writes:
> > > I do not believe this is a single bit error.  I believe this is the same
> > > problem I have been seeing.
> > > 
> > > Does your ethernet hardware address begin with 00 00?
> > 
> > news.gamma.ru (158.250.39.26) at 0:0:c0:a4:2e:61
> > Is there a problem with 0:0 ?
> 
> Look at your corrupt variables and nearby variables in the stack, and
> see if your ethernet address is being blown onto the stack somewhere.
> 
> There is no problem with the 0:0, but it reinforces my feeling that
> this could be resulting from a trashed kernel stack.

	I doubt that his ethernet address indicates any problems.  00:00:c0
is an SMC ethernet address prefix.  I've got two SMC 10/100 cards in one of
my systems, and a SMC Elite Ultra 16 (or something to that effect) in
another system, and all of the ethernet addresses begin with 00:00:c0.

Ken
-- 
Kenneth Merry
ken@plutotech.com