[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0703081008340.4086-100000@iolanthe.rowland.org>
Date: Thu, 8 Mar 2007 10:10:53 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Pete Zaitcev <zaitcev@...hat.com>
cc: ebuddington@...leyan.edu, Oliver Neukum <oneukum@...e.de>,
USB development list <linux-usb-devel@...ts.sourceforge.net>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] khubd and ent:sda1 sucking CPU with reiser4
+ USB HD
On Wed, 7 Mar 2007, Pete Zaitcev wrote:
> On Wed, 7 Mar 2007 17:18:29 -0500 (EST), Alan Stern <stern@...land.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.
You mean, if it is currently running? I don't believe that. A simple
test comparison shows every process listed in "ps -A" also listed in
SysRq-t.
> 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".
If it was killed then it wouldn't show up in "ps" or as a directory under
/proc.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists