All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Artur Skawina <art.08.09@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Venkatesh Pallipadi <venki@google.com>,
	Damien Wyart <damien.wyart@free.fr>,
	John Drescher <drescherjm@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Fri, 10 Sep 2010 08:42:00 +0100	[thread overview]
Message-ID: <87eid282pj.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <4C8982EF.8030705@gmail.com> (Artur Skawina's message of "Fri, 10 Sep 2010 02:59:27 +0200")

On 10 Sep 2010, Artur Skawina spake thusly:
> I'm seeing this too, except here it happens every couple of days of uptime,
> lasts for a few minutes, and then goes away. Which made bisecting a bit
> impractical... Thank you for doing it. 

I just happened to be the lucky sod for whom it was consistently going
wrong. :)

> HW is similar; x64 and X58/82801JI/ICH10, tsc clocksrc.
> Did that printk trigger?

No.

(hm, odd.

spindle:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc

spindle:~# grep -i tsc /proc/timer_list
spindle:~# grep -i hpet /proc/timer_list
Clock Event Device: hpet
 set_next_event: hpet_legacy_next_event
 set_mode:       hpet_legacy_set_mode

I suspect current_clocksource doesn't do what we think it does, or the
clocksource and 'clock event device' are not the same.)

  parent reply	other threads:[~2010-09-10  7:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05  0:51 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?) Nix
2010-09-06  5:32 ` Damien Wyart
2010-09-06 20:27   ` Nix
2010-09-07  5:36     ` Damien Wyart
2010-09-08 21:24   ` Nix
2010-09-08 21:35     ` John Drescher
2010-09-08 22:25       ` Nix
2010-09-09 22:34     ` [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET) Nix
2010-09-09 23:44       ` John Drescher
2010-09-09 23:57         ` Nix
2010-09-10  0:08           ` John Drescher
2010-09-10  0:14             ` John Drescher
2010-09-10  0:59       ` Artur Skawina
2010-09-10  5:36         ` Damien Wyart
2010-09-10  7:42         ` Nix [this message]
2010-09-10  7:47           ` Damien Wyart
2010-09-10  8:37           ` Thomas Gleixner
2010-09-10  9:41             ` Jiri Slaby
2010-09-10 13:22               ` Artur Skawina
2010-09-10 20:13                 ` Nix
2010-09-10 20:12               ` Nix
2010-09-14 10:09             ` Thomas Gleixner
2010-09-14 20:17               ` Nix
2010-09-14 22:18                 ` Thomas Gleixner
2010-09-14 22:23                 ` Artur Skawina

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=87eid282pj.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=art.08.09@gmail.com \
    --cc=damien.wyart@free.fr \
    --cc=drescherjm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=venki@google.com \
    /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.