freebsd stable - Nov 2003 - kern/59719 Re: 4.9 Stable Crashes on SuperMicro with SMP

Having disabled the SMP in the kernel. The box is running with
Hypterthreading Turned on thus using 2 virtual CPU's.

Would this indicatate that the problem is with the second CPU? Or does this
prove nothing...

Jonathan



----- Original Message ----- 
From: "Jonathan Gilpin" <jonathan@fluent.ltd.uk>
To: "David Malone" <dwmalone@maths.tcd.ie>;
<freebsd-gnats-submit@FreeBSD.org>
Cc: <freebsd-bugs@freebsd.org>; <freebsd-stable@freebsd.org>;
"Don Bowman"
<don@sandvine.com>
Sent: Saturday, November 29, 2003 1:22 AM
Subject: Re: kern/59719 Re: 4.9 Stable Crashes on SuperMicro with SMP

> I've run memtest (memtest86.com) kindly provided by Don and it passed
all
> the tests. I've installed installed a kernel module to test for memory
> errors and found that again no memory errors are found... So this means
it's
> either a problem with the CPU's or a geniune bug in the kernel.
(bugger!)
>
> I'm going to switch the CPU's around (we dont have any spare) and
then try
> and get spares from my supplier to test with. Today I aslo enabled
> Hypterthreading in the BIOS and Disabled MPS 1.4. This had no effect and
the
> box continued to crash...
>
> The strange thing is that this box ran fine using Suse...
>
> The box BTW is a SuperMicro 6013-I (some of you have asked).
>
> Is it worth enabling any debug stuff in the kernel? I'm not familair
with
> gdb but can follow instructions to provide more info to anyone
investigating
> possible bugs such as these...
>
> Unless the switching of the CPU's around works I'm going to have to
go
back
> to 1 CPU for stability...
>
> Jonathan
>
>
>
> ----- Original Message ----- 
> From: "David Malone" <dwmalone@maths.tcd.ie>
> To: "Jonathan Gilpin" <jonathan@fluent.ltd.uk>
> Cc: <freebsd-bugs@freebsd.org>; <freebsd-stable@freebsd.org>
> Sent: Thursday, November 27, 2003 2:09 PM
> Subject: Re: 4.9 Stable Crashes on SuperMicro with SMP
>
>
> > On Wed, Nov 26, 2003 at 10:35:49PM -0000, Jonathan Gilpin wrote:
> > > Further Crashes as reported before:
> >
> > Both of these crashes could potentially be caused by hardware or
> > memory problems. While it is possible it's a bug of some sort,
I'd
> > start by checking out my hardware, if I were you...
> >
> > David.
> >
>