public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* RE: [ACPI] Re: 2.6.13-rc3-mm3
@ 2005-07-29 19:42 Moore, Robert
  2005-07-30  0:29 ` Michael Thonke
  0 siblings, 1 reply; 4+ messages in thread
From: Moore, Robert @ 2005-07-29 19:42 UTC (permalink / raw)
  To: Andrew Morton, Michael Thonke; +Cc: iogl64nx, linux-kernel, acpi-devel

+    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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ACPI] Re: 2.6.13-rc3-mm3
  2005-07-29 19:42 [ACPI] Re: 2.6.13-rc3-mm3 Moore, Robert
@ 2005-07-30  0:29 ` Michael Thonke
  2005-08-04 22:55   ` Andrew Morton
  0 siblings, 1 reply; 4+ messages in thread
From: Michael Thonke @ 2005-07-30  0:29 UTC (permalink / raw)
  To: Moore, Robert; +Cc: Andrew Morton, Michael Thonke, linux-kernel, acpi-devel

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]

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.

Best regards
          Michael

[-- Attachment #2: acpidump.2613rc3mm3.bz2 --]
[-- Type: application/x-bzip, Size: 31124 bytes --]

[-- Attachment #3: dmesg_ksyms.hda-intel.bz2 --]
[-- Type: application/x-bzip, Size: 5285 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ACPI] Re: 2.6.13-rc3-mm3
  2005-07-30  0:29 ` Michael Thonke
@ 2005-08-04 22:55   ` Andrew Morton
  2005-08-05 12:00     ` Michael Thonke
  0 siblings, 1 reply; 4+ messages in thread
From: Andrew Morton @ 2005-08-04 22:55 UTC (permalink / raw)
  To: Michael Thonke; +Cc: robert.moore, tk-shockwave, linux-kernel, acpi-devel

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ACPI] Re: 2.6.13-rc3-mm3
  2005-08-04 22:55   ` Andrew Morton
@ 2005-08-05 12:00     ` Michael Thonke
  0 siblings, 0 replies; 4+ messages in thread
From: Michael Thonke @ 2005-08-05 12:00 UTC (permalink / raw)
  To: Andrew Morton; +Cc: robert.moore, linux-kernel, acpi-devel



Hello Andrew,
> Andrew Morton wrote:
> 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?
>   
a.) I don't have any problems in 2.6.13-rc5-git[1-3] and 2.6.13-rc4-mm1 
they are working quite fantastic.
Good work :-)
> So I think we have a bug in git-acpi.patch?
>   
I reverted them and left them in..no problems with kernels I said above.
Again good work :-)
> 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?
>   
I would, but the motherboard is dropped from my hardware test approval. 
Maybe I can get it back to test again
if it helps to solve some acpi issues.
> We seem to have a handful of bug reports against the -mm acpi patch.
>   
Well, I noticed that there are a lots of bugs and I'm willing to find 
search and reproduce them.

> Thanks.
I have to say thanks for the great help/feedback.

Greets and
Best regards

--
_Michael Thonke
IT-Systemintegrator /
System- and Softwareanalyist


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-08-05 12:00 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-29 19:42 [ACPI] Re: 2.6.13-rc3-mm3 Moore, Robert
2005-07-30  0:29 ` Michael Thonke
2005-08-04 22:55   ` Andrew Morton
2005-08-05 12:00     ` Michael Thonke

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox