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

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

[Andrey Borzenkov]

[-- Attachment #1: Type: Text/Plain, Size: 1711 bytes --]

Even if messages is DEBUG, I assume condition is unusual (otherwise we 
would not need any message in the first place).

This is Dell XPS M1330 with ICH8M:

00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) 
IDE Controller (rev 02)                                                                 
        Subsystem: Dell Device 0209                                            
        Kernel driver in use: ata_piix                                         
        Kernel modules: ata_piix, pata_acpi, ata_generic, piix, ide-pci-
generic
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) 
SATA AHCI Controller (rev 02)                                                         
        Subsystem: Dell Device 0209                                            
        Kernel driver in use: ahci                                             
        Kernel modules: ahci                                                   

Every time I do to sleep I get:

PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
btusb_bulk_complete: hci0 urb ffff88005485d180 failed to resubmit (1)
btusb_bulk_complete: hci0 urb ffff880039086c00 failed to resubmit (1)
btusb_intr_complete: hci0 urb ffff880078556780 failed to resubmit (1)
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.
ata_piix 0000:00:1f.1: PCI INT A disabled
ehci_hcd 0000:00:1d.7: PCI INT A disabled
...

Otherwise there are no negative effects as far as I can tell.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

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

[Andreas Mohr]

Hi,

> Every time I do to sleep I get:
> 
> PM: Entering mem sleep
> Suspending console(s) (use no_console_suspend to debug)
> btusb_bulk_complete: hci0 urb ffff88005485d180 failed to resubmit (1)
> btusb_bulk_complete: hci0 urb ffff880039086c00 failed to resubmit (1)
> btusb_intr_complete: hci0 urb ffff880078556780 failed to resubmit (1)
> 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.
> ata_piix 0000:00:1f.1: PCI INT A disabled
> ehci_hcd 0000:00:1d.7: PCI INT A disabled
> ...
> Otherwise there are no negative effects as far as I can tell.

JFTR, I've seen this as well, on a VT8237 libata system I believe.

Andreas Mohr

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

[Frans Pop]

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

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

[Rafael J. Wysocki]

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