public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wesley J. Landaker" <wjl@icecavern.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Tejun Heo <htejun@gmail.com>,
	linux-scsi@vger.kernel.org,
	Carlos Pardo <Carlos.Pardo@siliconimage.com>
Subject: [SOLVED] Re: Support for (new?) Silicon Image PCI SATA controller
Date: Tue, 5 Dec 2006 15:48:50 -0700	[thread overview]
Message-ID: <200612051548.54416.wjl@icecavern.net> (raw)
In-Reply-To: <200611091659.16002.wjl@icecavern.net>

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

On Thursday 09 November 2006 16:59, Wesley J. Landaker wrote:
> On Thursday 09 November 2006 16:40, Matthew Wilcox wrote:
> > On Fri, Nov 10, 2006 at 08:37:23AM +0900, Tejun Heo wrote:
> > > >00:10.0 Mass storage controller [0180]: Silicon Image, Inc. Unknown
> > > > device [1095:2502] (rev 01)
> > > >        Subsystem: Silicon Image, Inc. Unknown device [1095:2512]
> > >
> > > SIMG says there's no such device and it's probably bad hardware
> > > (probably a 3512) with stuck bits in PCI ID.  If you bought it, ask
> > > for replacement.
> >
> > It could also be a problem with his motherboard.  I'd try it in a
> > different slot (or in a different machine) before returning the card
> > as bad.
>
> Guys, thank you. Your suggestion about a stuck bit sounds reasonable,
> since I couldn't find any indication of any device IDs from SI that
> matched... that's why I originally assumed it was a new device (since the
> hardware is supposedly fairly recent).
>
> I will try this out in a different motherboard slot and if there's no
> luck there see if I can get this card replaced.
>
> Thank for the help, and hopefully I can get it working. =)

Just to follow up with this, I got another new SATA card (just in case) and 
had another chance to take down the server in question and try to fix this. 

I did some testing with the other card and other slots and it was definitely 
the motherboard PCI slot that had problems. 

A different card in the same slot failed, moving to a different slot with 
the either card worked immediately. It's now shows up as I would have 
expected. Whew!

00:0f.0 Mass storage controller [0180]: Silicon Image, Inc. SiI 3512 
[SATALink/SATARaid] Serial ATA Controller [1095:3512] (rev 01)
        Subsystem: Silicon Image, Inc. SiI 3512 SATALink Controller 
[1095:3512]

Anyway, thanks everyone for your help.

-- 
Wesley J. Landaker <wjl@icecavern.net> <xmpp:wjl@icecavern.net>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2006-12-05 22:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  1:03 Support for (new?) Silicon Image PCI SATA controller Wesley J. Landaker
2006-11-09 23:37 ` Tejun Heo
2006-11-09 23:40   ` Matthew Wilcox
2006-11-09 23:59     ` Wesley J. Landaker
2006-11-11 22:47       ` Dave Jones
2006-12-05 22:48       ` Wesley J. Landaker [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=200612051548.54416.wjl@icecavern.net \
    --to=wjl@icecavern.net \
    --cc=Carlos.Pardo@siliconimage.com \
    --cc=htejun@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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