Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964813Ab3CNQmm (ORCPT ); Thu, 14 Mar 2013 12:42:42 -0400 Received: from mailout01.c08.mtsvc.net ([205.186.168.189]:51898 "EHLO mailout01.c08.mtsvc.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932487Ab3CNQmk (ORCPT ); Thu, 14 Mar 2013 12:42:40 -0400 Message-ID: <1363279329.7443.10.camel@thor.lan> Subject: Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses) From: Peter Hurley To: Jiri Kosina Cc: Alan Stern , Thomas Meyer , Shawn Starr , Kernel development list , USB list , linux-acpi@vger.kernel.org, "Rafael J. Wysocki" , Bjorn Helgaas , linux-pci@vger.kernel.org Date: Thu, 14 Mar 2013 12:42:09 -0400 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.3-0pjh1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Authenticated-User: 125194 peter@hurleysoftware.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1443 Lines: 38 On Thu, 2013-03-14 at 17:09 +0100, 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. When I had this happen on -next, it was PCI + ACPI-related and I had to bisect it. But for me the problem was quite noticable and showed up right at login prompt. Regards, Peter Hurley PS - I already confirmed that the commit that fixes that is in 3.9-rc1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/