From: Jeff Garzik <jeff@garzik.org>
To: Eric Schoeller <eric@junker.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_sil driver dev 0 failed to IDENTIFY (INIT_DEV_PARAMS failed)
Date: Mon, 14 Aug 2006 04:29:30 -0400 [thread overview]
Message-ID: <44E0346A.3040705@garzik.org> (raw)
In-Reply-To: <20060814034028.C66081@junker.org>
Eric Schoeller wrote:
> howdy,
>
> i am using the sata_sil driver with a Silicon Image, Inc. SiI 3112
> Controller and have recently started receiving these messages on driver
> load:
>
> [17179867.424000] libata version 1.20 loaded.
> [17179958.936000] sata_sil 0000:02:0b.0: version 0.9
> [17179958.936000] ACPI: PCI Interrupt 0000:02:0b.0[A] -> Link [LNKA] ->
> GSI 3 (level, low) -> IRQ 3
> [17179958.936000] ata1: SATA max UDMA/100 cmd 0xD0838080 ctl 0xD083808A
> bmdma 0xD0838000 irq 3
> [17179958.936000] ata2: SATA max UDMA/100 cmd 0xD08380C0 ctl 0xD08380CA
> bmdma 0xD0838008 irq 3
> [17179966.296000] ata1 is slow to respond, please be patient
> [17179975.928000] ata1: SATA link up 1.5 Gbps (SStatus 113)
> [17179975.928000] ata1: dev 0 failed to IDENTIFY (INIT_DEV_PARAMS failed)
> [17179975.928000] scsi0 : sata_sil
> [17179976.132000] ata2: SATA link down (SStatus 0)
>
> As a result, the maxtor 250gb drive fails to be detected :(
> I'm roughly 1900 miles away from this box so I have no ability to
> physically inspect the device. I'm worried that the drive is blown (sure
> wish smartmontools was compatible with libata so I might have seen this
> coming sooner!) but after checking the usual sources I'm still not
smartmontools works just fine with libata, and has for quite a while.
> Any insights are greatly appreciated!
Switch out the drive and/or cable and see what happens...
Jeff
prev parent reply other threads:[~2006-08-14 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 7:41 sata_sil driver dev 0 failed to IDENTIFY (INIT_DEV_PARAMS failed) Eric Schoeller
2006-08-14 8:29 ` Jeff Garzik [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=44E0346A.3040705@garzik.org \
--to=jeff@garzik.org \
--cc=eric@junker.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