From: Andrew Morton <akpm@osdl.org>
To: Michael Thonke <iogl64nx@gmail.com>
Cc: robert.moore@intel.com, tk-shockwave@web.de,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: 2.6.13-rc3-mm3
Date: Thu, 4 Aug 2005 15:55:13 -0700 [thread overview]
Message-ID: <20050804155513.727a3894.akpm@osdl.org> (raw)
In-Reply-To: <42EAC9DB.9010702@gmail.com>
Michael Thonke <iogl64nx@gmail.com> wrote:
>
> Moore, Robert schrieb:
>
> >+ ACPI-0287: *** Error: Region SystemMemory(0) has no handler
> >+ ACPI-0127: *** Error: acpi_load_tables: Could not load namespace:
> >AE_NOT_EXIST
> >+ ACPI-0136: *** Error: acpi_load_tables: Could not load tables:
> >
> >This looks like a nasty case where some executable code in the table is
> >attempting to access a SystemMemory operation region before any OpRegion
> >handlers are initialized.
> >
> >We certainly want to see the output of acpidump to attempt to diagnose
> >and/or reproduce the problem.
> >
> >Bob
> >
> >
> >
> >
> Sorry for double post.
>
> With this mail I hand over the acpidump output with the pmtools
> Andrew pointed me to.
>
> And a dmesg output with CONFIG_KALLSYMS=y.
>
>
> I attached them in bz2 format, because of the length.
>
> I hope we find the problem.
>
Michael, I'm assuming that a) this problem remains in those -mm kernels
which include git-acpi.patch and that b) the problems are not present in
2.6.13-rc5 or 2.6.13-rc6, yes?
So I think we have a bug in git-acpi.patch?
If that's all correct then can you please test the next -mm (which will
include git-acpi.patch - the most recent -mm did not) and if the bug's
still there can you raise a bugzilla.kernel.org entry for it?
We seem to have a handful of bug reports against the -mm acpi patch.
Thanks.
next prev parent reply other threads:[~2005-08-04 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 19:42 Moore, Robert
2005-07-30 0:29 ` Michael Thonke
2005-08-04 22:55 ` Andrew Morton [this message]
2005-08-05 12:00 ` Michael Thonke
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=20050804155513.727a3894.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=iogl64nx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=tk-shockwave@web.de \
/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
Powered by JetHome