public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: dougg@torque.net
Cc: Gilbert Wu <Gilbert_Wu@adaptec.com>, Linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic94xx: fix smartctl utility problem
Date: Sun, 16 Sep 2007 18:21:11 -0500	[thread overview]
Message-ID: <1189984871.3383.17.camel@localhost.localdomain> (raw)
In-Reply-To: <46EDB5B7.10101@torque.net>

On Sun, 2007-09-16 at 19:01 -0400, Douglas Gilbert wrote:
> James Bottomley wrote:
> > On Sat, 2007-09-15 at 12:05 -0500, James Bottomley wrote:
> >> On Fri, 2007-09-14 at 10:58 -0700, Gilbert Wu wrote:
> >>> Fixed the problem that "smartctl -a /dev/some_sata_disk -d ata"  does
> >>> not work on SATA device. ( The smartctl v5.38 does need "-d ata"
> >>> option.)
> >>>   The aic94xx need to return ATA output register for all ATA commands
> >>> except ATA Read/Write commands.
> >>>   The aic94xx also mark out the DRQ bit from status register which is
> >>> treated as AC_ERR_HSM (host state machine violation) error by top layer
> >>> if it set to one.
> >>>  The firmware of aic94xx chip handle all ATA handshaking, data transfer
> >>> and return ATA output register which is sent by the device.  So the DRQ
> >>> bit may not reflect the last state of device when the command finished
> >>> and it is no meaning for the caller.
> >>>
> >>> Signed-off-by: Gilbert Wu <gilbert_wu@adaptec.com>
> >> I'm afraid this can't go in.  It has a bad effect on my expander remote
> >> ATAPI device:
> > 
> > OK, found the root cause: your CSMI_TASK flag is getting set on all
> > packet commands.  I can think of two fixes: either smartctl should never
> > be used on ATAPI devices (reasonable, since smart is a disc protocol),
> 
> Feature code 101h in MMC seems to sink your argument for
> cd/dvd drives.

I was more thinking that smartctl is a pure ATA type thing (The problem
which the flag is set for is to allow smartctl to muck with ATA
commands)... the MMC devices supporting smart features report this via
the informational exceptions mode page to conform to the MMC command
set.  So, when smartctl does SCSI transports, they'll go via a packet
command anyway.

> Also tape drives may support SMART and if they do,
> smartmontools can access the associated data. And tape
> drives may be on an ATAPI transport.

That's probably via the same mechanism, isn't it?

James



  reply	other threads:[~2007-09-16 23:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 17:58 [PATCH] aic94xx: fix smartctl utility problem Gilbert Wu
2007-09-14 18:14 ` Jeff Garzik
2007-09-15 17:05 ` James Bottomley
2007-09-16 16:37   ` James Bottomley
2007-09-16 19:43     ` Jeff Garzik
2007-09-16 23:01     ` Douglas Gilbert
2007-09-16 23:21       ` James Bottomley [this message]
2007-09-17 20:53         ` Wu, Gilbert
2007-09-17 22:59           ` James Bottomley
2007-09-18  1:43             ` Wu, Gilbert
2007-09-18  3:31               ` James Bottomley
2007-09-21 18:53             ` Wu, Gilbert
2007-09-21 20:40               ` James Bottomley
2007-09-21 23:05                 ` Wu, Gilbert
2007-09-20 18:52         ` Douglas Gilbert
2007-09-18 20:35 ` Luben Tuikov
  -- strict thread matches above, loose matches on Subject: below --
2007-09-14 12:30 Gilbert Wu
2007-09-14 17:26 ` Jeff Garzik
2007-09-14 17:30   ` Wu, Gilbert
2007-09-05 22:25 Gilbert Wu
2007-09-06 10:06 ` Jeff Garzik
2007-09-06 18:33   ` Wu, Gilbert
2007-09-07 23:00     ` Jeff Garzik
2007-09-07 23:58       ` Wu, Gilbert

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=1189984871.3383.17.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=Gilbert_Wu@adaptec.com \
    --cc=Linux-scsi@vger.kernel.org \
    --cc=dougg@torque.net \
    /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