RE: ACPI errors

RE: ACPI errors

[Yu, Luming]

Sure, Please open a bug at bugzilla.kernel.org.
Please post acpidump output, and dmesg.

Thanks,
Luming

>I get a lot of these errors in dmesg:
>
> ACPI-0339: *** Error: Looking up [\_TZ_.THRM] in namespace,
>AE_NOT_FOUND
>search_node dfff7800 start_node dfff7800 return_node 00000000
>    ACPI-0508: *** Error: Method execution failed [\_GPE._L1C] (Node
>dfff7800), AE_NOT_FOUND
>    ACPI-0549: *** Error: AE_NOT_FOUND while evaluating method [_L1C]
>for GPE[ 0]
>
>This happens with 2.6.14 and 2.6.16 kernels
>
>
>Can you help me?
>
>

Re: ACPI errors

[Emiliano Grilli]

lunedì, 05 giugno 2006 alle 20:49:44, Yu, Luming ha scritto:
> 
> Sure, Please open a bug at bugzilla.kernel.org.
> Please post acpidump output, and dmesg.


Done.

Bug number is 6649:
http://bugzilla.kernel.org/show_bug.cgi?id=6649

 
> Thanks,

Thanks to you :)

> Luming
> 
> >I get a lot of these errors in dmesg:
> >
> > ACPI-0339: *** Error: Looking up [\_TZ_.THRM] in namespace,
> >AE_NOT_FOUND
> >search_node dfff7800 start_node dfff7800 return_node 00000000
> >    ACPI-0508: *** Error: Method execution failed [\_GPE._L1C] (Node
> >dfff7800), AE_NOT_FOUND
> >    ACPI-0549: *** Error: AE_NOT_FOUND while evaluating method [_L1C]
> >for GPE[ 0]
> >
> >This happens with 2.6.14 and 2.6.16 kernels
> >
> >
> >Can you help me?
> >
> >

-- 
Emiliano Grilli
Linux user #209089 
http://www.emillo.net
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ACPI errors

[Emiliano Grilli]

lunedì, 05 giugno 2006 alle 20:49:44, Yu, Luming ha scritto:
> 
> Sure, Please open a bug at bugzilla.kernel.org.
> Please post acpidump output, and dmesg.
> 
> Thanks,
> Luming
> 
> >I get a lot of these errors in dmesg:
> >
> > ACPI-0339: *** Error: Looking up [\_TZ_.THRM] in namespace,
> >AE_NOT_FOUND
> >search_node dfff7800 start_node dfff7800 return_node 00000000
> >    ACPI-0508: *** Error: Method execution failed [\_GPE._L1C] (Node
> >dfff7800), AE_NOT_FOUND
> >    ACPI-0549: *** Error: AE_NOT_FOUND while evaluating method [_L1C]
> >for GPE[ 0]
> >
> >This happens with 2.6.14 and 2.6.16 kernels
> >
> >
> >Can you help me?
> >
> >

Hi, some months are passed from this report... Now I'm running 2.6.18
and the problem is still present, and very annoiying: basically I got
the cpu fan to "breathe" at ~ 1 Hz.
Some suggestion (other than buy different hardware)?
Cheers,
-- 
Emiliano Grilli
Linux user #209089 
http://www.emillo.net
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

ACPI errors

[Émeric MASCHINO]

Hi,

Just noticed today, but they perhaps exist for quite some time. I'm
recording ACPI errors on my hp workstation zx6000 when booting 3.9 and
3.10 kernels (didn't try earlier kernels):

[   25.509388] libata version 3.00 loaded.
[   25.514781] ACPI Error: [LBAS] Namespace lookup failure,
AE_ALREADY_EXISTS (20130328/dswload2-330)
[   25.514884] ACPI Exception: AE_ALREADY_EXISTS, During name
lookup/catalog (20130328/psobject-222)
[   25.514965] ACPI Error: Method parse/execution failed [\LBA_.PRT_] (Node e000
0040831e5af0), AE_ALREADY_EXISTS (20130328/psparse-537)
[   25.515087] ACPI Error: Method parse/execution failed [\_SB_.SBA0.PCI1._PRT]
(Node e0000040831e5cd0), AE_ALREADY_EXISTS (20130328/psparse-537)
[   25.515211] ACPI: Marking method _PRT as Serialized because of
AE_ALREADY_EXISTS error
[   25.515302] ACPI Error: Method execution failed [\_SB_.SBA0.PCI1._PRT] (Node
e0000040831e5cd0), AE_ALREADY_EXISTS (20130328/uteval-103)
[   25.515429] tg3 0000:20:02.0: can't derive routing for PCI INT A
[   25.515466] tg3 0000:20:02.0: PCI INT A: no GSI
[   25.630678] ACPI: Marking method PRT_ as Serialized because of
AE_ALREADY_EXISTS error

Can they be safely ignored? How to read them to find which devices
they refer to?

Google can find references of identical errors on other arches too.
Does it mean that there's nothing that can be done to fix them? On
some occurences, these errors were caused by kernel misconfiguration.

Thanks,

     Émeric