From: Artur Skawina <art.08.09@gmail.com>
To: Nix <nix@esperi.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Venkatesh Pallipadi <venki@google.com>,
Damien Wyart <damien.wyart@free.fr>,
John Drescher <drescherjm@gmail.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Wed, 15 Sep 2010 00:23:23 +0200 [thread overview]
Message-ID: <4C8FF5DB.8000207@gmail.com> (raw)
In-Reply-To: <878w34qdu0.fsf@spindle.srvr.nix>
> On 14 Sep 2010, Thomas Gleixner said:
>> Another question. If you add hpet=verbose (or revert that commit) does
>> the printk_once in hpet_set_next_event() show up in dmesg ?
>>
>> "hpet: compare register read back failed."
Since adding back that extra read, the box here, which previously
was showing the symptoms every couple of days, has been ok; so i'm
now ~80% sure this change was indeed the cause. Nothing new in logs.
$ dmesg | grep -i hpet
ACPI: HPET 00000000bfee5dc0 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
ACPI: HPET id: 0x8086a201 base: 0xfed00000
hpet clockevent registered
HPET: 4 timers in total, 0 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
hpet0: 4 comparators, 64-bit 14.318180 MHz counter
rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
$
artur
prev parent reply other threads:[~2010-09-14 22:23 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
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 [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=4C8FF5DB.8000207@gmail.com \
--to=art.08.09@gmail.com \
--cc=damien.wyart@free.fr \
--cc=drescherjm@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
--cc=suresh.b.siddha@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox