From: "Shawn Starr" <spstarr@sh0n.net>
To: "'Shawn Starr'" <spstarr@sh0n.net>, "'Andrew Morton'" <akpm@digeo.com>
Cc: <roland@topspin.com>, <rml@tech9.net>, <linux-kernel@vger.kernel.org>
Subject: [BUG][2.5.66bk9+] - changes to timers still broken - we don't oops anymore
Date: Sun, 6 Apr 2003 16:09:01 -0400 [thread overview]
Message-ID: <000001c2fc78$5f1df8b0$030aa8c0@unknown> (raw)
In-Reply-To:
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.
next reply other threads:[~2003-04-06 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 20:09 Shawn Starr [this message]
2003-04-06 20:20 ` [BUG][2.5.66bk9+] - changes to timers still broken - we don't oops anymore Roland Dreier
2003-04-06 20:38 ` Andrew Morton
2003-04-06 21:00 ` Shawn Starr
2003-04-09 2:12 ` [BUG][2.5.66bk9+] - tty hangings - patches, dmesg & sysctl+T info Shawn Starr
2003-04-09 4:12 ` Andrew Morton
2003-04-09 4:47 ` Roland Dreier
2003-04-09 4:56 ` Andrew Morton
2003-04-09 4:16 ` Roland Dreier
2003-04-09 4:27 ` Andrew Morton
2003-04-09 4:52 ` Roland Dreier
2003-04-09 5:01 ` Shawn Starr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001c2fc78$5f1df8b0$030aa8c0@unknown' \
--to=spstarr@sh0n.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=roland@topspin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox