From: Thomas Renninger <trenn@suse.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: nick bray <nick.bray1@ntlworld.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
lenb@kernel.org, Zhao Yakui <yakui.zhao@intel.com>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: kernel panic
Date: Mon, 31 Oct 2011 13:24:04 +0100 [thread overview]
Message-ID: <201110311324.05185.trenn@suse.de> (raw)
In-Reply-To: <201110280413.51751.trenn@suse.de>
On Friday 28 October 2011 04:13:50 Thomas Renninger wrote:
...
> Ah, maybe an older acpidump got used and the _CST method of the
> object is in a not exported, dynamically loaded SSDT.
> This is very likely.
>
> Please use a very recent acpidump:
> Hm, Len's ftp directory on kernel.org where latest acpidump was
> located is gone?
I've put a (hopefully) recent acpidump source here:
ftp.suse.com/pub/people/trenn/acpidump
Should get available in an hour or so.
I expect you see:
"Dynamic OEM Table Load"
message(s) in dmesg and the SSDT which includes the ACPI parts which are
causing this is loaded at runtime. Older acpidump versions were not able
to extract these, the one I put on my ftp account should be able to.
Can you run it and put the output somewhere (related Ubuntu bug?) and
provide a pointer to it, please.
Hm, you could create a bug here:
http://acpica.org/bugzilla
It looks like ACPI code in the _CST function is triggering an ACPICA
interpreter memory bug when it tries to evaluate the func (guessing...).
Thomas
prev parent reply other threads:[~2011-10-31 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EA549C3.4080206@ntlworld.com>
2011-10-25 20:55 ` kernel panic Bjorn Helgaas
2011-10-26 10:00 ` Len Brown
2011-10-26 14:53 ` Bjorn Helgaas
[not found] ` <4EA82832.2070201@ntlworld.com>
2011-10-26 16:18 ` Bjorn Helgaas
[not found] ` <4EA83F5D.20001@ntlworld.com>
2011-10-26 18:10 ` Bjorn Helgaas
2011-10-28 2:13 ` Thomas Renninger
2011-10-31 12:24 ` Thomas Renninger [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=201110311324.05185.trenn@suse.de \
--to=trenn@suse.de \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.bray1@ntlworld.com \
--cc=rui.zhang@intel.com \
--cc=yakui.zhao@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox