From: Pete Zaitcev <zaitcev@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: ebuddington@wesleyan.edu, Oliver Neukum <oneukum@suse.de>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] khubd and ent:sda1 sucking CPU with reiser4 + USB HD
Date: Wed, 7 Mar 2007 15:02:27 -0800 [thread overview]
Message-ID: <20070307150227.e5395d6c.zaitcev@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0703071713220.9831-100000@iolanthe.rowland.org>
On Wed, 7 Mar 2007 17:18:29 -0500 (EST), Alan Stern <stern@rowland.harvard.edu> wrote:
> I've never heard of a process failing to show up in a SysRq-t listing. It
> suggests something is wrong with the process management in the kernel you
> were using. That leads me to think a non -mm kernel might give more
> informative results.
I think, if a process is looping, it's not shown in SysRq-t. So maybe
khubd is on a CPU.
In RHEL we have a patch for SysRq-w, which showed all CPU states by
the way of a special IPI (unless looping with closed interrups, of course).
But this capability seems a bit degraded in stock SysRq-w. It might not
catch this (does not seem for me in 2.6.20).
Another possibility is, something killed khubd. It's only a process
after all. Remember how we had grief with it being killed by "telinit 1".
-- Pete
next prev parent reply other threads:[~2007-03-07 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070306154854.GD9198@pool-71-123-121-36.spfdma.east.verizon.net>
2007-03-06 18:34 ` Alan Stern
2007-03-06 19:06 ` Eric Buddington
2007-03-07 16:03 ` Alan Stern
2007-03-07 16:32 ` Eric Buddington,,,
2007-03-07 20:22 ` Alan Stern
2007-03-07 20:47 ` Eric Buddington
2007-03-07 22:18 ` Alan Stern
2007-03-07 23:02 ` Pete Zaitcev [this message]
2007-03-08 15:10 ` Alan Stern
2007-03-06 8:52 Oliver Neukum
2007-03-06 15:36 ` [linux-usb-devel] " Alan Stern
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=20070307150227.e5395d6c.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=ebuddington@wesleyan.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®