All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Grant Coady <grant_lkml@dodo.com.au>,
	Nigel Cunningham <ncunningham@cyclades.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Mon, 3 Oct 2005 06:20:56 +0200	[thread overview]
Message-ID: <20051003042056.GC22601@alpha.home.local> (raw)
In-Reply-To: <20051003041719.GA5576@ime.usp.br>

Hi Rogerio,

On Mon, Oct 03, 2005 at 01:17:19AM -0300, Rogério Brito wrote:
(...)
> The thing is that any stick alone doesn't seem to generate a problem.
> Only when they are used simultaneously
> 
> I will test it more to see what may be wrong with my setup. :-( I still
> have not isolated and understood the problem completely. :-(

This is a common problem caused by flaky motherboards and/or poor
power supplies. You should first take a look at your motherboard's
manual to see if it *really* supports your configuration. Often,
they won't support several dual-side sticks simply because there
are too many chips connected to each signal pin. For instance, my
mobo (A7M266-D) has a lot of trouble if I use more than 2 sticks,
and it is documented that I need registered RAM to do this.

Also, sometimes your mobo will not have been carefully tested by
the maker with every combination of memory sticks. It might be
your case. Sometimes it helps to increase the RAM voltage (you
might have a jumper for this on the mobo or may be able to do
this in the BIOS). In my case, it helped to set the RAM to 2.7V,
but that was not enough to get a stable setup.

Last possible trouble may come from the power supply. If it's
not strong enough to maintain a perfect voltage output during
slightly higher intensity peaks, it can cause what you observe.

Hoping this helps,
Willy


  reply	other threads:[~2005-10-03  4:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 11:10 Strange disk corruption with Linux >= 2.6.13 Rogério Brito
2005-09-27 11:34 ` Diego Calleja
2005-09-27 11:58   ` Rogério Brito
2005-09-27 12:10     ` Rogério Brito
2005-09-27 11:57 ` Grant Coady
2005-09-27 12:43   ` Ondrej Zary
2005-10-01 21:22     ` Rogério Brito
2005-09-27 14:04   ` Lennart Sorensen
2005-10-01 21:28     ` Rogério Brito
2005-10-03 16:20       ` Lennart Sorensen
     [not found] ` <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
2005-09-27 12:20   ` Rogério Brito
2005-09-27 12:38     ` Grzegorz Kulewski
2005-09-27 19:42       ` Guennadi Liakhovetski
2005-09-27 21:01         ` Erik Mouw
2005-09-27 21:44           ` Guennadi Liakhovetski
2005-10-01 21:15         ` Rogério Brito
2005-10-08 22:35           ` Guennadi Liakhovetski
2005-10-09  9:30             ` Rogério Brito
2005-10-01 21:02       ` Rogério Brito
2005-09-27 23:31 ` Nigel Cunningham
2005-10-01 21:36   ` Rogério Brito
2005-10-02  0:06     ` Grant Coady
2005-10-03  4:17       ` Rogério Brito
2005-10-03  4:20         ` Willy Tarreau [this message]
2005-10-03  4:55     ` Nigel Cunningham
2005-10-04 10:28     ` Sander
2005-10-04 12:42       ` Nigel Cunningham
2005-09-28  8:43 ` Ville Herva
2005-09-28 23:23   ` Alan Cox
2005-09-29  6:29     ` Ville Herva
2005-09-29 16:14       ` Alan Cox
2005-10-03  5:05         ` Rogério Brito
2005-10-03  5:15   ` Rogério Brito
     [not found] <4RlFC-2ev-17@gated-at.bofh.it>
     [not found] ` <4Rxdq-2Tc-19@gated-at.bofh.it>
     [not found]   ` <4SXfs-7hM-27@gated-at.bofh.it>
2005-10-02  3:37     ` Bodo Eggert
2005-10-03  4:30       ` Rogério Brito

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=20051003042056.GC22601@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=grant_lkml@dodo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.