All of lore.kernel.org
 help / color / mirror / Atom feed
From: m.luescher@vtxmail.ch
To: <linux-rt-users@vger.kernel.org>
Subject: Hard lockup with 2.6.24.7-rt26 on x86
Date: Mon, 2 Feb 2009 21:55:36 +0100	[thread overview]
Message-ID: <37144.1233608136@vtxmail.ch> (raw)

Dear Linux rt users

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

During the test I made some additional observations:
- The lockup is really hard: there is no output on a netconsole and even the magic sysrequest keys to reboot the system (Alt+SysRQ+b) do not work anymore.
- with a lower realtime priority the system seems to run at least more stable (e.g. sudo ./cyclictest -p95 -t10 -n -i250)
- with the vanilla 2.6.26.6-rt11 kernel I observed probably the same crash
- the problem also appears on Ubuntu Hardy Heron with the latest official kernel (2.6.24.23.25 with rt21 patch)
- the problem did not appear on Ubuntu Hardy Heron with older rt-kernel versions (also 2.6.24 but based on rt3 patch)

So at the moment I am really clueless and I would be happy for any hint on how I can further debug this crash.

Best regards
Matthias

             reply	other threads:[~2009-02-02 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 20:55 m.luescher [this message]
2009-02-03 15:00 ` Hard lockup with 2.6.24.7-rt26 on x86 Clark Williams
2009-02-03 15:44   ` Carsten Emde
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=37144.1233608136@vtxmail.ch \
    --to=m.luescher@vtxmail.ch \
    --cc=linux-rt-users@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 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.