Re: 5.3-BETA7 install cd: kernel trap 12 with interrupts disabled (fwd)

From: Robert Gray (bob_at_boulderlabs.com)
Date: 10/15/04

  • Next message: Max Laier: "Re: network slowness/freez-up since update 10/11" 
    To: freebsd-current@freebsd.org
Date: Fri, 15 Oct 2004 11:41:22 -0600

    Yes, a built-in memory tester would be helpful. However, my experience
    is that many memory problems pass the x86memtest, but cause
    "seg faults" during buildworld, partly due to the extra load and heat
    from disk activity.

    I'm a firm believer that we should encourage our users to
    buy ECC systems - motherboards that support ECC, and the
    more expensive SIMMs/DIMMs that have redundant bits.

    I'd rather spend a few more dollars to *know* when memory is
    the problem during normal operations instead of trying to
    locate the source of the problem after something bad happens.

    I would be happy to lead a "documentation" project for FreeBSD
    that talks about the issues and the current hardware options.
    I've got the start of an article for the USENIX login magazine.
    If people want to encourage me to publish, please send email
    and suggest an appropriate mailing group or forum.

    Thanks
    -robert gray

    Robert Watson <rwatson@freebsd.org> Fri, 15 Oct 2004 04:14:04 EDT says:
    >On Fri, 15 Oct 2004, Guido van Rooij wrote:
    >
    >> It turns out this was a memory problem. Refitting the dimms was all
    >> that was needed to 'solve' the issue. The weird thing is that
    >> 1. The BIOS had memtesting enabled and did not complain
    >> 2. W2K seemed to install ok (though I never let it hit the disk)
    >> 3. FBSD would repeatedly crash at exactly the same spot.
    >>
    >> I am beginning to wonder if we should have a boot option that enables a
    >> thorough memtest from within the kernel...(e.g. boot -m).
    >
    >I guess the old /dev/test_for_shoddy_workmanship driver is working :-).
    >
    >It's probably just bad luck -- BIOS memory testing is generally pretty
    >poor, and it could just be FreeBSD stored your root vnode pointer (or some
    >other critical thing) in a memory word that Win2K was using for an icon,
    >so a single bit twiddle did pretty different things. Glad it's fixed. I
    >occasionally wonder if we shouldn't build a memory tester into the FreeBSD
    >boot loader to help diagnose this sort of stuff, though. Not to run every
    >boot, but as a diagnostics option.
    >
    >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    >robert@fledge.watson.org Principal Research Scientist, McAfee Research

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

  • Next message: Max Laier: "Re: network slowness/freez-up since update 10/11"

    Relevant Pages

    • Re: Activating Windows XP
      ... Memory problems can and do prevent boot. ... Also there is no such thing as "Product Captivation", ...
      (microsoft.public.windowsxp.general)
    • Re: statins dont reduce dementia risk
      ... Futher, if it is the statins that caused the memory loss, you will want to ... >>>doctor to prescribe statins. ... >>>I had used statins before I developed memory problems. ...
      (sci.med.cardiology)
    • Level of schooling may protect brain against memory loss
      ... Level of schooling may protect brain against memory loss ... Memory problems, including Alzheimer's, appeared less common in people 70 ... Seniors in 2002 might have gained protection from memory loss because they ...
      (soc.senior.issues)
    • Dodgy memory - should I replace?
      ... 128Mb RAM, and one free SO-DIMM 333Mhz slot. ... Then it would never boot... ... and found screeds of memory problems. ... memory problems appear to go away ...
      (uk.comp.sys.laptops)
    • RE: Garbage Collection - Strange Results.
      ... Memory problems do not arise in the managed environment due to numerous ... >> Task Manager the MEM USAGE is always stable yet the VM SIZE ... >> I also noticed the TOTAL HEAP SIZE of my application remainds between ...
      (microsoft.public.dotnet.framework.clr)
    Loading