public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>
Subject: Re: dsdt buggy acpi
Date: Tue, 1 Jul 2008 16:18:45 +0000	[thread overview]
Message-ID: <dd18b0c30807010918p48cfbe2bnb7e4a2bf00a01638@mail.gmail.com> (raw)
In-Reply-To: <200807011619.53339.rjw@sisk.pl>

On Tue, Jul 1, 2008 at 2:19 PM, Rafael J. Wysocki <rjw@sisk.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

  reply	other threads:[~2008-07-01 16:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  6:39 dsdt buggy acpi Justin Mattock
2008-07-01 14:19 ` Rafael J. Wysocki
2008-07-01 16:18   ` Justin Mattock [this message]
2008-07-02  5:25     ` Eduard - Gabriel Munteanu
2008-07-02  6:16       ` Justin Mattock
2008-07-02 10:09       ` Matthew Garrett
2008-07-02 11:48         ` Eduard - Gabriel Munteanu
2008-07-02 11:55           ` Matthew Garrett
2008-07-02 16:30             ` Justin Mattock
2008-07-02 16:35               ` Matthew Garrett
2008-07-02 17:37                 ` Justin Mattock
2008-07-04 11:32                   ` Alexey Starikovskiy
2008-07-04 16:23                     ` Justin Mattock
2008-07-04 21:45                       ` Justin Mattock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd18b0c30807010918p48cfbe2bnb7e4a2bf00a01638@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox