public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: mru@users.sourceforge.net (Måns Rullgård), linux-kernel@vger.kernel.org
Subject: Re: [BUG]  Serious scheduler starvation
Date: Sun, 17 Aug 2003 22:52:52 +1000	[thread overview]
Message-ID: <200308172252.52464.kernel@kolivas.org> (raw)
In-Reply-To: <yw1xekzkv5yv.fsf@users.sourceforge.net>

On Sun, 17 Aug 2003 22:11, Måns Rullgård wrote:
> I'm reposting this, since I got no response last time.
>
> First the machine details.  It's a Pentium4 running at 2 GHz.  Linux
> version 2.6.0-test3 + O16int + softrr.

Softrr ? Which patch? Davide's? Noone has tried to make them compatible 
(yet?). Even so, this may be unrelated to softrr.

> I just experienced something that might be a scheduler problem.  I was

Almost certainly is.

> 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?

Run top in batch mode as root reniced to -11 so it doesn't get preempted and 
capture it happening before you kill XEmacs. Then try running XEmacs niced 
+10 and see if it doesn't happen there. Also if it was lucky enough that you 
booted with profiling enabled you could profile it, but top will tell if it's 
a simple scheduler starvation error. 

Con


  reply	other threads:[~2003-08-17 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 12:11 [BUG] Serious scheduler starvation Måns Rullgård
2003-08-17 12:52 ` Con Kolivas [this message]
2003-08-17 13:17   ` Måns Rullgård
2003-08-17 13:43   ` Daniel Phillips
2003-08-17 13:49     ` Con Kolivas
2003-08-17 12:55 ` Daniel Phillips

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=200308172252.52464.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@users.sourceforge.net \
    /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