linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Alexander Sabourenkov <screwdriver@lxnt.info>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Promise SATA300 TX4: errors, oops in ext3 code
Date: Mon, 01 Oct 2007 11:09:58 +0200	[thread overview]
Message-ID: <4700B966.1030508@anagramm.de> (raw)
In-Reply-To: <47009BF6.5000208@lxnt.info>

Alexander Sabourenkov schrieb:
 > Hardware:  Athlon64, Asus A8V, Promise SATA300 TX4, 2xSeagate 7200.10
 > 320G, jumper-limited to SATA150.
 > Kernel : 2.6.22.9 amd64
 >
 > Problem:
 > Heavy load causes errors and triggers oops.

Have you checked your memory already (memtest86)?

We have several applications with Promise controllers on strange
hardware and we never had integrity problems with i.e. not so standard
SATA connections over custom vaccum-tight connectors.

 > Problems were blamed:
 >   - SATA300 being too 'hot'  (jumpered the drives)

Is this a common known problem with your harddrives or controller?
(ask google) Otherwise, it sounds like a problem with broken hardware.

 >   - cables (work perfectly on onboard controller)
 >   - interrupt sharing (found the only slot which does not share
 > interrupt line)
 >   - cooling (3 fans installed, smartctl-reported temperature at max load
 > dropped to 35C)

Try to heat up your memory a little (your wife's hair blower).
If it fails more often, your memory is most likely broken.

 >   - weak PSU (installed 600W FSP)
 >   - kernel bugs (upgraded to 2.6.22.9)
 >
 > All those measures significantly dropped error rate (from about 20 to
 > 2-4 per mirror rebuild) but did not eliminate the problem.

Again... sounds like bad memory to me.

Juat my $0.05.
Regards,

Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com



  reply	other threads:[~2007-10-01  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  7:04 Promise SATA300 TX4: errors, oops in ext3 code Alexander Sabourenkov
2007-10-01  9:09 ` Clemens Koller [this message]
2007-10-01 10:26   ` Alexander Sabourenkov
2007-10-02  4:35   ` Alexander Sabourenkov
2007-10-02  9:08     ` Clemens Koller
2007-10-02  9:49       ` Alexander Sabourenkov
2007-10-02  9:25 ` Clemens Koller

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=4700B966.1030508@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=screwdriver@lxnt.info \
    /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;
as well as URLs for NNTP newsgroup(s).