linux-kernel - Re: pci 0000:0a:00.0: Refused to change power state, currently in D3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201105192335.22414.rjw@sisk.pl>
Date:	Thu, 19 May 2011 23:35:22 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Mikko Vinni <mmvinni@...oo.com>
Cc:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux PM mailing list <linux-pm@...ts.linux-foundation.org>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: pci 0000:0a:00.0: Refused to change power state, currently in D3

On Sunday, May 15, 2011, Mikko Vinni wrote:
> From: Rafael J. Wysocki:
> 
> >>  in an HP Pavilion dv5 laptop model dv5-1250eo always at resume
> >>  from s2ram the following messages are printed:
> >> 
> >>  pci 0000:0a:00.0: Refused to change power state, currently in D3
> >>  pci 0000:0a:00.1: Refused to change power state, currently in D3
> >>  pci 0000:0a:00.2: Refused to change power state, currently in D3
> >>  pci 0000:0a:00.3: Refused to change power state, currently in D3
> >>  pci 0000:0a:00.4: Refused to change power state, currently in D3
> > 
> > The lspci output indicates that this is a single multi-function
> > device that doesn't change its power state when programmed to go
> > into D0.  Perhaps it requires a power resource that is not available
> > at the point we're trying to restore those devices' registers.
> > 
> > Hard to say what that may be, though.  Please attach the output of
> > acpidump from the affected system.
> 
> Here it goes. Hopefully it contains the necessary parts and is not
> too big for the lists (produced without any parameters to acpidump):

Thanks.  Unfortunately, I didn't have the time to look into it.

Could you please go to https://bugzilla.kernel.org/show_bug.cgi?id=35452
and attach the acpidump output?

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/