[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dd18b0c30807010918p48cfbe2bnb7e4a2bf00a01638@mail.gmail.com>
Date: Tue, 1 Jul 2008 16:18:45 +0000
From: "Justin Mattock" <justinmattock@...il.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"ACPI Devel Maling List" <linux-acpi@...r.kernel.org>
Subject: Re: dsdt buggy acpi
On Tue, Jul 1, 2008 at 2:19 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Tuesday, 1 of July 2008, Justin Mattock wrote:
>> With not knowing what I'm doing, I think I need assistance. With looking at acpi
>> I decided to have a try at the dsdt.dat bit(pretty easy so far) except
>> I'm being confronted with some errors, in of which
>> I don't know how to resolve(still Googling for the answer) If anybody
>> has any answers it would sure be appreciated.
>> errors below:
>>
>> Intel ACPI Component Architecture
>> ASL Optimizing Compiler version 20051216 [Jan 9 2006]
>> Copyright (C) 2000 - 2005 Intel Corporation
>> Supports ACPI Specification Revision 3.0
>>
>> No back ptr to Op: type 8
>> No back ptr to Op: type 8
>> dsdt.dsl 511: If (And (PDC0, 0x08))
>> Error 1061 - Object does not exist ^ (PDC0)
>>
>> dsdt.dsl 514: If (And (PDC0, 0x10))
>> Error 1061 - Object does not exist ^ (PDC0)
>>
>> dsdt.dsl 521: If (And (PDC1, 0x08))
>> Error 1065 - ^ Object not accessible from
>> this scope (PDC1)
>>
>> dsdt.dsl 524: If (And (PDC1, 0x10))
>> Error 1065 - ^ Object not accessible
>> from this scope (PDC1)
>>
>> ASL Input: dsdt.dsl - 5040 lines, 171343 bytes, 1814 keywords
>> Compilation complete. 4 Errors, 0 Warnings, 0 Remarks, 609 Optimizations
>>
>> I'm figuring if I can at least fix this, then maybe this will help
>> with: http://bugzilla.kernel.org/show_bug.cgi?id=10724
>> acpi gpe storm regression.(or at least get me this much closer to
>> figuring out what is up with that).
>
> Please have a look at http://www.lesswatts.org/projects/acpi/
>
> Thanks,
> Rafael
>
Cool; thanks.
I'll check that out and see where and how I can locate the dsdt
manufacture number, then see if I can fix the broken dsdt error and
apply this to the kernel and see what happens.
regards;
--
Justin P. Mattock
--
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