DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082016-02-06T13:09:05ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #2887 (New): Missing extattr_namespace_to_string and extattr_string_to_namespa...https://bugs.dragonflybsd.org/issues/28872016-02-06T13:09:05Zrubenkruben@rubenkerkhof.com
<p>Hi,</p>
<p>I'm working on porting Burp (<a class="external" href="http://burp.grke.org">http://burp.grke.org</a>) to DragonFly.<br />I've been looking into what it would take for it to support backing up extended attributes.</p>
<p>Burp uses the extattr_namespace_to_string and extattr_string_to_namespace functions, which FreeBSD has in libutil.h and NetBSD in sys/extattr.h. DragonFlyBSD misses those however.</p>
<p>Would it be possible to add those functions?</p> DragonFlyBSD - Bug #2882 (New): bridge sends packets from individual interfaceshttps://bugs.dragonflybsd.org/issues/28822016-01-09T20:43:59Zarcade@b1t.namearcade@b1t.name
<p>Hi, recently tried configuring a bridge/stp alongside freebsd host with bridge. Looks like DragonFly version has some bugs in it... Dunno whether they are serious one or not. From time to time it loses connectivity and falls back to "blocking". Much more frequently following situation occurs:</p>
<p>FreeBSD (net.link.bridge.log_stp=1):</p>
<p>Jan 9 22:08:45 limbo kernel: arp: 172.29.1.195 moved from b6:02:35:28:d0:b1 to d4:3d:7e:48:ab:9d on bridge0<br />Jan 9 22:28:41 limbo kernel: arp: 172.29.1.195 moved from b6:02:35:28:d0:b1 to d4:3d:7e:48:ab:9d on bridge0</p>
<p>DragonFly (net.link.bridge.debug=1):</p>
<p>Jan 9 22:07:36 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:07:36 probe kernel: 02:3b:77:1f:48:00 52:54:00:12:34:56 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:08:45 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:10:40 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:12:13 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:12:13 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:25:43 probe kernel: ff:ff:ff:ff:ff:ff 84:8e:df:11:d2:e2 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:25:44 probe kernel: ff:ff:ff:ff:ff:ff 84:8e:df:11:d2:e2 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:27:11 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:27:11 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:27:32 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:27:32 probe kernel: 02:3b:77:1f:48:00 52:54:00:12:34:56 type 0608 lla b6:02:35:28:d0:b1<br />Jan 9 22:28:41 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1</p>
<p>re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500<br /> options=19<RXCSUM,VLAN_MTU,VLAN_HWTAGGING><br /> inet6 fe80::d63d:7eff:fe48:ab9d%re0 prefixlen 64 scopeid 0x1<br /> ether d4:3d:7e:48:ab:9d<br /> media: Ethernet autoselect (1000baseT <full-duplex>)<br /> status: active</p>
<p>bridge0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br /> inet6 fe80::b402:35ff:fe28:d0b1%bridge0 prefixlen 64 scopeid 0x3<br /> inet 172.29.1.195 netmask 0xffffff00 broadcast 172.29.1.255<br /> ether b6:02:35:28:d0:b1<br /> priority 32768 hellotime 2 fwddelay 15 maxage 20<br /> member: tap0 flags=3<LEARNING,DISCOVER><br /> member: re0 flags=37<LEARNING,DISCOVER,STP,DESIGNATED,ROOT><br /> port 1 priority 128 pathcost 55 forwarding<br /> bondweight 1<br /> designated root: 8000b6023528d0b1<br /> designated bridge: 8000b6023528d0b1<br /> designated cost: 54<br /> designated port: 0</p>
<p>There's no hints on how bridge should be set up also. The recipe that works for me flawlessly is:</p>
<p>1. Clone one bridge interface:<br /> cloned_interfaces=bridge0</p>
<p>1. Bring child interfaces up:<br /> ifconfig_re0=up</p>
<p>2. Set up inet on the bridge in first configuration directive:<br /> ifconfig_bridge0=DHCP<br />or:<br /> ifconfig_bridge0='inet 172.29.1.100/24'</p>
<p>3. Add other interfaces:<br /> ifconfig_bridge0_alias0='addm re0 stp re0'</p>
<p>Just to pinpoint - FreeBSD guide page is fine about bridges except that DHCP will not work in aliases.</p> DragonFlyBSD - Bug #2877 (New): sed fails when working with UTF-8 locale and non-UTF symbolshttps://bugs.dragonflybsd.org/issues/28772015-12-30T19:20:47Zarcade@b1t.namearcade@b1t.name
<p>I.e. when some file has a line with upper ASCII symbols:</p>
<ul>
<li>and L<E1>szl<F3> N<E9>meth (Hunspell). Portions created by the Initial Developers</li>
</ul>
<p>and LANG is set to *.UTF8 running sed on that file results in:</p>
<p>+ /usr/bin/sed -i.bak -e 's|%%LOCALBASE%%|/usr/local|g' /tmp/ports/www/firefox/firefox-43.0.1/extensions/spellcheck/hunspell/glue/mozHunspell.cpp<br />sed: RE error: Illegal byte sequence</p>
<p>Unsetting lang makes sed silently accept the file.</p> DragonFlyBSD - Bug #2859 (New): Installer configuration menu always highlights "Select timezone",...https://bugs.dragonflybsd.org/issues/28592015-12-02T21:54:29Zcgagcurtis@curtis.io
<p>If you finish finish step 5, when you return to the menu, step 1 will be selected. Ideally it would have step 6 selected.</p> DragonFlyBSD - Bug #2858 (New): Installer "Local or UTC" question should have "No" selected by de...https://bugs.dragonflybsd.org/issues/28582015-12-02T21:18:58Zcgagcurtis@curtis.io
<p>The installer suggests selecting "No" unless you know what you're doing. I think it should should have "No" selected as the default answer. I'll try to submit a patch for this at some point, but I thought I should write it down.</p>
<p>Not a real bug, more a minor UX suggestion, wasn't sure how to classify this so sorry if it's wrong.</p> DragonFlyBSD - Submit #2790 (New): filedesc softrefs increment code factoringhttps://bugs.dragonflybsd.org/issues/27902015-02-21T12:00:29Zdclinkdevnexen@gmail.com
<p>Just putting locking + sifters field update in common function ...</p> DragonFlyBSD - Bug #2680 (New): boot0cfg update makes box unbootablehttps://bugs.dragonflybsd.org/issues/26802014-06-07T17:56:45Zherrgard
<p>If I hit any of the F-keys box will not boot next time. Laptop says "Bootable device not found".</p>
<p>Workaround: install boot0 in noupdate mode:</p>
<blockquote>
<p>fdisk -I da0<br />boot0cfg -B -o noupdate da0</p>
</blockquote>
<p>Only running boot0cfg and not fdisk does not fix it. Warning: fdisk may mess up your fancy slice setup.</p> DragonFlyBSD - Bug #2552 (New): hammer recovery should indicate progresshttps://bugs.dragonflybsd.org/issues/25522013-05-01T02:44:36Zphma
<p>I'm running hammer recover on a 55 GB partition of an IDE drive and it's been running for about a day. I have no idea how long it'll take. It would be a good idea if, every few minutes, hammer recover would output how many blocks it's read and how many are left, or just a percentage.</p> DragonFlyBSD - Bug #2529 (New): Sundance network adapter is not detected and attachedhttps://bugs.dragonflybsd.org/issues/25292013-03-21T14:13:29Zkworrc.kworr@gmail.com
<p>I have one of those ASUS NX1001 cards with Sundance controller. Current version doesn't correctly detects it.</p>
<p>pciconf -lv (snip):<br />none6@pci0:2:6:0: class=0x020000 card=0x82131043 chip=0x020013f0 rev=0x31 hdr=0x00<br /> vendor = 'Sundance Technology Inc / IC Plus Corp'<br /> device = 'IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY'<br /> class = network<br /> subclass = ethernet</p>
<p>In current FreeBSD (RELENG_9) it is detected as:</p>
<p>ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2<br />ste0: Ethernet address: 00:26:18:eb:37:85<br />miibus1: <MII bus> on ste0<br />ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus1<br />ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto</p> DragonFlyBSD - Bug #2403 (New): newfs -E doesn't handle /dev/serno device names properlyhttps://bugs.dragonflybsd.org/issues/24032012-08-17T12:07:45Zftigeot
<p>Trying to run this command fails:</p>
<pre><code>newfs_hammer -E -L USR_OBJ /dev/serno/00000000112233445566</code></pre>
<pre><code>Device:/dev/serno/00000000112233445566 (kern.cam.da.rno/00000000112233445566.trim_enabled) does not support the TRIM command<br /> usage: newfs_hammer -L label [-Ef] [-b bootsize] [-m savesize] [-u undosize]<br /> [-V version] special ...</code></pre>
<p>The only trim_enabled sysctls id are of the form<br /> kern.cam.da.0.trim_enabled<br /> kern.cam.da.1.trim_enabled<br /> kern.cam.da.2.trim_enabled<br /> etc...</p>
<p>It seems newfs -E only expects drive names to be of the form /dev/daX<br />TRIM options in other utilities such as fdisk or disklabel may have the same issue</p> DragonFlyBSD - Bug #2095 (New): Running installer post-install: Unsupported DFUI transport ''https://bugs.dragonflybsd.org/issues/20952011-06-26T16:20:49Zgreenrd
<p>If you try to run installer on an installed system to reconfigure it, you get:</p>
<p>Starting installer. /etc/pfi.conf not found, starting interactive install.<br />Unsupported DFUI transport ''.</p> DragonFlyBSD - Bug #2020 (New): Port brcm80211 driver from Linux to DragonFly BSDhttps://bugs.dragonflybsd.org/issues/20202011-03-06T06:54:10Zstuder
<p>In September 2010, Broadcom released a full opensource version under BSD licence <br />of their driver for part of their WLAN hardware (BCM43224, BCM43225, BCM4313 <br />(PCIe NIC)).</p>
<p>That would be so nice if this could be added to DragonFly BSD.</p>
<p>For more information, see :<br />- <a class="external" href="http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418">http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418</a><br />- <a class="external" href="http://wireless.kernel.org/en/users/Drivers/brcm80211">http://wireless.kernel.org/en/users/Drivers/brcm80211</a></p> DragonFlyBSD - Bug #1882 (New): Idea for handling new USB vendor/device codeshttps://bugs.dragonflybsd.org/issues/18822010-10-20T17:22:04Zbmk
<p>This is just an idea / wish.</p>
<p>Have a config file called /etc/usb_hotwire.conf</p>
e.g.:
<ol>
<li>This file allows you to map a new unsupported usb vendor/device code</li>
<li>to an existing usb vendor/device code supported by a driver.</li>
<li>File Format:</li>
<li><unsupported vendor code>:<unsupported device code> <supported vendor<br />code>:<supported device code></li>
</ol>
<ol>
<li>The following makes my unsupported USB wireless adapter use the same driver<br />(rum) as a D-Link DWL-G122</li>
</ol>
<p>0x1044:0x2573 0x07d1:0x3c03</p> DragonFlyBSD - Bug #725 (In Progress): 'make distribution' fails w/'ro' /usr/objhttps://bugs.dragonflybsd.org/issues/7252007-07-10T09:42:05Zc.turner
<p>This seems to choke on sendmail from a ~1wk build<br />(no code changes on this part of the tree it seems)</p>
<p>not sure if it is 'supposed to work' or<br />for how long it has been broken, so I didn't investigate further..</p>
<p>basically, trying to use a -HEAD machine to build out jail<br />images from a release machine over ro nfs..</p>
<p>Thanks,</p>
<p>- Chris</p> DragonFlyBSD - Bug #285 (Feedback): interrupt latency with re without ip address configuredhttps://bugs.dragonflybsd.org/issues/2852006-08-07T06:00:07Zthomas.nikolajsen
<p>Playing sound using pcm(4)/snd(4) gives bad quality: hiss and hops, like sound isn't playing for very short time periods.</p>
<p>This is experienced:<br /> - not having SMP in kernel config (eg GENERIC)<br /> - from dfly-1.5 26th December '05 (24th is ok using kernels from chlamydia);<br />including HEAD.</p>
<p>dfly-1.4 is ok, including 1.4.4.</p>
<p>Using audio/mpg123 for MP3, 'cp test.raw /dev/dspW' or pcmplay for decoded sound.<br />Buffering audio data with mpg123 -b doesn't sound like making any difference.</p>
<p>CPU load doesn't sound like making any difference.<br />Problem experienced on several systems, using snd_via8233 and snd_ich.</p>
<p>No X11 used.</p>
<pre><code>-thomas</code></pre>