On Mon, 23 Sep 2013, Bjorn Helgaas wrote:
> d010e5769 ("PCI / ACPI: Use dev_dbg() instead of dev_info() in
> acpi_pci_set_power_state()") might be part of the solution. That was
> done in response to https://bugzilla.kernel.org/show_bug.cgi?id=60636,
> which looks basically the same as your compl
On Monday, September 23, 2013 04:28:49 PM Bjorn Helgaas wrote:
> [+cc Rafael, linux-pm]
>
> On Mon, Sep 23, 2013 at 1:36 PM, Alan Stern wrote:
> > On Mon, 23 Sep 2013, Andy Lutomirski wrote:
> >
> >> I've been getting this on several recent kernel revisions. Is it
> >> interesting? If so, I'm h
[+cc Rafael, linux-pm]
On Mon, Sep 23, 2013 at 1:36 PM, Alan Stern wrote:
> On Mon, 23 Sep 2013, Andy Lutomirski wrote:
>
>> I've been getting this on several recent kernel revisions. Is it
>> interesting? If so, I'm happy to help diagnose it. If not, can the
>> message be killed or severely r
On Mon, 23 Sep 2013, Andy Lutomirski wrote:
> I've been getting this on several recent kernel revisions. Is it
> interesting? If so, I'm happy to help diagnose it. If not, can the
> message be killed or severely ratelimited? I'm getting so much of
> this that it tends to overflow the log ring.
I've been getting this on several recent kernel revisions. Is it
interesting? If so, I'm happy to help diagnose it. If not, can the
message be killed or severely ratelimited? I'm getting so much of
this that it tends to overflow the log ring.
[ 287.344991] ehci-pci :00:1d.0: power state c
