From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Scheduler issue?
Date: Fri, 15 Aug 2003 16:21:44 +0200 [thread overview]
Message-ID: <yw1xadabf1c7.fsf@users.sourceforge.net> (raw)
First the machine details. It's a Pentium4 running at 2 GHz. Linux
version 2.6.0-test3 + O15int + softrr.
I just experienced something that might be a scheduler problem. I was
working in XEmacs, when suddenly the machine became very
unresponsive. The mouse pointer in X moved sporadically. I could
switch to a text console and log in, though typing lagged tens of
seconds. Switching between text consoles was fast, though. I killed
xemacs, and the system was back to normal. Further investigation
showed that xemacs was stuck in a nasty regexp match. If I was quick
enough, I could interrupt it with C-g.
With X and the window manager reniced to -10, they seem to be able to
get their job done. This leads me to believe that maybe xemacs is
considered interactive, and given too high priority when it suddenly
starts burning the cpu.
I'll try it later with other kernel versions, but right now I don't
want to reboot.
What can I do to collect more information about the problem?
--
Måns Rullgård
mru@users.sf.net
reply other threads:[~2003-08-15 16:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=yw1xadabf1c7.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--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