From: "NucleoDyne Systems Inc." <nucleon@nucleodyne.com>
To: linux-kernel@vger.kernel.org
Subject: lost SCSI IO
Date: Mon, 08 Dec 2003 11:29:07 -0800 [thread overview]
Message-ID: <3FD4D103.2080007@nucleodyne.com> (raw)
I have been developing a SCSI based application and facing hardship due
to lack of better debugging support in SCSI domain on linux. May be I
am not very familiar with linux scsi subsystem.
I have a lost IO, sitting somewhere in some queue. The scsi logging
facility has been turned on with : echo "scsi log all" > /proc/scsi/scsi.
The syslog shows that the request has started:
scsi_do_req (host = 0, channel = 0 target = 3, buffer =00000000, bufflen
= 0, d)command : 00 20 00 00 00 00
Leaving scsi_do_req()
The SCSI bus trace does not show any activity.
I guess only way to find out the state of the IO is to put printf and
recompile the kernel. HP-UX had facilities like lkcd, linux crash dump
analyzer. I used to be called q4. A perl script could be written to
navigate kernel data structures and extract information from them on a
running system. If we had that kind of tool already into linux then
debugging the live system would be easier.
Is there a plan to include lkcd into default kernel?
reply other threads:[~2003-12-08 19:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FD4D103.2080007@nucleodyne.com \
--to=nucleon@nucleodyne.com \
--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