From: Chuck Ebbert <cebbert@redhat.com>
To: linux-kernel <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: SCSI logging sucks
Date: Wed, 07 Feb 2007 12:06:30 -0500 [thread overview]
Message-ID: <45CA0716.5060803@redhat.com> (raw)
SCSI logging isn't documented very well, and what little there is
has a problem:
In Documentation/kernel-parameters.txt we have:
scsi_logging= [SCSI]
but it's really "scsi_logging_level", as seen here in drivers/scsi/scsi.c:
module_param(scsi_logging_level, int, S_IRUGO|S_IWUSR);
MODULE_PARM_DESC(scsi_logging_level, "a bit mask of logging levels");
Not exactly helpful. And the sysctl is called:
/proc/sys/dev/scsi/logging_level
Using scsi_logging.h, I came up with this:
0000 0000 0000 0000 0000 0000 0000 0000
0x7 111 Error
0x38 11 1 Timeout
0x1c0 1 11 Scan
0xe00 111 Midlevel queue
0x7000 111 Midlevel
completions
0x38000 11 1 Lowlevel queue
0x1c0000 1 11 Lowlevel
completions
0xe00000 111 Highlevel queue
0x7000000 111 Highlevel
completions
0x38000000 11 1 IOCTL
but I'm not sure if it's right.
And the actual implementation looks backwards, at least for highlevel
events. You need to set the level to 800000 to see driver loads and
that means wading through tons of extraneous crap. The logging
should show more verbosity at the higher numbers, not start
out with the most verbose output at the low numbers.
next reply other threads:[~2007-02-07 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:06 Chuck Ebbert [this message]
2007-02-07 23:35 ` [patch] Re: SCSI logging sucks Randy Dunlap
2007-02-08 0:20 ` Martin K. Petersen
2007-02-08 7:21 ` Volker Sameske
2007-02-09 22:45 ` Chuck Ebbert
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=45CA0716.5060803@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).