linux-kernel - Re: 2.6.31-rc6: ACPI handle has no context apparenty from libata during suspend to RAM

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200908231407.38543.elendil@planet.nl>
Date:	Sun, 23 Aug 2009 14:07:37 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
Cc:	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

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.

Cheers,
FJP
--
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/