From: Robert Hancock <hancockrwd@gmail.com>
To: Tomas Lund <tlund@nxs.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_sil24 failed command: READ FPDMA QUEUED
Date: Fri, 30 Jul 2010 12:30:24 -0600 [thread overview]
Message-ID: <4C531A40.6080804@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.1007211433360.24693@envy.nxs.se>
On 07/21/2010 06:38 AM, Tomas Lund wrote:
> On Wed, 21 Jul 2010, Tomas Lund wrote:
>
>> Put the "LYCOM SATA PE-103 2-CH" back in the server with the Gigabyte
>> 965P-DS4 motherboard and installed the debian backports kernel
>> 2.6.32-bpo.5-amd64.
>>
>> Problem persists and a dmesg and console output (since dmesg buffer is
>> too small to fit everything) is available at:
>>
>> http://tlund.pp.se/sil24/console_2.6.32-bpo.5-amd64.txt
>> http://tlund.pp.se/sil24/dmesg_2.6.32-bpo.5-amd64.txt
>
> Tested Debian 2.6.26-2-amd64, files at the same place.
What does "hdparm -I" show when run on the drive attached to that
controller? Is it possible there's some security locking enabled on it?
If the BIOS is doing some kind of security unlock then it probably does
it only on drives attached to the motherboard controller, not on any
add-in cards. It certainly seems like the drive is returning command
aborted on all reads when connected to that controller for whatever reason.
next prev parent reply other threads:[~2010-07-30 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 21:09 sata_sil24 failed command: READ FPDMA QUEUED Tomas Lund
2010-07-14 1:30 ` Robert Hancock
2010-07-14 8:02 ` Tomas Lund
2010-07-15 19:05 ` Tomas Lund
2010-07-17 12:29 ` Tomas Lund
2010-07-21 12:06 ` Tomas Lund
2010-07-21 12:38 ` Tomas Lund
2010-07-30 18:30 ` Robert Hancock [this message]
2010-08-01 14:27 ` Tomas Lund
2010-08-01 16:55 ` Tomas Lund
2010-08-01 21:15 ` Robert Hancock
2010-08-02 7:21 ` sata_sil24 failed command: READ FPDMA QUEUED (resolved) Tomas Lund
2010-08-02 18:23 ` Robert Hancock
2010-08-03 5:33 ` Tomas Lund
2010-08-06 5:03 ` Robert Hancock
2010-08-12 14:09 ` Gwendal Grignou
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=4C531A40.6080804@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=tlund@nxs.se \
/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