From owner-freebsd-bugs  Fri Jul 24 00:55:33 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA10136
          for freebsd-bugs-outgoing; Fri, 24 Jul 1998 00:55:33 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10040;
          Fri, 24 Jul 1998 00:55:00 -0700 (PDT)
          (envelope-from phk@FreeBSD.org)
From: Poul-Henning Kamp <phk@FreeBSD.ORG>
Received: (from phk@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id AAA12728;
	Fri, 24 Jul 1998 00:54:26 -0700 (PDT)
Date: Fri, 24 Jul 1998 00:54:26 -0700 (PDT)
Message-Id: <199807240754.AAA12728@freefall.freebsd.org>
To: rivers@dignus.com, phk@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/7367
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

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