From: John Moser <john.r.moser@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: What would cause freezes that numlock fixes?
Date: Sun, 05 Apr 2009 18:57:26 -0400 [thread overview]
Message-ID: <49D93756.2080608@gmail.com> (raw)
I'm using Ubuntu's current beta 9.04 and it's having issues. I think
it's a kernel thing, but I have no debug data or anything; if anyone has
any insight as to what might be happening I'd like that. I can't do
debugging here (unless they package a debugging kernel).
I'm using what Ubuntu calls "2.6.28-11.40" "generic", on x86-64, with
the uname:
Linux icebox 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC
2009 x86_64 GNU/Linux
What's happening is this:
I noticed immediately that the system lags a lot, especially when under
load, sometimes when not under load. I figured bad scheduling at first.
Switching to ext4 helped.
Oddly enough, switching to elevator=as instead of CFQ helps as well.
This helps, but doesn't fix the problem. So, I'm guessing there's no
bug in CFQ or EXT3, but running these rather than AS and EXT4 aggravates
symptoms.
Occasionally almost everything in X will freeze. Some programs (like, a
terminal) still work until they try to access the disk (say, if I run a
command, bash hangs). I eventually had this happen while top was
running and noticed stuff going into state D and staying there for up to
5 minutes, while the disk halts. I can still shift between virtual
desktops in Gnome, with the stipulation that every application is frozen
and I can't start any others.
At some point (today, actually) I found a workaround. When
applications-- either one, or all of them-- start to freeze, if I press
(specifically) the Num Lock key, everything suddenly wakes up. Disk
starts cranking like crazy, windows redraw, and I assume everything
instantly comes back out of D state.
Just Num Lock. Not A, not CTRL, not Tab. Just Num Lock.
Anyone have any guesses?
next reply other threads:[~2009-04-05 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 22:57 John Moser [this message]
2009-04-06 2:36 ` What would cause freezes that numlock fixes? Trenton D. Adams
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=49D93756.2080608@gmail.com \
--to=john.r.moser@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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