Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Ludovico Cavedon <ludovico.cavedon@gmail.com>
To: Tejun Heo <tj@kernel.org>, Stan Hoeppner <stan@hardwarefreak.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: understanding the cause of ATA failures
Date: Thu, 25 Mar 2010 19:22:00 -0700	[thread overview]
Message-ID: <4BAC1A48.5020904@gmail.com> (raw)
In-Reply-To: <4BAAB3D0.90704@kernel.org>

Tejun Heo wrote:
> If you have the machine locally, one thing you can try is to pull out
> all the drives and hook them up directly to the motherboard bypassing
> the backplane and see whether anything changes.

Yes, I think I'll try to go this way. Unfortunately (or not :) the issue
happens once a month... I'll see if icnreasing the load on the machine
it will happen more frequently.

Stan Hoeppner wrote:
> In short, I don't know how it all needs to be hooked up, what the specific
> device combination needs to be, or what Linux modules you need to
> communicate with the MG9072 chip on that backplane.  Again, call your
> vendor.  It's their product.  They should have the answers.

Yes, I talked to supermirco and suggested basically what Tejun did:
bypass the backplane and see if the problem persists.

> Your welcome.  Glad to pass on some of my experience if it can help someone
> else.  I wish there was more I could do at this point, but it's pretty much
> up to you now.  Hope I've helped steer you in the right direction.  As
> always, don't put all your eggs in this one troubleshooting basket.  The
> cause of the problem could also lie elsewhere so keep and open mind and
> don't throw up your hand in frustration if this track doesn't pan out.

Very valuable info, thank you.

Cheers,
Ludovico

  reply	other threads:[~2010-03-26  2:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 21:50 understanding the cause of ATA failures Ludovico Cavedon
2010-03-18 22:00 ` Tim Small
2010-03-18 22:13   ` Ludovico Cavedon
2010-03-18 22:33     ` Stan Hoeppner
2010-03-18 23:03       ` Ludovico Cavedon
2010-03-18 23:39         ` Stan Hoeppner
2010-03-19  3:38           ` Ludovico Cavedon
2010-03-19 10:26             ` Stan Hoeppner
2010-03-25  0:52             ` Tejun Heo
2010-03-26  2:22               ` Ludovico Cavedon [this message]
2010-03-22  3:37 ` Robert Hancock

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=4BAC1A48.5020904@gmail.com \
    --to=ludovico.cavedon@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=stan@hardwarefreak.com \
    --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