Messages in this thread | ![/](/images/icornerl.gif) | | From | "Shawn Starr" <> | Subject | RE: [BUG][2.5.66bk9+] - changes to timers still broken - we don't oops anymore | Date | Sun, 6 Apr 2003 17:00:48 -0400 |
| |
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 :-)
Shawn.
-----Original Message----- From: Andrew Morton [mailto:akpm@digeo.com] Sent: Sunday, April 06, 2003 4:38 PM To: Shawn Starr Cc: spstarr@sh0n.net; roland@topspin.com; rml@tech9.net; linux-kernel@vger.kernel.org Subject: Re: [BUG][2.5.66bk9+] - changes to timers still broken - we don't oops anymore
"Shawn Starr" <spstarr@sh0n.net> 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |