From: Grant Grundler <grundler@google.com>
To: Jonathan Nell <crtrn13@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi traffic sniffing
Date: Tue, 1 Sep 2009 09:06:50 -0700 [thread overview]
Message-ID: <da824cf30909010906q677e59e8v17dbd3d54cd2614d@mail.gmail.com> (raw)
In-Reply-To: <48e952f40908312313y372d5009mc0197dff49d3b778@mail.gmail.com>
On Mon, Aug 31, 2009 at 11:13 PM, Jonathan Nell<crtrn13@gmail.com> wrote:
> Is there any way to sniff the traffic of a scsi device? I need to
> debug a firmware update and need to see the traffic being passed to
> the drive
The ideal tool is a protocol analyzer for whatever transport the SCSI
device is attached to.
Here's the slide deck from a talk I once gave at OLS outlining the HW
debug tools:
http://iou.parisc-linux.org/ols_2001/slides/generated/
(and "SCSI" in that slide deck often means Parallel SCSI transport.)
Using the scsi_logging hooks described by Stefan Richter are often enough
to understand where in the process something is failing.
hth,
grant
next prev parent reply other threads:[~2009-09-01 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48e952f40908312312w7765c2a1q3a4f022967735288@mail.gmail.com>
[not found] ` <48e952f40908312313u75e4d00cr3d934f1dbdd1cca9@mail.gmail.com>
2009-09-01 6:13 ` scsi traffic sniffing Jonathan Nell
2009-09-01 10:40 ` 谢纲
2009-09-01 11:19 ` Stefan Richter
2009-09-02 3:12 ` 谢纲
2009-09-02 4:20 ` Jonathan Nell
2009-09-02 4:49 ` 谢纲
2009-09-02 6:48 ` Jonathan Nell
2009-09-02 7:21 ` Xie Gang
2009-09-02 7:50 ` Jonathan Nell
2009-09-02 8:03 ` Xie Gang
2009-09-02 12:05 ` Jonathan Nell
2009-09-01 16:06 ` Grant Grundler [this message]
[not found] ` <48e952f40909010917n7590d364sc4a16317d5e7fb0a@mail.gmail.com>
2009-09-01 16:48 ` Grant Grundler
2009-09-01 16:57 ` Ric Wheeler
2009-09-01 17:13 ` Bart Van Assche
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=da824cf30909010906q677e59e8v17dbd3d54cd2614d@mail.gmail.com \
--to=grundler@google.com \
--cc=crtrn13@gmail.com \
--cc=linux-scsi@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