All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-ide@vger.kernel.org
Subject: Re: SATA driver sata_sil24
Date: Fri, 23 Apr 2010 23:16:13 -0500	[thread overview]
Message-ID: <4BD2708D.5050408@hardwarefreak.com> (raw)
In-Reply-To: <y2i51f3faa71004231734hbcda3ad5p61798db712cc87c5@mail.gmail.com>

My reply-list plugin sometimes has problems.  Apologies for the double hit
to your inbox Robert.

Robert Hancock put forth on 4/23/2010 7:34 PM:
> On Fri, Apr 23, 2010 at 2:34 PM, Richard Mawson
> <richard@crow.mawsonit.co.uk> wrote:

>> .. but as this is clearly later on from the previously mentioned stack, I'm
>> starting to suspect that this is failing in random places when talking across
>> this pci-pcie bridge. Do you agree that this sounds plausible?
> 
> I suspect it's something like that - not sure what else could cause
> things to explode at that point..

Hay Richard, if you've not already, try booting with the eSATA cable _not_
connected to the HBA and see if that prevents the lock up.  If it boots,
make sure both the server and disk box PSUs are both plugged into the same
AC circuit, preferably the same UPS, and that all equipment shares the same
earth ground, and give it another go.  Having equipment like this on
different earth ground paths can cause issues like what you're seeing due to
voltage differences on the eSATA wire.  Or, at least, this used to occur on
occasion with external SCSI array boxen, so I'm guessing eSATA isn't immune
given the interconnect is copper, not fiber.

Replace the eSATA cable with a "known good" cable if you haven't already.
Just helping you dot all the Ts and cross all the Is.  I know I've
overlooked small "simple" stuff on at least more than one occasion--happens
to all of us at one point or another.

Would you mind supplying the specific branded server or mobo model # so I
can do some research on possible board and/or chipset errata, known bad
card/slot combinations, etc?

-- 
Stan

  reply	other threads:[~2010-04-24  4:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100422083226.GA6018@crow.mawsonit.co.uk>
     [not found] ` <4BD0203C.7010903@gmail.com>
2010-04-22 12:17   ` SATA driver sata_sil24 Richard Mawson
2010-04-22 13:33     ` Tejun Heo
2010-04-22 22:33       ` Richard Mawson
2010-04-23  3:23         ` Robert Hancock
2010-04-23 14:06           ` Richard Mawson
2010-04-23 20:34           ` Richard Mawson
2010-04-24  0:34             ` Robert Hancock
2010-04-24  4:16               ` Stan Hoeppner [this message]
2010-04-24  5:10               ` Richard Mawson
2010-04-26 11:59                 ` Tim Small
     [not found]                   ` <20100429091436.GO5360@crow.mawsonit.co.uk>
2010-04-29 14:43                     ` Robert Hancock
2010-04-25 16:21               ` Richard Mawson
     [not found]                 ` <4BD50012.1030103@hardwarefreak.com>
2010-04-26  8:17                   ` Richard Mawson
     [not found]                     ` <4BD567CE.9070905@hardwarefreak.com>
2010-04-26 11:25                       ` Richard Mawson

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=4BD2708D.5050408@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-ide@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 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.