From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GS8Sr-0003j8-DT for garchives@archives.gentoo.org; Tue, 26 Sep 2006 08:38:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8Q8b4je028751; Tue, 26 Sep 2006 08:37:04 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8Q8b3Zc009882 for ; Tue, 26 Sep 2006 08:37:04 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GS8Qv-0001o7-8Y for gentoo-amd64@lists.gentoo.org; Tue, 26 Sep 2006 10:36:53 +0200 Received: from ip68-230-97-209.ph.ph.cox.net ([68.230.97.209]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Sep 2006 10:36:53 +0200 Received: from 1i5t5.duncan by ip68-230-97-209.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Sep 2006 10:36:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: "Duncan" <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: problems with emerging programs Date: Tue, 26 Sep 2006 08:36:40 +0000 (UTC) Message-ID: References: <07C6A61102C94148B8104D42DE95F7E8C8F0A4@exchange2k.envision.co.il> <03ac01c6e0cc$f47a6510$7b00a8c0@Turbo2> <45181E99.5050002@pro.onet.pl> <03cb01c6e0d2$61df0e80$7b00a8c0@Turbo2> <03ec01c6e0da$3dcc4f50$7b00a8c0@Turbo2> <03ff01c6e0de$16caf880$7b00a8c0@Turbo2> <45183C63.6010705@pro.onet.pl> <043f01c6e0eb$406476a0$7b00a8c0@Turbo2> <7573e9640609251725q52cf39efr58d0f59dfb15ce5b@mail.gmail.com> <04b401c6e136$bacb3140$7b00a8c0@Turbo2> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-97-209.ph.ph.cox.net User-Agent: pan 0.114 (Angry Albatross) Sender: news X-Archives-Salt: 33790176-e3a6-4cbd-a7c3-ae8b3925efea X-Archives-Hash: 3c4b432da8af0f835f5c86f588e912ce "Patric Douhane" 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