From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org
Subject: Re: Unplugging of SBP-2 devices still does not work
Date: Sat, 30 Jul 2005 23:52:34 +0200 [thread overview]
Message-ID: <42EBF6A2.7040305@s5r6.in-berlin.de> (raw)
In-Reply-To: <20050726042640.GA17885@phunnypharm.org>
Ben Collins wrote on 2005-07-26:
> Sounds like it is probably hanging in sbp2 while it is trying to logout.
I don't think so. According to dmesg with SBP2_DEBUGs enabled,
scsi_remove_device() is entered but sbp2_logout_device() not.
IOW scsi_remove_device() is not completed. (I'm using sbp2 rev
1316 which calls scsi_remove_device() before logout. Also, I'm
on 2.6.13-rc4 now.)
> Perhaps you can turn on spinlock debug to see if there is a deadlock
> somewhere? Check wstat for the knodemgrd process aswell, see what it is
> waiting for.
I did not enable spinlock debugging yet.
Here is more process info for now:
# ps lx
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
1 0 1539 1 15 0 0 0 scsi_w D ? 0:00 [knodemgrd_1]
# cat /proc/1539/wchan
scsi_wait_req
Patrick Mansfield wrote on 2005-07-27:
> Seeing sysrq-t stack traces might help debugging.
The knodemgrd is not traced by sysrq-t, and no userspace task is
hanging.
Thanks for the hints so far, I will hopefully be back with better
debug info later.
--
Stefan Richter
-=====-=-=-= -=== ====-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2005-07-30 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 19:43 Unplugging of SBP-2 devices still does not work Stefan Richter
2005-07-23 19:58 ` Stefan Richter
2005-07-26 4:26 ` Ben Collins
2005-07-30 21:52 ` Stefan Richter [this message]
2005-07-30 23:15 ` Stefan Richter
[not found] ` <20050731173554.GA2970@us.ibm.com>
2005-07-31 18:48 ` Stefan Richter
2005-07-31 20:17 ` Stefan Richter
2005-07-26 22:09 ` Patrick Mansfield
2005-07-31 23:43 ` Unplugging of SBP-2 devices still does not work --- solved Stefan Richter
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=42EBF6A2.7040305@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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