Date: Mon, 27 Apr 2015 12:13:41 -0400 From: Michael Powell <nightrecon@hotmail.com> To: freebsd-questions@freebsd.org Subject: Re: Debugging bad memory problems Message-ID: <mhln7m$fkh$1@ger.gmane.org> References: <CAGwOe2Y%2BRuT7MuCTBq_swn-Ny-BS-WH1J=bZTbE9L4tuv8LmCA@mail.gmail.com> <5480.69.209.235.143.1430078703.squirrel@cosmo.uchicago.edu> <CAGwOe2a7UZxSsaV4T2pcU0K1MA-OH1=123pb%2BsM=pTgSFEDLFg@mail.gmail.com> <5793.69.209.235.143.1430086547.squirrel@cosmo.uchicago.edu> <CAOgwaMs8ePhmD9%2BX6C87atHu-RxO5Q0%2Bce%2BRLMfhMDPfcmpxGQ@mail.gmail.com> <553D8452.9050601@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
jd1008 wrote: [snip] > One slight, and perhaps remote, possibility is that memory > is a hair slower than what the memory controller expects, > especially, as Valerie mentioned, under heavy memory load. > On systems where the cpu clocking is unlocked, one might > be able to slow down the cpu clock just slightly to see if the > problem is mitigated. Another consideration is the power supply. An aged power supply can be right on the raggedy edge ripple wise such that it seems OK when not under load. Place a load on it and the ripple shoots up. Easy to see with an oscilloscope. Not to mention the machine's behavior gets extremely erratic. If it works fine on a known good battery under battery only (pure DC), but flakes when plugged up to the AC mains... I only bring this up because I have chased my tail looking for memory problems when it turned out to be a power supply about to go south. I doubt this is his situation though. He's most likely right that it is memory. I just include this to get away from 'tunnel' vision. -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?mhln7m$fkh$1>