From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: problems with emerging programs
Date: Tue, 26 Sep 2006 08:36:40 +0000 (UTC) [thread overview]
Message-ID: <efaoqn$bb2$2@sea.gmane.org> (raw)
In-Reply-To: 04b401c6e136$bacb3140$7b00a8c0@Turbo2
"Patric Douhane" <patric@ownit.se> posted
04b401c6e136$bacb3140$7b00a8c0@Turbo2, excerpted below, on Tue, 26 Sep
2006 08:41:00 +0200:
> Ok that could be it, though I've never noticed that there could be
> something wrong with the memory before, but I ran Windows XP and perhaps
> you don't notice such problems then? Can I test my memory with Memtest86??
You can, but it won't necessarily find a problem. If it does tho, you
know you have one, but on mine, it didn't, because the problem wasn't
really with the memory, but with the speed of access. Memtest86 came up
100% fine, but it was running on an otherwise idle system (duh, since you
boot to it and can't be running anything else at the time), and simply
wasn't stressing the timings enough to trigger the problem, which as I
said wasn't the memory cells themselves going bad, but simply the timing.
That was part of the frustration. At first I didn't know which component
it was, and the memory never did actually turn out bad. It's just that it
wasn't stable at the rated speed when under stress. I never /did/
actually know it was the memory until I got the BIOS that let me slow it
down, and that cured it -- and then when I got new memory and it ran just
fine at the higher speed, so it wasn't that the mobo memory traces simply
couldn't handle it either.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-26 8:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 11:20 [gentoo-amd64] problems with emerging programs Nadav Horesh
2006-09-25 15:06 ` Patric Douhane
2006-09-25 16:32 ` Petter Haggholm
2006-09-25 16:49 ` Patric Douhane
2006-09-25 17:15 ` Patric Douhane
2006-09-25 17:44 ` Joaquim Quinteiro Uchoa
2006-09-25 18:03 ` Patric Douhane
2006-09-25 18:23 ` Piotr Pruszczak
2006-09-25 18:42 ` Patric Douhane
2006-09-25 19:27 ` [gentoo-amd64] " Duncan
2006-09-25 19:38 ` Patric Douhane
2006-09-25 19:53 ` Duncan
2006-09-25 20:06 ` Patric Douhane
2006-09-25 20:30 ` Piotr Pruszczak
2006-09-25 21:40 ` Patric Douhane
2006-09-25 22:15 ` Peter Davoust
2006-09-26 0:25 ` Richard Fish
2006-09-26 6:06 ` Duncan
2006-09-26 6:41 ` Patric Douhane
2006-09-26 8:36 ` Duncan [this message]
2006-09-26 8:50 ` Richard Fish
2006-09-26 15:51 ` [gentoo-amd64] Re: problems with emerging programs [SOLVED] Patric Douhane
2006-09-26 23:42 ` Duncan
2006-09-30 16:04 ` [gentoo-amd64] problems with emerging programs Ronan Klyne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='efaoqn$bb2$2@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox