From: Ingo Molnar <mingo@elte.hu>
To: Mark_H_Johnson@Raytheon.com
Cc: Karsten Wiese <annabellesgarden@yahoo.de>,
Bill Huey <bhuey@lnxw.com>, Adam Heath <doogie@debian.org>,
"K.R. Foley" <kr@cybsft.com>,
linux-kernel@vger.kernel.org,
Florian Schmidt <mista.tapas@gmx.net>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Lee Revell <rlrevell@joe-job.com>,
Rui Nuno Capela <rncbc@rncbc.org>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4
Date: Thu, 28 Oct 2004 09:03:57 +0200 [thread overview]
Message-ID: <20041028070357.GC10488@elte.hu> (raw)
In-Reply-To: <OF45330B99.149A2C07-ON86256F3A.00757C16@raytheon.com>
* Mark_H_Johnson@Raytheon.com <Mark_H_Johnson@Raytheon.com> wrote:
> I am aware of slow responses normally during tests. However the audio
> test should only use one CPU out of two. The other CPU is busy as well
> with a cpu burner (nice 10) but that should leave me CPU cycles to
> move the mouse, swap windows, etc. The "lock up" I saw this time was
> a lot more severe (no mouse motion for several minutes at a time). I
> knew the system was still running since the audio continued to play.
the way i typically debug such scenarios is to set up a separate
'highprio console' of some sorts. E.g. log in via the network from
another box and make sure all processing of that console is SCHED_FIFO.
(in the network case that would mean the network IRQ, ksoftirqd, sshd,
login and bash.) Such a 'highprio console' should have a higher priority
than any other task in the system. If you run alot of stuff in it then
it will surely disturb your measurements (and largely invalidate them),
but otherwise it can be useful to have it around just in case you
experience a lockup that you suspect to be some sort of livelock or
starvation. Whenever the lockup happens, check out what's going on, via
the highprio console.
another useful 'highprio console' is the text console itself - in this
case only login and bash has to be chrt-ed, and the runtime impact on
the test is smaller as well. This is only useful if you can start your
'bad' workload over ssh or via networked X.
Ingo
next prev parent reply other threads:[~2004-10-28 7:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 21:30 [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4 Mark_H_Johnson
2004-10-28 7:03 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 21:48 Remi Colinet
2004-10-27 16:12 Mark_H_Johnson
2004-10-27 21:04 ` Ingo Molnar
2004-10-18 14:50 [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U5 Ingo Molnar
2004-10-19 12:46 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U6 Ingo Molnar
2004-10-19 18:00 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U7 Ingo Molnar
2004-10-20 9:45 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U8 Ingo Molnar
2004-10-21 13:27 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U9 Ingo Molnar
2004-10-22 13:35 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U9.3 Ingo Molnar
2004-10-22 15:50 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-U10 Ingo Molnar
2004-10-22 17:56 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-U10.2 Ingo Molnar
2004-10-25 10:40 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0 Ingo Molnar
2004-10-27 0:15 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.3 Ingo Molnar
2004-10-27 12:43 ` Rui Nuno Capela
2004-10-27 13:53 ` Ingo Molnar
2004-10-27 15:26 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4 Rui Nuno Capela
2004-10-27 15:30 ` Lee Revell
2004-10-27 17:39 ` Rui Nuno Capela
2004-10-27 18:57 ` karsten wiese
2004-10-27 20:28 ` Rui Nuno Capela
2004-10-27 18:59 ` karsten wiese
2004-10-27 20:01 ` Ingo Molnar
2004-10-27 20:51 ` Ingo Molnar
2004-10-27 21:19 ` Ingo Molnar
2004-10-27 23:31 ` Rui Nuno Capela
2004-10-28 6:36 ` Ingo Molnar
2004-10-28 8:31 ` Rui Nuno Capela
2004-10-28 8:56 ` Ingo Molnar
2004-10-28 9:17 ` Rui Nuno Capela
2004-10-28 9:32 ` Ingo Molnar
2004-10-28 16:33 ` Rui Nuno Capela
2004-10-28 19:16 ` Ingo Molnar
2004-10-28 23:49 ` Rui Nuno Capela
2004-10-29 0:07 ` Lee Revell
2004-10-29 7:30 ` Ingo Molnar
2004-10-29 15:00 ` Rui Nuno Capela
2004-10-29 17:57 ` Lee Revell
2004-10-29 14:31 ` Florian Schmidt
2004-10-29 14:25 ` Ingo Molnar
2004-10-29 15:09 ` Florian Schmidt
2004-10-29 14:53 ` Florian Schmidt
2004-10-30 3:09 ` Lee Revell
2004-10-30 3:22 ` Joe
2004-10-27 13:03 ` Ingo Molnar
2004-10-27 21:41 ` Magnus Naeslund(t)
2004-10-28 6:55 ` Ingo Molnar
2004-10-28 9:31 ` Magnus Naeslund(t)
2004-10-28 6:58 ` Ingo Molnar
2004-10-28 14:14 ` K.R. Foley
2004-10-28 14:20 ` Ingo Molnar
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=20041028070357.GC10488@elte.hu \
--to=mingo@elte.hu \
--cc=Mark_H_Johnson@Raytheon.com \
--cc=annabellesgarden@yahoo.de \
--cc=bhuey@lnxw.com \
--cc=doogie@debian.org \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=nando@ccrma.Stanford.EDU \
--cc=rlrevell@joe-job.com \
--cc=rncbc@rncbc.org \
--cc=tglx@linutronix.de \
--cc=xschmi00@stud.feec.vutbr.cz \
/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;
as well as URLs for NNTP newsgroup(s).