From: Pat LaVarre <p.lavarre@ieee.org>
To: patmans@us.ibm.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: printk the cdb's that interest me
Date: 24 Sep 2003 09:07:02 -0600 [thread overview]
Message-ID: <1064416021.28767.10.camel@patehci2> (raw)
In-Reply-To: <20030923095248.A9896@beaverton.ibm.com>
> > ... I have no confident idea of what the cdb was, ...
>
> From: Patrick Mansfield <patmans@us.ibm.com>
> Date: Tue, 23 Sep 2003 09:52:48 -0700
>
> It got a DID_NO_CONNECT (host busy 0x01),
> so there should be no sense data. Or do you mean ...
Whoops, bonehead newbie error, sorry, specifically:
!!! I did not know this cdb had not reached the drive. !!!
Yet another reason for me to want a trace of cdb's that do reach the
drive.
Tuesday I launched a separate linux-scsi thread titled "max GiB written
per boot" to log my exploration of why, without actually unplugging my
drive, I reliably end up dying in:
dd: opening `/dev/scd1': No such device or address
> All scsi core cdb's ...
> via the host->queuecommand, ...
> only two callers ... in 2.6 ...
> ...
> [most] sent to the LLDD
> go out via scsi_dispatch_cmd, and
> come back via scsi_softirq...
Great nuggets, thanks.
Tuesday [usb-storage] worked out how to trace all cdb's that pass thru
to usb-storage.ko bInterfaceProtocol = '\x50' = *"Pat". Here I think I
have enough clues to trace at the Scsi level as well ... and then the
Scsi and Usb traces should agree.
> Ignoring the non-auto sense request and TUR
> in scsi_error.c, ...
I'll go discover what this means, unless someone tells me.
Pat LaVarre
prev parent reply other threads:[~2003-09-24 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 15:40 printk the cdb's that interest me Pat LaVarre
2003-09-23 16:52 ` Patrick Mansfield
2003-09-24 15:07 ` Pat LaVarre [this message]
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=1064416021.28767.10.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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