From: Wes Janzen <superchkn@sbcglobal.net>
To: Mike Galbraith <efault@gmx.de>
Cc: Con Kolivas <kernel@kolivas.org>, Voluspa <lista1@comhem.se>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] O17int
Date: Fri, 22 Aug 2003 15:48:01 -0500 [thread overview]
Message-ID: <3F468181.5020605@sbcglobal.net> (raw)
In-Reply-To: <5.2.1.1.2.20030822072356.01a22be0@pop.gmx.net>
Yep, those are very bad stalls, much worse than the normal temporary
stalls when something is running in the background. I think part of
that can be attributed to mozilla, which likes to do very little for a
while, then jump up to 5% for a little bit and then up to 35% for 5
seconds or so.
With something running in the background, things get very bad. Those
vmstat were supposed to be reported at 5 second intervals, but they were
not being reported at the rate during the problem. Those represent
about 5 minutes of stalling. I could live with a short stall, but 5
minutes where the computer barely takes input is crazy. X becomes
totally unresponsive to the point I cannot switch to a VT.
I started a shutdown one time with the acipd daemon watching for power
button events. It took 1 hour 30 minutes from the time it said that it
was shutting down (I could hear the beep from the shutdown process) to
the point I got to "Stopping at daemon" which is barely into the
shutdown cycle. Even then I waited another 10 minutes for it to
complete the shutdown and it never did. All I was doing there was
compiling in a gnome-terminal, and had just clicked on a bug-buddy
window to get it to show debugging information. I couldn't get to a VT
so I wasn't able to get a vmstat log of that one.
Even if this is due to a bad interaction between a program and X, it
shouldn't be able to bring the system to its knees.
Kernel version:
2.6.0-test3-mm2 + O16.3int
Mike Galbraith wrote:
>
> Those high interrupt counts are all stalls? What kernel is that?
>
next prev parent reply other threads:[~2003-08-22 20:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 15:01 [PATCH] O17int Con Kolivas
2003-08-19 16:39 ` Måns Rullgård
2003-08-20 1:23 ` Con Kolivas
2003-08-20 9:19 ` Måns Rullgård
2003-08-19 18:58 ` Måns Rullgård
2003-08-20 1:19 ` Con Kolivas
2003-08-20 8:53 ` Måns Rullgård
2003-08-20 16:27 ` Wiktor Wodecki
2003-08-20 16:42 ` Nick Piggin
2003-08-20 21:23 ` Con Kolivas
2003-08-21 5:26 ` Con Kolivas
2003-08-21 7:53 ` Mike Galbraith
2003-08-21 11:46 ` Con Kolivas
2003-08-21 15:14 ` Mike Galbraith
2003-08-21 22:18 ` Wes Janzen
2003-08-22 0:09 ` Con Kolivas
2003-08-22 21:17 ` Wes Janzen
2003-08-22 0:42 ` Felipe Alfaro Solana
2003-08-22 5:34 ` Mike Galbraith
2003-08-22 20:48 ` Wes Janzen [this message]
2003-08-21 23:59 ` Con Kolivas
2003-08-22 5:11 ` Mike Galbraith
2003-08-21 5:30 ` Apurva Mehta
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 4:55 Voluspa
2003-08-20 8:00 ` Mike Galbraith
2003-08-20 11:21 ` Con Kolivas
2003-08-20 22:51 Voluspa
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=3F468181.5020605@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@comhem.se \
/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