Re: ACPI Exception triggered by pata_amd driver in 2.6.24, is this an ACPI bug?

[Thomas Renninger <trenn@suse.de>]

On Wed, 2007-10-24 at 19:00 +0100, Andrew wrote:
> Hi,
> 
> This is probably nothing since there seems to be no ill effects
> but I thought someone should know because...well it bothers me.
> 
> Heres a diff of the kernel boot log between 2.6.23 and 2.6.24:
> 
>  scsi4 : pata_amd
>  scsi5 : pata_amd
> -ata5: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma
> 0x000000000001ffa0 irq 14
> -ata6: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma
> 0x000000000001ffa8 irq 15
> +ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
> +ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
> +ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFF) is beyond end of
> object [20070126]
> +ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.GTM_] (Node
> ffff810002001740), AE_AML_PACKAGE_LIMIT
> +ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1._GTM] (Node
> ffff810002001620), AE_AML_PACKAGE_LIMIT
> +ata6: ACPI get timing mode failed (AE 0x300d)
>  ata6.00: ATAPI: HL-DT-ST DVDRAM GSA-4167B, DL13, max UDMA/33
>  ata6.00: configured for UDMA/33
I doubt the ACPI interpreter broke between those kernels...
Is this the same message as seen when _GTM/_STM were invoked in wrong
order (or the one not invoked at all)?
Tejun might be interested in this one...

Thanks,

   Thomas
> 
> ...and lspci output:
> 
> 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) (prog-if 8a [Master SecP PriP])
>         Subsystem: Unknown device f043:81bc
>         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
> FastB2B- DisINTx-
>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort-
> >SERR- <PERR- INTx-
>         Latency: 0 (750ns min, 250ns max)
>         Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
>         Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
>         Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
>         Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
>         Region 4: I/O ports at ffa0 [size=16]
>         Capabilities: [44] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> So, is it a bug?
> Please CC as I am not subscribed.
>