Oh, the timer changes made caused sshd to hang It appears.
When it next does this I will sysctl+T and report the output.
It's still hard to track this problem, but at least its not causing the box
to hang anymore, so part of the problem is solved :-)
From: Andrew Morton [mailto:firstname.lastname@example.org]
Sent: Sunday, April 06, 2003 4:38 PM
To: Shawn Starr
Cc: email@example.com; firstname.lastname@example.org; email@example.com;
Subject: Re: [BUG][2.5.66bk9+] - changes to timers still broken - we don't
"Shawn Starr" <firstname.lastname@example.org> wrote:
> It just caused sshd to hang.
What is "it"?
I receive rather a lot of email and am dependent on people helping me
out a bit with context. I have lost the plot on this one.
> I don't know why Here's what strace reports:
> Sshd is stuck in 'D' and a child in zombie state. The machine has been up
> for 2 days 18 hours 50 mins.
a sysrq-T trace here would help.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 07 2003 - 22:00:28 EST