Re: Executed AML Breakpoint opcode

[YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>]

On Thu, Jul 06, 2006 at 06:54:36PM +1000, Petr Janda wrote:
> The fix has fixed the breakpoint. However, dmesg still says
> 
> unknown: I/O range not supported

This is the same on FreeBSD - acpi_res_set_iorange() is the function
printing this message.  It's been implemented as that way for years.

> can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - 
> AE_AML_INVALID_RESOURCE_TYPE

There's several places in ACPI-CA code where it can display this message,
so I'd look at a verbose dmesg output with the following variables set
at boot prompt(don't try to post it to the mailing list) to find which
function in ACPI-CA code is showing the message:

  debug.acpi.layer="ACPI_RESOURCES"
  debug.acpi.level="ACPI_LV_FUNCTIONS"

> Can anyone have look at it and explain to me why this shows up, and fix it 
> possibly?

They're probably as harmless as they are on FreeBSD.
Quickest workaround I can think of is to set
  debug.acpi.disabled="resource"
in /boot/loader.conf, but I'm not sure if it has any side effect.
If you're not seeing any problem other than the annoying warning
messages and the LPT port, you can ignore them.