From: Harald Arnesen <skogtun.linux@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [3.9-rc1] very poor interrupt responses
Date: Mon, 11 Mar 2013 11:09:33 +0100 [thread overview]
Message-ID: <513DAD5D.6040905@gmail.com> (raw)
In-Reply-To: <7791757.cgjzv69Ulu@vostro.rjw.lan>
Rafael J. Wysocki [2013-03-11 04:38]:
> On Friday, March 08, 2013 02:12:33 PM Shawn Starr wrote:
>> Hello folks,
>>
>> I am noticing since rc0 and now rc1, very poor interrupt handling. Keyboard response, mouse movements, display refreshing etc. General input/display sluggishness. Did something break IRQ handling somewhere? I need to validate if this happens with X not running also if it is i915 related somehow. The behavor is noticed in a console login however.
>
> Please try to disable the intel_pstate driver by putting intel_pstate=disable
> into the kernel's command line and see if that helps (you may also try to
> compile the driver out).
I see the same problem on my Thinkpad T500, and I have
X86_INTEL_PSTATE=n in my config.
--
Hilsen Harald
next prev parent reply other threads:[~2013-03-11 10:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 19:12 [3.9-rc1] very poor interrupt responses Shawn Starr
2013-03-08 21:33 ` [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) Peter Hurley
2013-03-09 2:19 ` Alan Stern
2013-03-09 8:53 ` Thomas Meyer
2013-03-09 13:07 ` Peter Hurley
2013-03-13 21:35 ` Jiri Kosina
2013-03-14 14:51 ` Alan Stern
2013-03-14 14:56 ` Jiri Kosina
2013-03-14 15:18 ` Alan Stern
2013-03-14 15:39 ` Jiri Kosina
2013-03-14 15:47 ` Jiri Kosina
2013-03-14 16:10 ` Alan Stern
2013-03-14 16:13 ` Alan Stern
2013-03-14 16:09 ` Jiri Kosina
2013-03-14 16:42 ` Peter Hurley
2013-03-14 16:46 ` Rafael J. Wysocki
2013-03-14 17:06 ` Peter Hurley
2013-03-14 17:22 ` Rafael J. Wysocki
2013-03-14 17:26 ` Peter Hurley
2013-03-15 7:59 ` Jiri Kosina
2013-03-15 9:20 ` Harald Arnesen
2013-03-15 13:33 ` Jiri Kosina
2013-03-15 13:33 ` Jiri Kosina
2013-03-15 15:14 ` Jiri Kosina
2013-03-15 19:14 ` Yinghai Lu
2013-03-18 9:12 ` Jiri Kosina
2013-03-18 18:57 ` Yinghai Lu
2013-03-18 22:05 ` Jiri Kosina
2013-03-18 22:50 ` Yinghai Lu
2013-03-18 19:19 ` Daniel Vetter
2013-03-18 19:57 ` Chris Wilson
2013-03-18 22:04 ` Jiri Kosina
2013-03-15 15:32 ` Greg KH
2013-03-15 15:37 ` Jiri Kosina
2013-03-15 15:47 ` Greg KH
2013-03-15 16:21 ` Jiri Kosina
2013-03-18 8:21 ` Daniel Vetter
2013-03-18 15:56 ` [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)) Jiri Kosina
2013-03-18 17:04 ` Chris Wilson
2013-03-19 8:56 ` Jiri Kosina
2013-03-19 9:03 ` Chris Wilson
2013-03-18 19:21 ` Daniel Vetter
2013-03-18 11:13 ` [PATCH] drm/i915: Flush writes to GMBUS registers Chris Wilson
2013-03-18 11:51 ` Jiri Kosina
2013-03-18 12:48 ` Chris Wilson
2013-03-14 18:48 ` [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) Yinghai Lu
2013-03-11 3:38 ` [3.9-rc1] very poor interrupt responses Rafael J. Wysocki
2013-03-11 10:09 ` Harald Arnesen [this message]
2013-03-11 14:55 ` Rafael J. Wysocki
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=513DAD5D.6040905@gmail.com \
--to=skogtun.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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