https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082006-07-05T23:14:20ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8212006-07-05T23:14:20Zqhwt+dfly
<ul></ul><p>On Thu, Jul 06, 2006 at 12:54:47AM +1000, Petr Janda wrote:</p>
<blockquote>
<p>Hi,</p>
<p>I got my self a smp server box today, a HP Netserver LP 1000r and Im <br />trying to install DragonFly on it but booting with ACPI brings me to do <br />the debugger. The message is:</p>
<p>......<br />acpi0: <HP HWPC213> on motherboard<br />Debugger("Executed AML Breakpoing opcode")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0</p>
</blockquote>
<p>Here's a summary from Martin P. Hellwig two years ago about this<br />breakpoint issue:<br /><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html">http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html</a></p>
<p>I'll commit a fix for this now, thanks for the report.</p>
<blockquote>
<p>WARNING: ACPI is disabling APM's device You can't run both</p>
</blockquote>
<p>This is harmless.</p>
<blockquote>
<p>unknown: I/O range not supported<br />can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - <br />AE_AML_INVALID_RESOURCE_TYPE</p>
</blockquote>
<p>I wonder if Martin also saw this message at that time.</p> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8272006-07-06T16:02:20Zelekktretterr
<ul></ul><p>Hi there,</p>
<p>The fix has fixed the breakpoint. However, dmesg still says</p>
<p>unknown: I/O range not supported<br />can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - <br />AE_AML_INVALID_RESOURCE_TYPE</p>
<p>Can anyone have look at it and explain to me why this shows up, and fix it possibly?</p>
<p>Cheers</p>
<p>YONETANI Tomokazu wrote:</p>
<blockquote>
<p>On Thu, Jul 06, 2006 at 12:54:47AM +1000, Petr Janda wrote:</p>
<blockquote>
<p>Hi,</p>
<p>I got my self a smp server box today, a HP Netserver LP 1000r and Im <br />trying to install DragonFly on it but booting with ACPI brings me to do <br />the debugger. The message is:</p>
<p>......<br />acpi0: <HP HWPC213> on motherboard<br />Debugger("Executed AML Breakpoing opcode")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0</p>
</blockquote>
<p>Here's a summary from Martin P. Hellwig two years ago about this<br />breakpoint issue:<br /><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html">http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html</a></p>
<p>I'll commit a fix for this now, thanks for the report.</p>
<blockquote>
<p>WARNING: ACPI is disabling APM's device You can't run both</p>
</blockquote>
<p>This is harmless.</p>
<blockquote>
<p>unknown: I/O range not supported<br />can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - <br />AE_AML_INVALID_RESOURCE_TYPE</p>
</blockquote>
<p>I wonder if Martin also saw this message at that time.</p>
</blockquote> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8282006-07-06T18:50:20Zqhwt+dfly
<ul></ul><p>On Thu, Jul 06, 2006 at 06:54:36PM +1000, Petr Janda wrote:</p>
<blockquote>
<p>The fix has fixed the breakpoint. However, dmesg still says</p>
<p>unknown: I/O range not supported</p>
</blockquote>
<p>This is the same on FreeBSD - acpi_res_set_iorange() is the function<br />printing this message. It's been implemented as that way for years.</p>
<blockquote>
<p>can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - <br />AE_AML_INVALID_RESOURCE_TYPE</p>
</blockquote>
<p>There's several places in ACPI-CA code where it can display this message,<br />so I'd look at a verbose dmesg output with the following variables set<br />at boot prompt(don't try to post it to the mailing list) to find which<br />function in ACPI-CA code is showing the message:</p>
<pre><code>debug.acpi.layer="ACPI_RESOURCES" <br /> debug.acpi.level="ACPI_LV_FUNCTIONS"</code></pre>
<blockquote>
<p>Can anyone have look at it and explain to me why this shows up, and fix it <br />possibly?</p>
</blockquote>
<p>They're probably as harmless as they are on FreeBSD.<br />Quickest workaround I can think of is to set<br /> debug.acpi.disabled="resource" <br />in /boot/loader.conf, but I'm not sure if it has any side effect.<br />If you're not seeing any problem other than the annoying warning<br />messages and the LPT port, you can ignore them.</p> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8312006-07-06T20:06:10Zelekktretterr
<ul></ul><p>Hmm, Ive set</p>
<p>debug.acpi.disabled="resource"</p>
<p>in boot /boot/loader.conf and /boot/defaults/loader.conf but the message is still there.</p>
<p>Putting <br /> debug.acpi.layer="ACPI_RESOURCES" <br /> debug.acpi.level="ACPI_LV_FUNCTIONS"</p>
<p>in there also seems to have no effect.</p>
<p>YONETANI Tomokazu wrote:</p>
<blockquote>
<p>On Thu, Jul 06, 2006 at 06:54:36PM +1000, Petr Janda wrote:</p>
<blockquote>
<p>The fix has fixed the breakpoint. However, dmesg still says</p>
<p>unknown: I/O range not supported</p>
</blockquote>
<p>This is the same on FreeBSD - acpi_res_set_iorange() is the function<br />printing this message. It's been implemented as that way for years.</p>
<blockquote>
<p>can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - <br />AE_AML_INVALID_RESOURCE_TYPE</p>
</blockquote>
<p>There's several places in ACPI-CA code where it can display this message,<br />so I'd look at a verbose dmesg output with the following variables set<br />at boot prompt(don't try to post it to the mailing list) to find which<br />function in ACPI-CA code is showing the message:</p>
<p>debug.acpi.layer="ACPI_RESOURCES" <br />debug.acpi.level="ACPI_LV_FUNCTIONS"</p>
<blockquote>
<p>Can anyone have look at it and explain to me why this shows up, and fix it <br />possibly?</p>
</blockquote>
<p>They're probably as harmless as they are on FreeBSD.<br />Quickest workaround I can think of is to set<br />debug.acpi.disabled="resource" <br />in /boot/loader.conf, but I'm not sure if it has any side effect.<br />If you're not seeing any problem other than the annoying warning<br />messages and the LPT port, you can ignore them.</p>
</blockquote> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8322006-07-06T20:26:20Zqhwt+dfly
<ul></ul><p>On Thu, Jul 06, 2006 at 10:59:51PM +1000, Petr Janda wrote:</p>
<blockquote>
<p>debug.acpi.disabled="resource"</p>
</blockquote>
<p>Oops, that should've been "sysresource" (it's written in acpi(4) BTW).</p>
<blockquote>
<p>in boot /boot/loader.conf and /boot/defaults/loader.conf but the message is <br />still there.</p>
<p>Putting <br />debug.acpi.layer="ACPI_RESOURCES" <br />debug.acpi.level="ACPI_LV_FUNCTIONS"</p>
<p>in there also seems to have no effect.</p>
</blockquote>
<p>Oops, I forgot saying that you need to reinstall acpi.ko with<br />debugging enabled to use them:</p>
<p>cd /sys/dev/acpica5<br />setenv ACPI_DEBUG yes<br />setenv MAKEOBJDIRPREFIX /usr/obj<br />make obj && make depend && make && make install</p>
<p>But then of course, it starts dropping into the debugger at the<br />breakpoint opcode on every reboot :) You might want to create<br />a custom AML like Martin did.</p> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8342006-07-06T20:47:20Zelekktretterr
<ul></ul><p>Do i need to recompile acpi.ko for this one too? Because it still doesnt</p>
<p>work and I dont have the system connected to the internet at the moment <br />so I cant get the source now.</p>
<p>YONETANI Tomokazu wrote:</p>
<blockquote>
<p>On Thu, Jul 06, 2006 at 10:59:51PM +1000, Petr Janda wrote:</p>
<blockquote>
<p>debug.acpi.disabled="resource"</p>
</blockquote>
<p>Oops, that should've been "sysresource" (it's written in acpi(4) BTW).</p>
</blockquote> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8362006-07-06T21:37:10Zqhwt+dfly
<ul></ul><p>On Thu, Jul 06, 2006 at 11:42:36PM +1000, Petr Janda wrote:</p>
<blockquote><blockquote><blockquote>
<p>debug.acpi.disabled="resource"</p>
</blockquote>
<p>Oops, that should've been "sysresource" (it's written in acpi(4) BTW).</p>
</blockquote>
<p>Do i need to recompile acpi.ko for this one too?</p>
</blockquote>
<p>No, debug.acpi.disabled works without ACPI_DEBUG. But you need "set" <br />in front of it (in case you never used the boot loader prompt before):</p>
<p>set debug.acpi.disabled="sysresource"</p>
<p>Cheers.</p> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8582006-07-08T21:09:20Zmhellwig
<ul></ul><p>YONETANI Tomokazu wrote:</p>
<blockquote>
<p>On Thu, Jul 06, 2006 at 12:54:47AM +1000, Petr Janda wrote:</p>
<blockquote>
<p>Hi,</p>
<p>I got my self a smp server box today, a HP Netserver LP 1000r and Im <br />trying to install DragonFly on it but booting with ACPI brings me to do <br />the debugger. The message is:</p>
<p>......<br />acpi0: <HP HWPC213> on motherboard<br />Debugger("Executed AML Breakpoing opcode")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0</p>
</blockquote>
<p>Here's a summary from Martin P. Hellwig two years ago about this<br />breakpoint issue:<br /><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html">http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html</a></p>
<p>I'll commit a fix for this now, thanks for the report.</p>
<blockquote>
<p>WARNING: ACPI is disabling APM's device You can't run both</p>
</blockquote>
<p>This is harmless.</p>
<blockquote>
<p>unknown: I/O range not supported<br />can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ - <br />AE_AML_INVALID_RESOURCE_TYPE</p>
</blockquote>
<p>I wonder if Martin also saw this message at that time.</p>
</blockquote>
<p>If I remember correctly I saw indeed these kind of messages.<br />At this moment that box is happily running FBSD 6.1.<br />But I will reinstall df next week, it's about time I'll dig into it <br />again (it's a personal test box).</p> DragonFlyBSD - Bug #228: Executed AML Breakpoint opcodehttps://bugs.dragonflybsd.org/issues/228?journal_id=8622006-07-09T13:44:10Zelekktretterr
<ul></ul><p>That would be great Martin. I just dont have time for all that debugging<br />at the moment myself.</p>
<p>Petr</p>
<blockquote>
<p>YONETANI Tomokazu wrote:</p>
<blockquote>
<p>On Thu, Jul 06, 2006 at 12:54:47AM +1000, Petr Janda wrote:</p>
<blockquote>
<p>Hi,</p>
<p>I got my self a smp server box today, a HP Netserver LP 1000r and Im<br />trying to install DragonFly on it but booting with ACPI brings me to do<br />the debugger. The message is:</p>
<p>......<br />acpi0: <HP HWPC213> on motherboard<br />Debugger("Executed AML Breakpoing opcode")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0</p>
</blockquote>
<p>Here's a summary from Martin P. Hellwig two years ago about this<br />breakpoint issue:<br /><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html">http://leaf.dragonflybsd.org/mailarchive/bugs/2004-08/msg00119.html</a></p>
<p>I'll commit a fix for this now, thanks for the report.</p>
<blockquote>
<p>WARNING: ACPI is disabling APM's device You can't run both</p>
</blockquote>
<p>This is harmless.</p>
<blockquote>
<p>unknown: I/O range not supported<br />can't fetch resources for \\_SB_.PCI0.ISA_.SIO_.LPT_ -<br />AE_AML_INVALID_RESOURCE_TYPE</p>
</blockquote>
<p>I wonder if Martin also saw this message at that time.</p>
</blockquote>
<p>If I remember correctly I saw indeed these kind of messages.<br />At this moment that box is happily running FBSD 6.1.<br />But I will reinstall df next week, it's about time I'll dig into it<br />again (it's a personal test box).</p>
<p>--<br />mph</p>
</blockquote>