mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <pierre-list@ossman.eu>
To: linux-ide@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Strange read data corruption on ext4/LVM/md
Date: Sun, 16 Jan 2011 15:01:54 +0100	[thread overview]
Message-ID: <20110116150154.127ea8b1@mjolnir.ossman.eu> (raw)
In-Reply-To: <20100715213801.627f095a@mjolnir.ossman.eu>

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

On Thu, 15 Jul 2010 21:38:01 +0200
Pierre Ossman <pierre-list@ossman.eu> wrote:

> 
> Status update:
> 
> 1. Putting the other sil3132 controller did not make any problems
> appear.
> 
> 2. Next I swapped that controller with the one next to it to test if
> this specific board design in combination with this specific slot was
> causing the issues. Still no corruption.
> 
> 3. Today I put the "bad" controller back in, but in a different slot.
> Still not seeing any issues.
> 
> I could move it back to the inital slot to see if the problem
> reappears, but I'm just happy the system is error free again so I'll
> write this off as a temporary glitch or a bad combination of card and
> slot.
> 

Time for an update to this somewhat old thread. The problem has
remained, but being so very rare that I cannot reproduce it often
enough for systematic testing. Both motherboard and the "bad"
controller have been swapped out with different (but identical) cards.

These days there are some controller cards based on Marvell's 88SE9128,
which seems to be a decent chip. So the next step is chucking all the
sil3132 stuff in favour of those...

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by FRA, a
  Swedish intelligence agency. Make sure your server uses
  encryption for SMTP traffic and consider using PGP for
  end-to-end encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

      reply	other threads:[~2011-01-16 14:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 20:56 Pierre Ossman
2010-05-19 21:04 ` Pierre Ossman
2010-05-19 21:29   ` Pierre Ossman
2010-05-19 21:34     ` Pierre Ossman
2010-05-20  7:14       ` Pierre Ossman
2010-05-20  8:57         ` Tejun Heo
2010-05-20  9:29           ` Pierre Ossman
2010-05-20  9:42             ` Tejun Heo
2010-05-20 10:22               ` Pierre Ossman
2010-05-20 14:00                 ` Pierre Ossman
2010-05-20 16:28                   ` Pierre Ossman
2010-07-15 19:38                     ` Pierre Ossman
2011-01-16 14:01                       ` Pierre Ossman [this message]

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=20110116150154.127ea8b1@mjolnir.ossman.eu \
    --to=pierre-list@ossman.eu \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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

all inboxes | Powered by JetHome®