From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
dvyukov@google.com, hare@suse.com, hch@lst.de,
martin.petersen@oracle.com
Subject: Re: [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control
Date: Tue, 18 Jul 2017 12:33:59 -0500 [thread overview]
Message-ID: <ufak235abug.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <20170718073747.GD4875@linux-x5ow.site> (Johannes Thumshirn's message of "Tue, 18 Jul 2017 09:37:47 +0200")
I have verified that building a clean v4.12 with
68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 cherry picked on top still
shows the problem:
[root@backup2 ~]# mtx -f /dev/sg7 next 0
Unloading drive 0 into Storage Element 45...mtx: Request Sense: Long
Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=0 (Unknown?!)
mtx: Request Sense: Sense Key=No Sense
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 00
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
MOVE MEDIUM from Element Address 1 to 1045 Failed
Nothing appears to be logged; is there any kind of debugging information
I can collect which might help to track this down? I'm not particularly
good at this but I am pretty sure that I'm building everything properly
and am actually booting the patched kernel.
- J<
next prev parent reply other threads:[~2017-07-18 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 0:44 [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control Jason L Tibbitts III
2017-07-18 7:37 ` Johannes Thumshirn
2017-07-18 16:53 ` Jason L Tibbitts III
2017-07-18 17:33 ` Jason L Tibbitts III [this message]
2017-07-19 7:03 ` Johannes Thumshirn
2017-07-19 8:13 ` Jason L Tibbitts III
2017-07-19 8:36 ` Johannes Thumshirn
2017-07-21 16:43 ` Johannes Thumshirn
2017-07-21 19:23 ` Jason L Tibbitts III
2017-07-25 7:18 ` Johannes Thumshirn
2017-07-25 18:25 ` Jason L Tibbitts III
2017-07-26 7:39 ` Johannes Thumshirn
2017-07-26 20:19 ` Jason L Tibbitts III
2017-07-25 19:09 ` Douglas Gilbert
2017-07-26 7:22 ` Johannes Thumshirn
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=ufak235abug.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--cc=dvyukov@google.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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