Re: kern/59719 Re: 4.9 Stable Crashes on SuperMicro with SMP

From: Jonathan Gilpin (jonathan_at_fluent.ltd.uk)
Date: 11/29/03

  • Next message: Marc G. Fournier: "Time jumping on both 4.x and 5.x ..." 
    To: "David Malone" <dwmalone@maths.tcd.ie>, <freebsd-gnats-submit@FreeBSD.org>
Date: Sat, 29 Nov 2003 01:22:21 -0000

    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.
    >

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Marc G. Fournier: "Time jumping on both 4.x and 5.x ..."

    Relevant Pages

    • [UNIX] Linux Kernel do_brk() Vulnerablility (Explained)
      ... Get your security news from a reliable source. ... A critical security bug has been found in the Linux kernel 2.4.22 (and ... earlier) memory management subsystem. ... for the code working at the lowest privilege level. ...
      (Securiteam)
    • Re: Cached memory never gets released
      ... Stock linux 2.4.26 kernel. ... Due to flash bug 3M of memory gets lost due to font memory getting lost ... The output of "free" cache number steadily grows. ... longer to exhaust all of system memory with the cache. ...
      (Linux-Kernel)
    • Re: fc5 hangs
      ... problem that was caused by a kernel bug relating to Athlon64 X2 ... take out or unplug each piece of hardware and retest ... work from my ssh session. ... Since no process seems to be hogging memory or swap. ...
      (Fedora)
    • Re: Flames over -- Re: Which is simpler?
      ... effect of doing a logical disconnect on the device. ... Does the kernel have any problem figuring out when a _different_ device ... But it does happen with USB disks, and it's not a bug; ... having the hardware verify that the device was connected the whole time. ...
      (Linux-Kernel)
    • Re: memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and c
      ... The kernel is most definitely not releasing the memory ... I further would have to say that the kernel isn't being ... >after cdrdao or cdrecord have used it, ... the Linux Kernel maintainers have not been very helpful with Linux ...
      (Linux-Kernel)