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-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
