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: <200908232058.32917.rjw@sisk.pl>
Date:	Sun, 23 Aug 2009 20:58:32 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Frans Pop <elendil@...net.nl>
Cc:	Andrey Borzenkov <arvidjaar@...l.ru>, linux-ide@...r.kernel.org,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.31-rc6: ACPI handle has no context apparenty from libata during suspend to RAM

On Sunday 23 August 2009, Frans Pop wrote:
> Andrey Borzenkov wrote:
> > sd 0:0:0:0: [sda] Synchronizing SCSI cache
> > sd 0:0:0:0: [sda] Stopping disk
> > ACPI handle has no context!
> > sdhci-pci 0000:03:01.1: PME# disabled
> > sdhci-pci 0000:03:01.1: PCI INT B disabled
> > ACPI handle has no context!
> > ata5: port disabled. ignoring.
> 
> I have a few of those too. I've been intending to try to investigate them, 
> but haven't gotten around to it yet. One problem is that there is no 
> context information in the error message itself (what 
> driver/function/whatever).
> 
> Are they new for you in .31 or have they always been there? I suspect the 
> latter, in which case I wouldn't worry about them too much. I at least 
> have never noticed any actual negative impact from them.

Most likely, the messages are from acpi_pm_device_sleep_state(), which on some
buses (PCI for one example) is called for all devices regardless of whether or
not they have the corresponding ACPI devices.  If they don't, this message is
printed and it's a KERN_DEBUG message.  It's totally harmless.

Thanks,
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ