public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Wu, Gilbert" <Gilbert_Wu@adaptec.com>
Cc: dougg@torque.net, Linux-scsi@vger.kernel.org
Subject: RE: [PATCH] aic94xx: fix smartctl utility problem
Date: Mon, 17 Sep 2007 22:31:56 -0500	[thread overview]
Message-ID: <1190086316.3386.72.camel@localhost.localdomain> (raw)
In-Reply-To: <BC382691D59EC94C8E57543C47EF8ED55B20E3@aime2k302.adaptec.com>

On Mon, 2007-09-17 at 18:43 -0700, Wu, Gilbert wrote:
>  ata_task_return code=0   ====> ****** cmd success then the no ATA
> output register return.
> scsi 2:0:0:0: CD-ROM            PLEXTOR  DVDR   PX-755A   1.02 PQ: 0
> ANSI: 5
> scsi 2:0:0:0: Attached scsi generic sg2 type 5
> ata command=a0
>  ata_task_return code=c  ======> ***** cmd failed then return ATA output
> register
> return reg= 34 40 51 54 0 0 0 a0 0
> ata command=a0
>  ata_task_return code=1

That just says a packet command returned an illegal request ... I think
the CD layer expects this, but without seeing the SCSI command it's hard
to tell.

> sas: sas_ata_phy_reset: Found ATAPI device.
> ata command=a0
>  ata_task_return code=c
> return reg= 34 40 51 24 0 0 20 a0 0
> ata command=a0
>  ata_task_return code=1

This again is a packet command returning not ready (probably no media
present).

> ata command=a0
>  ata_task_return code=c
> return reg= 34 40 51 24 0 0 20 a0 0
> ata command=a0
>  ata_task_return code=1
> ata command=a0
>  ata_task_return code=c
> return reg= 34 40 51 24 0 0 20 a0 0
> ata command=a0
>  ata_task_return code=1
> ata command=a0
>  ata_task_return code=c
> return reg= 34 40 51 24 0 0 20 a0 0
> ata command=a0
>  ata_task_return code=1

These again look like normal CD probes returning not ready.

> ata command=a0
> ------------[ cut here ]------------
> kernel BUG at drivers/ata/libata-core.c:1380!
> invalid opcode: 0000 [#1]

OK, this is the fascinating one ... I think it's a bug in libata itself.
It seems to mean that the tag its trying to use (which is fixed by
convention) is already outstanding.  Since the current probe sequence is
single threaded, I can't really see how this has happened.

James



  reply	other threads:[~2007-09-18  3:32 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
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 [this message]
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=1190086316.3386.72.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