linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Sabourenkov <screwdriver@lxnt.info>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Promise SATA300 TX4: errors, oops in ext3 code
Date: Tue, 02 Oct 2007 08:35:53 +0400	[thread overview]
Message-ID: <4701CAA9.6070902@lxnt.info> (raw)
In-Reply-To: <4700B966.1030508@anagramm.de>


> 
> Have you checked your memory already (memtest86)?
> 

[...]

> 
> 
> Again... sounds like bad memory to me.
> 

Nightly memtest86  run : 11 hours, 23 passes, 0 errors.


-- 

./lxnt



  parent reply	other threads:[~2007-10-02  4:33 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
2007-10-01 10:26   ` Alexander Sabourenkov
2007-10-02  4:35   ` Alexander Sabourenkov [this message]
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=4701CAA9.6070902@lxnt.info \
    --to=screwdriver@lxnt.info \
    --cc=clemens.koller@anagramm.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).