linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Warner <andyw@pobox.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [SATA] status report, libata-dev queue updated
Date: Fri, 5 Nov 2004 13:26:13 -0600	[thread overview]
Message-ID: <20041105132613.A30910@florence.linkmargin.com> (raw)
In-Reply-To: <418BCED3.1030600@wasp.net.au>; from brad@wasp.net.au on Fri, Nov 05, 2004 at 11:04:51PM +0400

Brad Campbell wrote:
> [...]
> Read that as "I have tried really, really hard to break it and as yet been unable to".

Is your system SMP ? I'm actively tracking a problem now with
pass-thru behaviour (via /dev/sg* ) on SMP systems.

Symptom is a system freeze after a few messages like
this:

ata3: command 0x34 timeout, stat 0x58 host_stat 0x0
ata2: command 0x24 timeout, stat 0x58 host_stat 0x0
ata3: status=0x58 { DriveReady SeekComplete <4>ATA: abnormal status 0x58 on port 0xF8A3CCC7
ata2: status=0x58 { DriveReady SeekComplete DataRequest }
DataReq

This particular example is of a Read Sectors command pending
on one drive and Write Sectors on another. Don't know if it
is the pio state machine not being SMP-safe, or what just yet.
-- 
andyw@pobox.com

Andy Warner		Voice: (612) 801-8549	Fax: (208) 575-5634

  reply	other threads:[~2004-11-05 19:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 10:00 [SATA] status report, libata-dev queue updated Jeff Garzik
2004-11-05 19:04 ` Brad Campbell
2004-11-05 19:26   ` Andy Warner [this message]
2004-11-05 19:44     ` Brad Campbell
2004-11-06  0:06       ` Andy Warner
  -- strict thread matches above, loose matches on Subject: below --
2004-10-01  4:58 [sata] " Jeff Garzik
2004-10-01 11:55 ` Brad Campbell
2004-10-01 12:38 ` Jesse Stockall

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=20041105132613.A30910@florence.linkmargin.com \
    --to=andyw@pobox.com \
    --cc=brad@wasp.net.au \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).