From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Milan Plzik <milan.plzik@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: DMI Info from Dell Latitude XT (and one weird ACPI issue)
Date: Sat, 18 Oct 2008 22:56:20 +0100 [thread overview]
Message-ID: <20081018215620.GA18897@srcf.ucam.org> (raw)
In-Reply-To: <1224356565.5831.14.camel@localhost>
On Sat, Oct 18, 2008 at 09:02:45PM +0200, Milan Plzik wrote:
> Oct 18 12:06:27 [kernel] [72428.864272] ACPI Error (psloop-0136): Found unknown opcode C0 at AML address ffffc200000267c7 offset 0, ignoring [20080609]
> Oct 18 12:06:27 [kernel] [72428.864280] ACPI Error (psloop-0136): Found unknown opcode ED at AML address ffffc200000267c8 offset 1, ignoring [20080609]
> Oct 18 12:06:27 [kernel] [72428.864286] ACPI Error (psloop-0136): Found unknown opcode 6F at AML address ffffc200000267c9 offset 2, ignoring [20080609]
> Oct 18 12:06:27 [kernel] [72428.864296] ACPI Error (psloop-0136): Found unknown opcode 4 at AML address ffffc200000267cc offset 5, ignoring [20080609]
> Oct 18 12:06:27 [kernel] [72428.864302] ACPI Error (psloop-0136): Found unknown opcode B0 at AML address ffffc200000267ce offset 7, ignoring [20080609]
> Oct 18 12:06:27 [kernel] [72428.864308] ACPI Error (psloop-0136): Found unknown opcode C3 at AML address ffffc200000267cf offset 8, ignoring [20080609]
> Oct 18 12:06:27 [kernel] [72428.864316] ACPI Error (psloop-0136): Found unknown opcode 6F at AML address ffffc200000267d9 offset 12, ignoring [20080609]
Yeah, we're seeing this on a few machines on resume - acpidump still
gives the correct output, so it seems to be something to be some sort of
internal state corruption. How much RAM do you have?
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2008-10-18 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 19:02 DMI Info from Dell Latitude XT (and one weird ACPI issue) Milan Plzik
2008-10-18 21:56 ` Matthew Garrett [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=20081018215620.GA18897@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=milan.plzik@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.