From: Andrew Morton <akpm@osdl.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>
Subject: Re: 2.6.18-rc4-mm3 -- ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [20060707]
Date: Fri, 8 Sep 2006 10:47:45 -0700 [thread overview]
Message-ID: <20060908104745.bff2449a.akpm@osdl.org> (raw)
In-Reply-To: <200609081010.58186.bjorn.helgaas@hp.com>
On Fri, 8 Sep 2006 10:10:57 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Thursday 07 September 2006 21:25, Miles Lane wrote:
> > Ping...
> >
> > I just reproduced this ACPI error with 2.6.18-rc5-mm1 + all hotfixes +
> > a crypto patch from Herbert + two nodemgr patched from Stefan + a max
> > trace depth patch from Ingo.
> >
> > Any additional debug information needed? Any progress?
>
> We identified the patch that causes the ACPI unknown exception,
> and I think Andrew will be removing it from the next -mm release.
>
> If you want to try reverting it yourself, here's the patch:
>
> http://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc4/2.6.18-rc4-mm3/broken-out/hot-add-mem-x86_64-acpi-motherboard-fix.patch
Yes, that was omitted from rc6-mm1.
next prev parent reply other threads:[~2006-09-08 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a44ae5cd0608262356j29c0234cl198fb207bcad383d@mail.gmail.com>
2006-08-27 7:14 ` 2.6.18-rc4-mm3 -- ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [20060707] Andrew Morton
2006-08-27 15:27 ` John Stoffel
2006-08-27 16:07 ` Laurent Riffard
2006-08-27 16:27 ` Miles Lane
2006-09-08 3:25 ` Miles Lane
2006-09-08 16:10 ` Bjorn Helgaas
2006-09-08 17:47 ` Andrew Morton [this message]
2006-08-28 1:44 ` John Stoffel
2006-09-08 16:09 ` Bjorn Helgaas
2006-09-08 17:54 ` John Stoffel
2006-09-09 23:47 ` John Stoffel
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=20060908104745.bff2449a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox