public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc6-rt5
Date: Thu, 23 Nov 2006 22:11:35 +0100	[thread overview]
Message-ID: <20061123211135.GY18636@pengutronix.de> (raw)
In-Reply-To: <a0580c510611231243x318f3cbanc8fa2cbbedcec060@mail.gmail.com>

Eduardo,

On Thu, Nov 23, 2006 at 04:43:01PM -0400, Eduardo Valentin wrote:
> However, I got a similar problem as reported by Robert:
> 
> 2.6.19-rc6:
> T: 0 ( 4861) P:80 I:   10000 C:   10000 Min:    2592 Act:    4878 Avg:   6137 Max:   10652
> 2.6.19-rc6-rt5:
> T: 0 ( 3661) P:80 I:   10000 C:   10000 Min:     828 Act:    1698 Avg:   3291 Max:    7171
>
> These results are quite different from what is reported at the wiki.

Is this with -r or without? I didn't get fixed maxima at all on the
celeron box. It also looks like you've changed the interval time to
10ms; nevertheless: a delay of > 10 ms @ a cylce time of 10 ms means
missing the deadlines.

Do you have the possibility to switch off the SMI for your chipset? As
tglx noted on irc recently this may be dangerous because thermal
throtteling can be implemented via SMI, but to get an idea if the SMI is
the reason for the delays, switching it off for a short time should do
the job.

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9


  reply	other threads:[~2006-11-23 21:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 22:02 2.6.19-rc6-rt5 Ingo Molnar
2006-11-20 22:39 ` 2.6.19-rc6-rt5 Alistair John Strachan
2006-11-21  7:17   ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-20 23:18 ` 2.6.19-rc6-rt5 Alistair John Strachan
2006-11-21  7:20   ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-21  1:35 ` 2.6.19-rc6-rt5 Sergio Monteiro Basto
2006-11-21  8:04   ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-21  3:07 ` compile problems 2.6.19-rc6-rt5 Sergio Monteiro Basto
2006-11-21  7:43   ` Ingo Molnar
2006-11-21  7:54   ` Ingo Molnar
2006-11-22 11:37 ` 2.6.19-rc6-rt5 Robert Schwebel
2006-11-23 20:43   ` 2.6.19-rc6-rt5 Eduardo Valentin
2006-11-23 21:11     ` Robert Schwebel [this message]
2006-11-22 14:06 ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-28 17:33   ` 2.6.19-rc6-rt5 Lee Revell
2006-11-28 19:53     ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-28 20:16       ` 2.6.19-rc6-rt5 Lee Revell
2006-11-28 20:15     ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-28 22:52       ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-29  6:54         ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-26 14:39 ` 2.6.19-rc6-rt5 Karsten Wiese
2006-11-27  7:48   ` 2.6.19-rc6-rt5 Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2006-11-21 12:01 2.6.19-rc6-rt5 Marcus Hartig
2006-11-21 12:45 ` 2.6.19-rc6-rt5 Karsten Wiese
2006-11-25 22:01 2.6.19-rc6-rt5 Thomas

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=20061123211135.GY18636@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=edubezval@gmail.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