linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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

  reply	other threads:[~2011-10-31 11:23 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 11:19 kernel panic nick bray
2011-10-25 20:55 ` 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]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-17  2:59 Kernel panic zhang xintao
2012-12-02 17:30 Stefan Beller
2012-12-02 17:51 ` Stefan Beller
2012-12-02 19:13   ` rh
     [not found] <201201191202.q0JC243u029201@curly.dor.state.ma.us>
2012-01-19 15:26 ` Ron Murray
2010-05-18  4:23 kernel panic senthilkumaar2021
2010-05-18  4:47 ` Justin P. Mattock
2010-05-18  4:55   ` senthilkumaar2021
2010-05-18  5:05     ` Eric Dumazet
2010-05-18  5:08     ` Justin P. Mattock
     [not found] <9a5eeacd0804210350v79db27f0of73a29c55e2b7311@mail.gmail.com>
2008-04-21 10:56 ` Kernel panic Matthias Andersson
2008-04-21 11:07   ` Bart Van Assche
2006-08-24 18:01 kernel panic febo
2006-02-24 10:15 Rogel Miguez
     [not found] <4GLD8-5Wa-27@gated-at.bofh.it>
2005-08-29 23:50 ` Robert Hancock
2005-08-29  6:43 manomugdha biswas
2004-04-12 10:39 osmaker@hu
2004-04-12 10:43 ` osmaker@hu
2004-04-12 12:26 ` Zwane Mwaikambo
     [not found] <S263478AbTLEJ0s/20031205092648Z+878@vger.kernel.org>
2003-12-05  9:34 ` Kernel panic neel vanan
2003-12-05 14:19   ` William Lee Irwin III
2003-12-06  5:47     ` William Lee Irwin III
2003-03-26 20:22 Kernel Panic David van Hoose
2003-03-26 11:28 ` dan carpenter
2002-04-06  4:16 Kernel panic Daniel Mundy
2002-04-06 18:05 ` Alan Cox
2002-03-05 22:31 Hanno Böck
2002-03-06  1:40 ` Lionel Bouton
2002-03-06  1:50   ` Andre Hedrick
2002-02-19 18:27 kernel panic chiranjeevi vaka
2002-02-19 18:50 ` Justin Carlson
2002-02-21 17:17 ` Fernando Korndorfer
2002-01-02 19:34 nntp
2001-12-15 18:47 mempool design Benjamin LaHaise
2001-12-15 22:18 ` Ingo Molnar
2001-12-17 15:04   ` Andrea Arcangeli
2001-12-17 15:38     ` Victor Yodaiken
2001-12-17 17:33       ` kernel panic Geoffrey
2000-11-17 17:44 Kernel Panic Dave Seff
2000-11-18 19:29 ` Chmouel Boudjnah

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;
as well as URLs for NNTP newsgroup(s).