From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: john stultz <johnstul@us.ibm.com>
Cc: Greg Schafer <gschafer@zip.com.au>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>
Subject: Re: 2.6.18 Nasty Lockup
Date: Sat, 7 Oct 2006 18:48:25 +0300 [thread overview]
Message-ID: <200610071848.25904.caglar@pardus.org.tr> (raw)
In-Reply-To: <1160175452.6140.45.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
07 Eki 2006 Cts 01:57 tarihinde, john stultz şunları yazmıştı:
> Hey S.Çağlar,
>
> So I just wrote up this test case that will show how skewed the TSCs
> are. I'd be interested if you could run it a few times quickly after a
> fresh boot, and then again a day or so later.
>
> See the header comment for instructions.
>
> And just a fair warning: this runs w/ SCHED_FIFO, and thus has the
> potential to hang your system (while writing it I made a few flubs and
> it hung my system). I believe I've got all of the issues fixed (tested
> on a few systems), but wanted to give you a fair warning before I
> suggest you run this. :)
Ok ill try this on Monday, thanks!
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-10-07 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:36 2.6.18 Nasty Lockup Greg Schafer
2006-09-26 13:56 ` Michael Obster
2006-09-26 15:41 ` Ben Duncan
2006-09-26 18:18 ` john stultz
2006-09-26 20:15 ` john stultz
2006-09-26 22:02 ` Greg Schafer
2006-09-26 22:58 ` john stultz
2006-09-26 21:15 ` S.Çağlar Onur
2006-09-26 22:50 ` john stultz
2006-09-27 9:45 ` S.Çağlar Onur
2006-09-27 19:14 ` john stultz
2006-09-27 20:55 ` Andi Kleen
2006-09-27 21:06 ` S.Çağlar Onur
2006-09-28 11:39 ` S.Çağlar Onur
2006-09-29 8:49 ` S.Çağlar Onur
2006-10-06 22:57 ` john stultz
2006-10-07 15:48 ` S.Çağlar Onur [this message]
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=200610071848.25904.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ak@muc.de \
--cc=gschafer@zip.com.au \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@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.