public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: time warp on 2.6.18-rt6 (2nd try)
Date: Fri, 20 Oct 2006 13:29:32 -0500	[thread overview]
Message-ID: <4539158C.2090801@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ingo,

I sent this yesterday morning and haven't seen it show up. I wonder if
my attached configs/logs were too large? Now referenced as URLs...

I'm still seeing the time warp ("It's just a jump to the left!" :))*
being triggered on both my Athlon64x2 (32-bit kernel) and my Athlon64 up
box (64-bit kernel). A boot log that shows the failure and the config
files for both systems can be found at:

http://people.redhat.com/williams/rt

To trigger this, I was running pi_stress test from:

http://people.redhat.com/williams/tests/pi_tests-1.3.tar.gz

I was running it like this:

$ sudo pi_stress --verbose

Note: Be aware that I still haven't got pi_stress to stop reliably.
It will catch SIGINT sometimes and sometimes it just blithely ignores it
and sails on. Since in the default run there are ten groups of three
threads all running SCHED_FIFO and performing a priority inversion
scenario, this will mean a uniprocessor box will be almost unusable for
other tasks. On my SMP box I can ssh into the box and kill the test with
"kill <pid>".

Let me know if you need me to reconfigure and try something else.

Clark

* lame "Rocky Horror Picture Show" reference

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFFORWMHyuj/+TTEp0RAq8QAJ9t30GOTjRmKD0Tkif94wQVyOyRTQCfbmX7
Qm3mAzmnnH8KDqpP2hoDwSE=
=kkAj
-----END PGP SIGNATURE-----

             reply	other threads:[~2006-10-20 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:29 Clark Williams [this message]
2006-10-20 21:08 ` time warp on 2.6.18-rt6 (2nd try) Ingo Molnar
2006-10-23 16:21   ` Clark Williams

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=4539158C.2090801@redhat.com \
    --to=williams@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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