From: Peter Hurley <peter@hurleysoftware.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jiri Kosina <jkosina@suse.cz>,
Alan Stern <stern@rowland.harvard.edu>,
Thomas Meyer <thomas@m3y3r.de>,
Shawn Starr <shawn.starr@rogers.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
linux-acpi@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)
Date: Thu, 14 Mar 2013 13:06:04 -0400 [thread overview]
Message-ID: <1363280764.26318.4.camel@thor.lan> (raw)
In-Reply-To: <1460519.ejNFI1DrGk@vostro.rjw.lan>
On Thu, 2013-03-14 at 17:46 +0100, Rafael J. Wysocki wrote:
> On Thursday, March 14, 2013 05:09:59 PM Jiri Kosina wrote:
> > On Thu, 14 Mar 2013, Jiri Kosina wrote:
> >
> > > > > I don't think I have seen this message on rc1+ (8343bce, to be precise),
> > > > > but I have definitely seen sluggish system response on that kernel as
> > > > > well.
> > > > >
> > > > > Attaching lspci, /proc/interrupts and dmesg.
> > > >
> > > > Can you try to do a git bisect for this? Is the sluggish system
> > > > response clear enough that you can tell reliably when it is present and
> > > > when it isn't?
> > >
> > > That was my first thought, but unfortunately I am afraid there will be
> > > point at which I will easily make a bisection mistake, as the
> > > responsiveness of the system varies over time, so it's not really a
> > > 100% objective measure.
> >
> > So I will try a bisect, but it'll take some time so that I could claim it
> > to be trustworthy.
> >
> > Therefore in case anyone has any idea in parallel, I am all ears.
>
> This one is a candidate to focus on I think:
>
> commit 181380b702eee1a9aca51354d7b87c7b08541fcf
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Sat Feb 16 11:58:34 2013 -0700
>
> PCI/ACPI: Don't cache _PRT, and don't associate them with bus numbers
This patch __fixed__ this problem for me in linux-next back in February.
Rafael, did you hold back some ACPI patches from 3.9 that would have
made fix no longer applicable?
next prev parent reply other threads:[~2013-03-14 17:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1303082116310.28403-100000@netrider.rowland.org>
[not found] ` <1362819234.1220.1.camel@localhost.localdomain>
2013-03-09 13:07 ` [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) 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 [this message]
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 2:41 ` Shawn Starr
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
[not found] ` <alpine.LNX.2.00.1303181010080.9529-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
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-14 18:48 ` [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) Yinghai Lu
2013-03-18 7:14 Thomas Meyer
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=1363280764.26318.4.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=bhelgaas@google.com \
--cc=jkosina@suse.cz \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shawn.starr@rogers.com \
--cc=stern@rowland.harvard.edu \
--cc=thomas@m3y3r.de \
--cc=yinghai@kernel.org \
/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