From owner-freebsd-bugs  Fri Jul 24 08:16:33 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA23872
          for freebsd-bugs-outgoing; Fri, 24 Jul 1998 08:16:33 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23802;
          Fri, 24 Jul 1998 08:16:15 -0700 (PDT)
          (envelope-from rivers@dignus.com)
Received: from dignus.com (ponds.vnet.net [166.82.177.48])
          by elvis.vnet.net (8.8.8/8.8.4) with ESMTP
	  id LAA13365; Fri, 24 Jul 1998 11:15:41 -0400 (EDT)
Received: from lakes.dignus.com (lakes [10.0.0.3])
	by dignus.com (8.8.8/8.8.5) with ESMTP id LAA07731;
	Fri, 24 Jul 1998 11:46:44 -0400 (EDT)
Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id LAA05554; Fri, 24 Jul 1998 11:17:47 -0400 (EDT)
Date: Fri, 24 Jul 1998 11:17:47 -0400 (EDT)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <199807241517.LAA05554@lakes.dignus.com>
To: freebsd-bugs@FreeBSD.ORG, phk@FreeBSD.ORG, rivers@dignus.com
Subject: Re: kern/7367
In-Reply-To: <199807240754.AAA12728@freefall.freebsd.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> 
> Synopsis: panic: malloc: wrong bucket
> 
> State-Changed-From-To: open-feedback
> State-Changed-By: phk
> State-Changed-When: Fri Jul 24 00:21:43 PDT 1998
> State-Changed-Why: 
> 
> Thomas, I hate to say this, but my initial reaction is "hardware!"
> It could be though, that you are on to a very elusive bug in the kernel,
> but in such case, I doubt anybody but you will be in a postiion to find
> it.  The diagnostic you propose sounds like a good first step, and all
> I can suggest you is to do the salami method from there.
> You may want to transplant another motherboard into the machine for a 
> week or so, just to rule out the hardware
> 

 Seems reasonable... although I am experiencing some mysterious
panics on a different machine.  It's likely stretching things to 
say they are the same issues... :-)

 I'd have to agree though; as I run FreeBSD on several other machines
without a single hiccup...

 But - My best guesses would also have to include something wrong
in XFree86 with the Matrox Millenium II driver... a wild pointer or
something...  What leads me this way is the fact that 2.2.5 didn't
get the problems; it all started the very day I installed 2.2.6 (which
also had the new XFree86.)

	- Dave Rivers -

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message