public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid@fc.hp.com>
To: Camm Maguire <camm@enhanced.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 IDE tape problem, with ide-scsi
Date: Tue, 27 Feb 2001 10:07:21 -0500	[thread overview]
Message-ID: <3A9BC2A9.F5EE8554@fc.hp.com> (raw)
In-Reply-To: <54u25g3yb9.fsf_-_@intech19.enhanced.com>

Camm Maguire wrote:
> 
> The Conner gives the problem:
> 
> Feb 27 06:23:16 intech9 kernel: st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sns = 70  5
> Feb 27 06:23:16 intech9 kernel: ASC=20 ASCQ= 0
> Feb 27 06:23:16 intech9 kernel: Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
> 
> and occaisional 'gunzip: unexpected end of file' errors on verifying
> the tape.
> 
> Take care,
> 
> --
> Camm Maguire                                            camm@enhanced.com

ASC/ASCQ of 0x20/0x00 means "Invalid command operation code". So the
drive is rejecting a command sent to it by the driver. If the other
drive that is working is identical to seemingly non-working one, maybe
this drive is going bad. 

st driver prints the SCSI command that may have caused this error only
when compiled with debug turned on. Maybe st driver should always print
the command that results in a check condition as long as the command is
not a Test Unit Ready or Mode Sense. 
 
====================================================================
Khalid Aziz                             Linux Development Laboratory
(970)898-9214                                        Hewlett-Packard
khalid@fc.hp.com                                    Fort Collins, CO

  reply	other threads:[~2001-02-27 17:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 16:06 2.2.18 IDE tape problem, with ide-scsi Camm Maguire
2001-02-27 15:07 ` Khalid Aziz [this message]
2001-02-27 17:19   ` Camm Maguire
2001-02-27 15:34     ` Khalid Aziz
2001-02-27 19:52       ` Camm Maguire
2001-02-27 18:18         ` Khalid Aziz
2001-02-27 20:26           ` Andre Hedrick
2001-02-27 21:26             ` Khalid Aziz
2001-02-28 15:23           ` Camm Maguire
2001-02-28 15:34             ` Mike Dresser
2001-03-07 22:54           ` Camm Maguire
2001-03-12 16:52             ` Khalid Aziz
2001-03-13 14:14               ` Camm Maguire
2001-02-27 17:32     ` Mike Dresser
2001-02-27 18:31       ` Camm Maguire
2001-02-27 18:34         ` Mike Dresser
2001-02-27 19:05           ` Andre Hedrick
2001-02-27 19:40             ` Camm Maguire
2001-03-01 17:02               ` Khalid Aziz
2001-02-27 22:21           ` Alan Cox
2001-02-27 19:01       ` Andre Hedrick
2001-02-27 19:04         ` Mike Dresser
2001-03-07  0:34 ` [PATCH] " Chip Salzenberg
2001-03-07  1:09   ` Andre Hedrick
     [not found] <Pine.LNX.4.10.10102271153560.29323-100000@coffee.psychology.mcmaster.ca>
2001-02-27 17:16 ` Camm Maguire

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=3A9BC2A9.F5EE8554@fc.hp.com \
    --to=khalid@fc.hp.com \
    --cc=camm@enhanced.com \
    --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