public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Matthew Garrett <mjg@redhat.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] 9a884ab64a4d092b4c3bf24fd9a30f7fbd4591e7 causes boot hang
Date: Tue, 15 Dec 2009 22:41:19 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912152240320.6885@localhost.localdomain> (raw)
In-Reply-To: <1260925040.3834.69.camel@minggr.sh.intel.com>

Matthew,

Alternatively, you can pick up the latest ACPICA code from
the acpica or release branches of the acpi tree.

Please let me know as soon as you can check if it helps.

thanks,
Len Brown, Intel Open Source Technology Center

On Wed, 16 Dec 2009, Lin Ming wrote:

> On Wed, 2009-12-16 at 02:15 +0800, Matthew Garrett wrote:
> > Commit 9a884ab64a4d092b4c3bf24fd9a30f7fbd4591e7 (ACPICA: Add additional 
> > module-level code support) results in one of my test machines hanging at 
> > boot. The last line output is:
> > 
> > bio: create slab <bio-0> at 0
> > 
> > which would normally be followed by
> > 
> > ACPI: EC: Look up EC in DSDT
> > 
> > but instead the machine hangs without printing this line. Reverting the 
> > commit results in the machine booting. acpidump output attached.
> > 
> 
> Hi, Matthew
> 
> Could you try the attached ACPICA latest release (20091214) patch
> series? There are module level code and _REG method fixes included in
> it.
> 
> Checkout Linus' tree.
> git am acpica-v20091214.patch
> 
> Thanks,
> Lin Ming
> 
> 

  reply	other threads:[~2009-12-16  3:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 18:15 [REGRESSION] 9a884ab64a4d092b4c3bf24fd9a30f7fbd4591e7 causes boot hang Matthew Garrett
2009-12-16  0:57 ` Lin Ming
2009-12-16  3:41   ` Len Brown [this message]
2009-12-16 15:10   ` Matthew Garrett
2009-12-22  2:14     ` Len Brown

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=alpine.LFD.2.00.0912152240320.6885@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mjg@redhat.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