DragonFly bugs List (threaded) for 2006-07
Re: Executed AML Breakpoint opcode
Hmm, Ive set
in boot /boot/loader.conf and /boot/defaults/loader.conf but the message is still there.
in there also seems to have no effect.
YONETANI Tomokazu wrote:
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_ -
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:
Can anyone have look at it and explain to me why this shows up, and fix it
They're probably as harmless as they are on FreeBSD.
Quickest workaround I can think of is to set
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.