From: Thomas Gleixner <tglx@linutronix.de>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: Sitsofe Wheeler <sitsofe@yahoo.com>,
Venkatesh Pallipadi <venki@google.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: Interrupt latency on some 945GM platforms
Date: Thu, 16 Sep 2010 20:50:50 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1009162049450.2416@localhost6.localdomain6> (raw)
In-Reply-To: <201009162142.10629.anarsoul@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 892 bytes --]
On Thu, 16 Sep 2010, Vasily Khoruzhick wrote:
> В сообщении от 16 of September 2010 21:30:58 автор Vasily Khoruzhick написал:
> > В сообщении от 16 of September 2010 21:07:39 автор Thomas Gleixner написал:
> > > > Btw, Jesse, any comments/solutions/workarounds except one with
> > > > processor.max_cstate=1 in kernel commandline? Should I file a bug on
> > > > fdo bugzilla?
> > >
> > > we fixed a HPET related bug a few days ago, which might be the cause
> > > for your problem as well.
> >
> > Nope, it doesn't help :(
>
> Btw, I suspect hpet is not related, I disabled hpet completely in kernel
> config but issue is still here (clocksource is acpi_pm)
Ok. The problematic part of HPET was not the clocksource, it was the
clock event device which failed to deliver interrupts occasionally. It
was worth a try at least.
Thanks,
tglx
next prev parent reply other threads:[~2010-09-16 18:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201009132336.17310.anarsoul@gmail.com>
[not found] ` <20100913134441.762001f7@jbarnes-desktop>
[not found] ` <201009140010.14783.anarsoul@gmail.com>
2010-09-13 21:19 ` Jesse Barnes
2010-09-13 21:41 ` Vasily Khoruzhick
2010-09-13 21:46 ` Jesse Barnes
2010-09-13 21:52 ` Vasily Khoruzhick
2010-09-13 21:59 ` Jesse Barnes
2010-09-13 22:03 ` Vasily Khoruzhick
2010-09-14 0:55 ` Venkatesh Pallipadi
2010-09-14 8:09 ` Vasily Khoruzhick
2010-09-14 9:52 ` Thomas Gleixner
2010-09-14 12:29 ` Vasily Khoruzhick
2010-09-14 22:41 ` Sitsofe Wheeler
2010-09-15 7:07 ` Vasily Khoruzhick
2010-09-16 15:03 ` Vasily Khoruzhick
2010-09-16 18:07 ` Thomas Gleixner
2010-09-16 18:30 ` Vasily Khoruzhick
2010-09-16 18:42 ` Vasily Khoruzhick
2010-09-16 18:50 ` Thomas Gleixner [this message]
2010-09-16 20:06 ` Vasily Khoruzhick
2010-09-24 19:39 ` Jesse Barnes
2010-09-24 19:48 ` Vasily Khoruzhick
2010-09-24 19:51 ` Jesse Barnes
2010-09-26 10:53 ` Stefan Biereigel
2010-09-27 0:46 ` Shaohua Li
2010-09-27 5:45 ` Stefan Biereigel
2010-09-27 11:41 ` Vasily Khoruzhick
2010-09-27 21:18 ` Vasily Khoruzhick
2010-09-25 10:25 ` Paolo Ornati
2010-09-17 9:02 ` [Intel-gfx] " Simon Farnsworth
2010-09-17 16:30 ` Jesse Barnes
2010-09-17 12:50 ` Vasily Khoruzhick
2010-09-21 18:26 ` Paolo Ornati
2010-09-21 22:56 ` Jesse Barnes
2010-09-22 5:57 ` Vasily Khoruzhick
2010-09-23 18:21 ` Paolo Ornati
2010-09-25 10:28 ` Paolo Ornati
2010-10-16 15:54 ` [Intel-gfx] Interrupt latency on some 945GM platforms -- and TCP/IP silent data corruption? Paolo Ornati
2010-09-24 18:41 ` Interrupt latency on some 945GM platforms Jesse Barnes
2010-09-14 9:55 ` Andi Kleen
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=alpine.LFD.2.00.1009162049450.2416@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=anarsoul@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
--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
all inboxes | Powered by JetHome®