* lost SCSI IO
@ 2003-12-08 19:29 NucleoDyne Systems Inc.
0 siblings, 0 replies; only message in thread
From: NucleoDyne Systems Inc. @ 2003-12-08 19:29 UTC (permalink / 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
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-12-08 19:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-08 19:29 lost SCSI IO NucleoDyne Systems Inc.
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).