DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082020-08-21T17:36:41ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3245 (New): panic: free: guard1x fail, i915 load from loader.confhttps://bugs.dragonflybsd.org/issues/32452020-08-21T17:36:41Zpolachok
<p>Same as <a class="external" href="https://bugs.dragonflybsd.org/issues/2837">https://bugs.dragonflybsd.org/issues/2837</a><br />It happened after I upgraded 2.8.1 release to master</p>
<p>DragonFly v5.9.0.756.g2e6c7-DEVELOPMENT #0: Fri Aug 21 19:51:28 MSK 2020 plhk@darkstar:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64</p> DragonFlyBSD - Bug #1811 (Closed): Machine hangs with recent codehttps://bugs.dragonflybsd.org/issues/18112010-08-29T22:09:37Zpolachok
<p>Hi. I updated sources today and can't boot any more (it hangs at "Finish MP <br />startup").<br />I attach serial log with newer kernel (top) and older one (on the bottom).</p> DragonFlyBSD - Bug #1713 (Closed): [pkgsrc] emulators/qemu wants OSS_GETVERSIONhttps://bugs.dragonflybsd.org/issues/17132010-04-03T03:31:37Zpolachok
<p>qemu 0.12.3 needs OSS_GETVERSION to build. I tried to fix it similar to these<br />FreeBSD commits:<br /><a class="external" href="http://svn.freebsd.org/viewvc/base?view=revision&revision=164613">http://svn.freebsd.org/viewvc/base?view=revision&revision=164613</a><br /><a class="external" href="http://svn.freebsd.org/viewvc/base?view=revision&revision=202150">http://svn.freebsd.org/viewvc/base?view=revision&revision=202150</a></p>
<p>Not sure if it works okay (no sound card to test here):<br /><a class="external" href="http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/commit/0497b0cb322307ef608bc5e7120111b25fb0531a">http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/commit/0497b0cb322307ef608bc5e7120111b25fb0531a</a></p> DragonFlyBSD - Bug #1616 (Closed): hotplug notificationhttps://bugs.dragonflybsd.org/issues/16162009-11-27T07:27:26Zpolachok
<p>I think it could be nice to receive notification for creation and<br />removal of device nodes in userland. So I ported hotplug(4) and<br />hotplugd(8) from OpenBSD. I like the design, it's clean and simple:<br />an event contains type (attach or detach), device class (disk, tty or<br />generic) and name (as in /dev). Events are queued and can be read<br />from /dev/hotplug one-by-one (hotplugd(8) does that and can be<br />configured to execute commands on event arrival).</p>
<p>You can get code to review here:<br /> <a class="external" href="http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/hotplug2">http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/hotplug2</a></p> DragonFlyBSD - Bug #1589 (Closed): ACPI updatehttps://bugs.dragonflybsd.org/issues/15892009-10-26T20:52:10Zpolachok
<p>I am working on updating ACPI to modern state and ACPI interrupt<br /> routing. You can get the current code here [1]. It's going not bad but<br /> I have some questions which I need answers for before moving on.</p>
<pre><code>1) Locking. I have no idea which one should be used. There're 2<br /> families of locking macros: ACPI_SERIAL_* and ACPI_LOCK_*<br /> (see sys/dev/acpica5/acpivar.h). FreeBSD uses mtx_* for ACPI_LOCK<br /> and sx_* for ACPI_SERIAL.</code></pre>
<pre><code>2) APIC. Current APIC code doesn't allow setting interrupts from other<br /> subsystems and changing interrupts after boot, but this is required for<br /> BUS_CONFIG_INTR to work.</code></pre>
<pre><code>[1] <a class="external" href="http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/newacpi">http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/newacpi</a></code></pre> DragonFlyBSD - Bug #1566 (Closed): root fallbackhttps://bugs.dragonflybsd.org/issues/15662009-10-13T04:27:36Zpolachok
<p>I think it could be nice to have root fallback. User can specify possible roots <br />via vfs.root.mountfrom and if one doesn't work (disk number changed or something), <br />then another one can be used.</p>
<p>Patch here:<br /><a class="external" href="http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/commit/155ea5a2f619c1d1d901">http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/commit/155ea5a2f619c1d1d901</a><br />bc6d26b246e456995ed9</p> DragonFlyBSD - Bug #1540 (Closed): LiveDVD: SMP mode brokenhttps://bugs.dragonflybsd.org/issues/15402009-09-28T02:14:16Zpolachok
<p>3.Boot DragonFly in SMP mode<br />4.Boot DragonFly in SMP-NOAPIC mode</p>
<p>doesn't work from LiveDVD:<br />can't find /kernel.smp/kernel.noapic</p> DragonFlyBSD - Bug #1522 (Closed): md0 partitions are not available in mountroot>https://bugs.dragonflybsd.org/issues/15222009-09-20T23:36:09Zpolachok
<p>Preload md image with load -t md_image /boot/miniroot.img in bootloader. Only md0 <br />is shown in available devices list in mountroot prompt. Although md0s0 is in /dev <br />after boot.<br />Image to test with: <a class="external" href="http://polachok.v12.su/miniroot.img">http://polachok.v12.su/miniroot.img</a></p> DragonFlyBSD - Bug #1519 (Closed): Keyboard broken in xdmhttps://bugs.dragonflybsd.org/issues/15192009-09-18T00:12:10Zpolachok
<p>If you start xdm with xdm_enable=YES in /etc/rc.conf keyboard won't work at all <br />(can't switch to console or anything). If you start xdm from user, it works.</p>
<p>Here's the relevant part of Xorg.0.log:<br />(<b>) Option "CoreKeyboard" <br />(</b>) Keyboard0: always reports core events<br />(<b>) Option "Protocol" "standard" <br />(</b>) Keyboard0: Protocol: standard<br />(<b>) Option "AutoRepeat" "500 30" <br />(</b>) Option "XkbRules" "xorg" <br />(<b>) Keyboard0: XkbRules: "xorg" <br />(</b>) Option "XkbModel" "pc105" <br />(<b>) Keyboard0: XkbModel: "pc105" <br />(</b>) Option "XkbLayout" "us,ru(winkeys)" <br />(<b>) Keyboard0: XkbLayout: "us,ru(winkeys)" <br />(</b>) Option "XkbOptions" "grp:caps_toggle,grp_led:scroll,compose:lwin" <br />(<b>) Keyboard0: XkbOptions: "grp:caps_toggle,grp_led:scroll,compose:lwin" <br />(</b>) Option "CustomKeycodes" "off" <br />(**) Keyboard0: CustomKeycodes disabled<br />(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)<br />(EE) KbdOn: tcsetattr: Bad file descriptor</p> DragonFlyBSD - Bug #1459 (Closed): panic in msdosfshttps://bugs.dragonflybsd.org/issues/14592009-08-21T07:30:30Zpolachok
<p>I get a panic while trying to read a file from msdos filesystem with latest <br />master.</p>
<p><a class="external" href="http://omploader.org/vMjZzaw">http://omploader.org/vMjZzaw</a></p> DragonFlyBSD - Bug #1451 (Closed): mpt(4) out of datehttps://bugs.dragonflybsd.org/issues/14512009-08-12T22:44:35Zpolachok
<p>Our mpt was not updated since 2004, and it doesn't support my <SAS 3000 series, <br />8-port with 1068 -StorPort>. So I made a port of mpt driver from FreeBSD 8.</p>
<p><a class="external" href="http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/mpt">http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/mpt</a></p>
<p>RAID functionality wasn't tested, and I doubt whether is should really use <br />crit_enter()/crit_exit() (mpt.h:830).</p> DragonFlyBSD - Bug #1449 (Closed): AHCI panic on Intel 6321ESB AHCIhttps://bugs.dragonflybsd.org/issues/14492009-08-11T00:11:09Zpolachok
<p>I have a panic here with AHCI enabled. See screenshot here: <br /><a class="external" href="http://omploader.org/vMjRueA">http://omploader.org/vMjRueA</a>. Console gets completely unusable and fills with <br />garbage.</p>
<p>DragonFly dmesg with ahci disabled:<br /><a class="external" href="http://leaf.dragonflybsd.org/~polachok/dmesg.dfly">http://leaf.dragonflybsd.org/~polachok/dmesg.dfly</a></p>
<p>OpenBSD dmesg with ahci enabled:<br /><a class="external" href="http://leaf.dragonflybsd.org/~polachok/dmesg.obsd">http://leaf.dragonflybsd.org/~polachok/dmesg.obsd</a></p> DragonFlyBSD - Bug #1422 (Closed): Attansic/Atheros L2 FastEthernet driverhttps://bugs.dragonflybsd.org/issues/14222009-07-12T07:30:05Zpolachok
<p>This a port of FreeBSD ae(4) driver. Tested on Asus EEE 900.</p> DragonFlyBSD - Bug #1415 (Closed): ext3 unmount panichttps://bugs.dragonflybsd.org/issues/14152009-07-04T03:31:29Zpolachok
<p>I have a linux ext3 partition here. When trying to mount it, it doesn't work <br />(Bad file descriptor). When trying to unmount, panic appears. I don't have <br />firewire or serial here, so got a screenshot.</p> DragonFlyBSD - Bug #1414 (Closed): ehci - strange attach messagehttps://bugs.dragonflybsd.org/issues/14142009-07-04T03:16:34Zpolachok
<p>I noticed that ehci attach message is a bit strange, looks like it displays <br />some wrong memory address. Device works fine though.</p>
<p>usb2: companion controllers, 4 ports each: `\M-r\M-.\M-A\M^<code>(g\M-</code>\M-hA\M-^\M-<br />Mttyv0 \240\M-s\M-.\M-A\M^D(g\M-@(\^F\M-o\M-Mttyv1</p>
<p>Complete dmesg attached.</p>