public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chander Kant" <ck-cFQ2QR18kktMdczFR1vadtBPR1lH4CV8@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: "Grover,
	Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	ck-cFQ2QR18kktMdczFR1vadtBPR1lH4CV8@public.gmane.org
Subject: need debugging help
Date: Tue, 1 Jul 2003 17:13:23 -0700	[thread overview]
Message-ID: <200307020013.h620DNO16049@meteor.hosting4less.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]


Thanks Andrew. I am moving the discussion to the acpi-devel list:

All,

I am attaching the output of "iasl -d dsdt" (in zipped format).

Please let me know if we can do anything on this system to get rid of the problem mentioned below.

Thanks,
Chander


"Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote ..
> > When we bring up a recent Linux kernel (2.4.20) with ACPI 
> > patch on our laptop. We get following error messages 
> > continously from the kernel:
> > 
> > Jul  2 04:31:16 localhost kernel:     ACPI-1103: *** Error: 
> > Method execution failed [\_SB_.PCI0.SBRG.EC0_._Q1E] (Node 
> > c33b1380), AE_AML_REGION_LIMIT
> > 
> > Besides filling up the log files, and making the console 
> > windows, I think it is also hampering ACPI functionality to 
> > work, as I do not see and battery file in the /proc/acpi directory.
> > 
> > I have seen other folks in user groups and lists getting 
> > these errors, but so far I have not seen a good response as 
> > far as a fix or workaround.
> 
> It's most likely an AML error. This particular error is not uncommon.
> 
> Do you have the ASL for this machine? If not, get iasl from
> http://developer.intel.com/technology/iapc/acpi/downloads.htm and feed
> your DSDT into it (from /proc/acpi/dsdt). with the -d option. Then, go
> take a look at the _Q1E method.
> 
> 

[-- Attachment #2: dsdt.dsl.gz --]
[-- Type: application/x-gzip, Size: 11329 bytes --]

             reply	other threads:[~2003-07-02  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02  0:13 Chander Kant [this message]
     [not found] <F760B14C9561B941B89469F59BA3A847E97021@orsmsx401.jf.intel. com>
2003-07-14  0:04 ` need debugging help Chander Kant
  -- strict thread matches above, loose matches on Subject: below --
2003-07-14  0:04 Grover, Andrew
2003-07-14  1:01 Grover, Andrew

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=200307020013.h620DNO16049@meteor.hosting4less.com \
    --to=ck-cfq2qr18kktmdczfr1vadtbpr1lh4cv8@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /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