[BUG][2.5.66bk9+] - changes to timers still broken - we don't oops anymore

[Shawn Starr]

It just caused sshd to hang. 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.

Somehow, although those changes fix the kernel from oopsing, its now causing
other tty issues somewhere.

Any ideas?

Shawn.

-----Original Message-----
From: Shawn Starr [mailto:[e-mail]] 
Sent: Saturday, April 05, 2003 7:35 PM
To: 'Andrew Morton'
Cc: '[e-mail]'; '[e-mail]'; '[e-mail]'
Subject: RE: [OOPS][2.5.66bk9+] run_timer_softirq - IRQ Mishandlings - New
OOPS w/ timer

Andrew, since the new timer changes made, Things are looking solid so far.
We might want to begin adding things into BK-current no?

Sshd hasn't hung, ttys haven't hung either.

Shawn.