All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <Carsten.Emde@osadl.org>
To: Clark Williams <williams@redhat.com>
Cc: m.luescher@vtxmail.ch, linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Hard lockup with 2.6.24.7-rt26 on x86
Date: Tue, 03 Feb 2009 16:44:10 +0100	[thread overview]
Message-ID: <4988664A.3080601@osadl.org> (raw)
In-Reply-To: <20090203090052.6a4dc4de@torg>

Clark,

>> On two different desktop PC (both Core 2 Duo) and on a notebook
>> (Core Duo) the kernel (2.6.24.7-rt26, CONFIG_X86_32) locks up hard
>> under a certain rt load. The failure can be reproduced reliably
>> with the following command:
>> sudo ./cyclictest -p99 -t10 -n -i250
> My guess would be that since you're running 10 threads on two 
> processors at the highest available priority, you're starving all the
> hard IRQ threads (as well as soft irq and other kernel threads).
> This is one of those power-tool moments where you can lock up the 
> system with the wrong workload/priority combination.
Hmm, I would agree immediately, if the tasks were using all of the CPU
power. But this is not the case. In the present case, running

# cyclictest -p99 -t10 -n -i250

results in about 10% CPU load. So there is plenty of time in between to
let the system respond. I can reproduce the problem here (2.6.24-rt,
2.6.26-rt, various configurations). The system does not crash every time
when cyclictest is started, only once in about 5 trials or so. If it
crashes, then it does so immediately after being started. Whenever
cyclictest survives for several seconds, then it never crashes at a
later time. I tend to believe that we have a bug here, not a regular
behavior.

	Carsten.

  reply	other threads:[~2009-02-03 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 20:55 Hard lockup with 2.6.24.7-rt26 on x86 m.luescher
2009-02-03 15:00 ` Clark Williams
2009-02-03 15:44   ` Carsten Emde [this message]
2009-02-03 16:26     ` Clark Williams
2009-02-03 19:20 ` Remy Bohmer
     [not found]   ` <902d99b50902040046u3257591fxe29cef4e62315b1a@mail.gmail.com>
2009-02-04 11:56     ` Remy Bohmer
2009-02-04 12:31       ` Claus Gindhart

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=4988664A.3080601@osadl.org \
    --to=carsten.emde@osadl.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=m.luescher@vtxmail.ch \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.