Messages in this thread | | | From | "Shawn Starr" <> | Subject | [BUG][2.5.66bk9+] - changes to timers still broken - we don't oops anymore | Date | Sun, 6 Apr 2003 16:09:01 -0400 |
| |
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:spstarr@sh0n.net] Sent: Saturday, April 05, 2003 7:35 PM To: 'Andrew Morton' Cc: 'roland@topspin.com'; 'rml@tech9.net'; 'linux-kernel@vger.kernel.org' 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.
- 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/
| |