public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Thomas Gleixner <tglx@linutronix.de>,
	Arjan van de Ven <arjan@infradead.org>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Marcin Slusarz <marcin.slusarz@gmail.com>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	corsac@debian.org
Subject: [2.6.28-rc5] TSC sync error and high hrtimer_start (was: Bootup time regression from 2.6.27 to 2.6.28-rc3+)
Date: Sun, 16 Nov 2008 20:27:43 +0100	[thread overview]
Message-ID: <200811162027.44988.elendil@planet.nl> (raw)
In-Reply-To: <200811140245.40505.elendil@planet.nl>

On Friday 14 November 2008, Frans Pop wrote:
> Could either of you maybe give a status update on this patch set and
> the remaining issues with it that were reported (especially the high C0
> reported by powertop)?

My previous tests were on my laptop. This is for my desktop running -rc5.
I had not tested my desktop with earlier .28 releases.

For .28 powertop prominently shows hrtimer_start (tick_sched_timer) which
was not present for .27. The list below that is virtually identical to .27.

Total wakeups for .28 is lower though. Something to look into or not?

Possibly this may be related to this diff in the boot messages:
-checking TSC synchronization [CPU#0 -> CPU#1]: passed.
+checking TSC synchronization [CPU#0 -> CPU#1]:
+Measured 696 cycles TSC warp between CPUs, turning off TSC clock.
+Marking TSC unstable due to check_tsc_sync_source failed

With .27.4 TSC _always_ passed. Now, with .28-rc5 I get this warp. I've
done two boots so far, for the other one the warp was 680 cycles.

Cheers,
FJP

Powertop output for idle system:
*** 2.6.27.4 ***
Wakeups-from-idle per second : 68.7     interval: 10.0s
no ACPI power usage estimate available

Top causes for wakeups:
  31.5% ( 17.8)     <kernel core> : __mod_timer (neigh_periodic_timer)
  14.5% (  8.2)   <kernel module> : mod_timer (rh_timer_func)
  11.3% (  6.4)             artsd : __mod_timer (process_timeout)
   9.2% (  5.2)        ksysguardd : __mod_timer (process_timeout)
   4.2% (  2.4)            kicker : __mod_timer (process_timeout)
   3.5% (  2.0)     <kernel core> : add_timer_on (clocksource_watchdog)

*** 2.6.28-rc5 ***
Wakeups-from-idle per second : 55.6     interval: 10.0s
no ACPI power usage estimate available

Top causes for wakeups:
  28.5% ( 23.4)     <kernel core> : hrtimer_start (tick_sched_timer)
  21.7% ( 17.8)     <kernel core> : __mod_timer (neigh_periodic_timer)
   9.7% (  8.0)   <kernel module> : mod_timer (rh_timer_func)
   7.8% (  6.4)             artsd : schedule_hrtimeout_range (hrtimer_wakeup)
   5.4% (  4.4)        ksysguardd : __mod_timer (process_timeout)
   2.8% (  2.3)            kicker : schedule_hrtimeout_range (hrtimer_wakeup)
   2.4% (  2.0)     <kernel core> : add_timer_on (clocksource_watchdog)

  parent reply	other threads:[~2008-11-16 19:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 17:33 Bootup time regression from 2.6.27 to 2.6.28-rc3+ Lukas Hejtmanek
2008-11-09  0:06 ` Rafael J. Wysocki
2008-11-09  4:55   ` Arjan van de Ven
2008-11-09  8:56     ` Lukas Hejtmanek
2008-11-09 10:52       ` Marcin Slusarz
2008-11-09 11:33         ` Lukas Hejtmanek
2008-11-09 13:24           ` Rafael J. Wysocki
2008-11-09 20:09             ` Lukas Hejtmanek
2008-11-09 20:28               ` Arjan van de Ven
2008-11-09 20:34                 ` Lukas Hejtmanek
2008-11-09 21:24                   ` Arjan van de Ven
2008-11-09 21:38                     ` Lukas Hejtmanek
2008-11-09 21:43                     ` Lukas Hejtmanek
2008-11-09 21:57                       ` Thomas Gleixner
2008-11-10  8:12                         ` Lukas Hejtmanek
2008-11-10 12:16                         ` Lukas Hejtmanek
2008-11-09 21:56                     ` Thomas Gleixner
2008-11-09 22:46                       ` Bernhard Schmidt
2008-11-09 22:53                       ` Frans Pop
2008-11-14  1:45                       ` Frans Pop
2008-11-15 17:16                         ` Frans Pop
2008-11-15 18:04                           ` Arjan van de Ven
2008-11-16 19:27                         ` Frans Pop [this message]
2008-11-17  2:18                           ` [2.6.28-rc5] TSC sync error and high hrtimer_start (was: Bootup time regression from 2.6.27 to 2.6.28-rc3+) Frans Pop
2008-11-10 13:45                     ` Bootup time regression from 2.6.27 to 2.6.28-rc3+ Yves-Alexis Perez
2008-11-11 17:33                       ` Len Brown
2008-11-09 20:39                 ` Linus Torvalds
2008-11-09 20:48                   ` Arjan van de Ven
2008-11-09 14:20       ` Frans Pop
2008-11-09 15:14         ` Lukas Hejtmanek

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=200811162027.44988.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=arjan@infradead.org \
    --cc=corsac@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xhejtman@ics.muni.cz \
    /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