From: Zhang Rui <rui.zhang@intel.com>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ACPI Errors on Acer Aspire One
Date: Wed, 12 May 2010 10:12:53 +0800 [thread overview]
Message-ID: <1273630373.22924.74.camel@rzhang1-desktop> (raw)
In-Reply-To: <AANLkTilF304TbgACKtvc_FA01uxHrdRBS2Q-o6Tm-n8Q@mail.gmail.com>
On Tue, 2010-05-11 at 22:55 +0800, Jaswinder Singh Rajput wrote:
> Hello,
>
> With latest git kernel, I am getting following ACPI errors :
>
> [ 0.289038] ACPI Error (dsfield-0143): [CAPB] Namespace lookup
> failure, AE_ALREADY_EXISTS
> [ 0.289399] ACPI Error (psparse-0537): Method parse/execution
> failed [\_SB_.PCI0._OSC] (Node f70477e8), AE_ALREADY_EXISTS
> [ 0.299684] ACPI Error (dsfield-0143): [CAPB] Namespace lookup
> failure, AE_ALREADY_EXISTS
> [ 0.300007] ACPI Error (psparse-0537): Method parse/execution
> failed [\_SB_.PCI0._OSC] (Node f70477e8), AE_ALREADY_EXISTS
>
>
> dmesg : http://userweb.kernel.org/~jaswinder/acer_netbook/dmesg_2634-rc7.txt
> .config : http://userweb.kernel.org/~jaswinder/acer_netbook/config_2634-rc7.txt
>
please attach the acpidump output.
It would be great if you can file a new bug report at
https://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
and attach the dmesg and acpidump there.
thanks,
rui
> How can I fix these errors.
>
> Thanks,
> --
> Jaswinder Singh.
> --
> 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
prev parent reply other threads:[~2010-05-12 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 14:55 ACPI Errors on Acer Aspire One Jaswinder Singh Rajput
2010-05-12 2:12 ` Zhang Rui [this message]
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=1273630373.22924.74.camel@rzhang1-desktop \
--to=rui.zhang@intel.com \
--cc=jaswinderlinux@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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