On Wed, Mar 07, 2007 at 11:03:21AM -0500, Alan Stern wrote: > On Tue, 6 Mar 2007, Eric Buddington wrote: > > > On Tue, Mar 06, 2007 at 01:34:41PM -0500, Alan Stern wrote: > > > The stack trace didn't include the khubd process at all. Probably that > > > means it had already died. > > > > No, it's still there. I ran 'echo t >/proc/sysrq-trigger' again, and > > khubd did not show up in dmesg: > > > > -bash-2.05b# echo t >/proc/sysrq-trigger > > -bash-2.05b# dmesg | grep khub > > -bash-2.05b# dmesg | grep SysRq > > SysRq : Show State > > SysRq : Show State > > -bash-2.05b# ps ax | grep khubd > > 163 ? R< 633:41 [khubd] > > -bash-2.05b# echo p >/proc/sysrq-trigger > > -bash-2.05b# dmesg | tail -2 > > ======================= > > SysRq : Show Regs > > -bash-2.05b# > > > > So SysRq-t doesn't show anything about khubd, and SysRq-p doesn't give > > me anything at all. What else can I try? > > I'm baffled. khubd should have shown up as the process with ID 163. Is > that process listed under a different name?
It does show up under /proc/163, for whatever that's worth. Going through the list of processes dumped by SysRq-t, here are the ones I didn't knowingly start myself: aio/0 ata/0 ata_aux ent:md1. events/0 ib_addr ib_cm/0 ib_mcast iw_cm_wq kacpid kblockd/0 kcryptd/0 khelper khpsbpkt kmirrord kmpathd/0 kprefetchd kpsmoused kseriod ksnapd ksuspend_usbd kswapd0 kthread ktxnmgrd:md1: ktxnmgrd:sda1 md2_raid1 pdflush rdma_cm reiserfs/0 scsi_eh_0 watchdog/0 And khubd is still showing up as a major CPU consumer. Interestingly, ent:sda1! is also absent from the SysRq-t listing, though present (and using lost of CPU) according to 'top' (ps, oddly, hangs in 'D' state after listing some processes). -Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
