https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082010-12-02T17:02:08ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1928: Weird behaviour after APIC_IO changeshttps://bugs.dragonflybsd.org/issues/1928?journal_id=93922010-12-02T17:02:08Ztuxillo
<ul></ul><p><a class="external" href="http://leaf.dragonflybsd.org/~tuxillo/archive/bugs/1928/dmesg_02october_verbose.txt">http://leaf.dragonflybsd.org/~tuxillo/archive/bugs/1928/dmesg_02october_verbose.txt</a><br /><a class="external" href="http://leaf.dragonflybsd.org/~tuxillo/archive/bugs/1928/dmesg_26november_verbose.txt">http://leaf.dragonflybsd.org/~tuxillo/archive/bugs/1928/dmesg_26november_verbose.txt</a><br /><a class="external" href="http://leaf.dragonflybsd.org/~tuxillo/archive/bugs/1928/dmesg_sorted.diff">http://leaf.dragonflybsd.org/~tuxillo/archive/bugs/1928/dmesg_sorted.diff</a></p> DragonFlyBSD - Bug #1928: Weird behaviour after APIC_IO changeshttps://bugs.dragonflybsd.org/issues/1928?journal_id=93932010-12-02T19:21:28Zalexh
<ul></ul><p>Obvious question: Have you tried toggling the apic_io tunable? Did you have <br />APIC_IO enabled before? Do you now?</p>
<p>Cheers,<br />Alex</p> DragonFlyBSD - Bug #1928: Weird behaviour after APIC_IO changeshttps://bugs.dragonflybsd.org/issues/1928?journal_id=93952010-12-02T19:45:07Zahuete.devel
<ul></ul><p>Hi Alex,</p>
<p>As you can see in both dmesgs, APIC_IO is disabled:</p>
<pre><code>Warning: APIC I/O disabled</code></pre>
<p>If I enable it, no hard disk is detected.</p> DragonFlyBSD - Bug #1928: Weird behaviour after APIC_IO changeshttps://bugs.dragonflybsd.org/issues/1928?journal_id=94632011-01-04T08:24:02Ztuxillo
<ul></ul><p>Commit 8995ba1d97e8261b45d0fdc0d710068a55f4ccc4 fixed the weirdness and the<br />interrupt problems for me.</p>