From: jtholmesjr@comcast.net
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test8 scsi logging not working
Date: Fri, 24 Oct 2003 03:10:53 +0000 [thread overview]
Message-ID: <102420030310.18374.4e89@comcast.net> (raw)
I dont take the mail list dist just answer here in and i will see the
answer.
The problem:
I thought
echo "scsi log all" >/proc/scsi/scsi
with
scsi_logging=y in .config
would turn on kernel scsi logging and put some notification line
in /var/log/messages
indicating scsi logging was now active at such and such a level
that is not happening and I have a external drive connected via
usb talking scsi that cannot be unmounted and i need to trace
scsi action so I can post here.
lsscsi output is
[0:0:0:0] disk USB 2.0 Storage Device 0100 /dev/sda
[1:0:0:0] disk Linux scsi_debug 0004 /dev/sdb
any help would be appreciated.
thanks
jt
--
Please respond to
jtholmes@jtholmes.com
Not to jtholmesjr@comcast.net
next reply other threads:[~2003-10-24 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 3:10 jtholmesjr [this message]
2003-10-24 3:36 ` mmap to Access PCI space? Randall Hyde
2003-10-24 7:57 ` David S. Miller
2003-10-24 5:17 ` 2.6.0-test8 scsi logging not working Mike Anderson
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=102420030310.18374.4e89@comcast.net \
--to=jtholmesjr@comcast.net \
--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;
as well as URLs for NNTP newsgroup(s).