DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082022-01-30T10:33:08ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3311 (New): TrueCrypt support may cause kernel crashhttps://bugs.dragonflybsd.org/issues/33112022-01-30T10:33:08Zarcade@b1t.namearcade@b1t.name
<p>When working on tcplay:hammer2 device kernel can crash. Screenshots attached...</p> DragonFlyBSD - Bug #3132 (New): unifdef minedhttps://bugs.dragonflybsd.org/issues/31322018-04-27T03:34:07Zbcallah
<p>Hi --</p>
<p>The included diff unifdefs the code in bin/mined. The #ifdef'd out paths probably would not even compile with the current #includes anyway.<br />No binary change. I have been running this on OpenBSD/amd64 and OpenBSD/armv7 for a while now. The DragonFly build is also happy with this.</p> DragonFlyBSD - Bug #3101 (New): PFI CGI install not working in dragonflybsd 5.0.1 USB installhttps://bugs.dragonflybsd.org/issues/31012017-11-12T08:47:51Zbnegre82
<p>Hello,<br />I tried to install dragonflybsd on a PCengines APU2 with the CGI installer interface. I have to do this because there is just a serial console and normal installer don't work.<br />I added a pfi.conf file in /etc/pfi.conf to the image, but no web interface comes.<br />It failed because /usr/local/sbin/thttpd_wrapper is not on the USB install image (dfly-x86_64-5.0.1_REL.img.bz2)</p>
<p>The webserver is called by the pfi service at startup (etc/rc.d/pfi) line 203<br /> if [ "X$pfi_frontend" = "Xcgi" ]; then<br /> echo "Starting thttpd..." <br /> /usr/local/sbin/thttpd_wrapper &<br /> fi</p>
<p>Can you fix this for the next release ?<br />How can I add the web server to the install image ?</p>
<p>Regards,<br />Bertrand</p> DragonFlyBSD - Bug #3024 (New): sys/dev/netif/wi/if_wi.c:1090]: (style) Redundant conditionhttps://bugs.dragonflybsd.org/issues/30242017-04-11T18:56:08Zdcb
<p>sys/dev/netif/wi/if_wi.c:1090]: (style) Redundant condition: params. '!params || (params && params.ibp_flags&IEEE80211_BPF_CRYPTO)' is equivalent to '!params || params.ibp_flags&IEEE80211_BPF_CRYPTO'</p>
<p>Source code is</p>
<pre><code>if ((wh->i_fc[1] & IEEE80211_FC1_PROTECTED) &&<br /> (!params || (params && (params->ibp_flags & IEEE80211_BPF_CRYPTO)))) {</code></pre> 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 #2878 (New): [fix] CCVER problem when using clang and cpu extensions (intrinsics)https://bugs.dragonflybsd.org/issues/28782015-12-30T20:46:33Zarcade@b1t.namearcade@b1t.name
<p>Ok, I'm trying to compile dri with clang37. When I setting CCVER to clang37 build stops on:</p>
<p>In file included from utils.c:37:<br />In file included from ../../../../../src/mesa/main/macros.h:36:<br />../../../../../src/util/rounding.h:33:10: fatal error: 'xmmintrin.h' file not found<br />include <xmmintrin.h><br /> ^<br /> 2 warnings and 1 error generated.</p>
<p>The file is present, but as per /etc/defaults/compiler.conf:</p>
<p>STD_INCOPT="-nostdinc -iprefix ${INCPREFIX} -iwithprefixbefore /usr/include" <br />DPORT_GCC_STD_INCOPTXX="-isystem /usr/local/lib/${CCVER}/include/c++ \<br /> -isystem /usr/local/lib/${CCVER}/include/c++/${MACHARCH}-portbld-dragonfly${MACHREL}" <br />DPORT_CLANG_STD_INCOPTXX="-cxx-isystem /usr/include/c++/5.0"</p>
<p>...</p>
<p>clang37_INCOPT=${STD_INCOPT}<br />clang37_INCOPTCXX=${DPORT_CLANG_STD_INCOPTXX}</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 #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 #1947 (New): GA-880GM-UD2H (rev. 1.3) AHCI fails to detect disks at the end of...https://bugs.dragonflybsd.org/issues/19472010-12-31T22:46:34Zeocallaghan
<p>Attached is the verbose boot of the machine when two 1TB disks are in a RAID 1<br />behind the controller. If the AMD RAID controller is set to AHCI mode the disks<br />show fine.</p>
<ul>
<li>Background:</li>
</ul>
<p>Board:<br /><a class="external" href="http://www.gigabyte.com/products/product-page.aspx?pid=3475#sp">http://www.gigabyte.com/products/product-page.aspx?pid=3475#sp</a></p>
<p>Southbridge chipset data sheet:<br /><a class="external" href="http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBIQFjAA&url=http%3A%2F%2Fdeveloper.amd.com%2Fassets%2F45215_sb710_ds_pub_1.25.pdf&rct=j&q=AMD%20SB710%20raid%20controller&ei=6-EdTb3dDZHwvwPp9-XwDQ&usg=AFQjCNH7gThMfcsRKvLicnmwBIJR1lSbRQ&cad=rja">http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBIQFjAA&url=http%3A%2F%2Fdeveloper.amd.com%2Fassets%2F45215_sb710_ds_pub_1.25.pdf&rct=j&q=AMD%20SB710%20raid%20controller&ei=6-EdTb3dDZHwvwPp9-XwDQ&usg=AFQjCNH7gThMfcsRKvLicnmwBIJR1lSbRQ&cad=rja</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 #1148 (In Progress): BCM4311 wireless network adapter detected but not functionalhttps://bugs.dragonflybsd.org/issues/11482008-10-09T12:27:01Zarchimedes.gaviola
<p>Hi,</p>
<p>I have a mini-PCI wireless network adapter on my laptop that wasn't<br />detected on DragonFly 2.0.0 during installation. Since it wasn't<br />detected, what I did is performing the steps in the<br />bwi(4) manual <a class="external" href="http://leaf.dragonflybsd.org/cgi/web-man?command=bwi&section=ANY">http://leaf.dragonflybsd.org/cgi/web-man?command=bwi&section=ANY</a><br />and download the firmware at<br /><a class="external" href="http://leaf.dragonflybsd.org/~sephe/bwi/v3.tbz">http://leaf.dragonflybsd.org/~sephe/bwi/v3.tbz</a>. Now, the driver were<br />detected (Broadcom BCM4311) but seems not functional. It doesn't show<br />up after invoking ifconfig. Below is the dmesg output:</p>
<p>device_probe_and_attach: bwi0 attach returned 6<br />Preloaded elf module "/modules/if_bwi.ko" at 0xc07b93c8.<br />bwi0: <Broadcom BCM4311 802.11 Wireless Lan> mem 0x31300000-0x31303fff<br />irq 11 at device 0.0 on pci1<br />bwi0: BBP: id 0x4311, rev 0x2, pkg 0<br />bwi0: MAC rev 13 is not supported<br />bwi0: no MAC was found</p>
<p>And as I try looking at the /usr/src/sys/dev/netif/bwi/if_bwi.c code,<br />BCM4311 is part of the supported device</p>
<pre><code>{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM4311,<br /> "Broadcom BCM4311 802.11 Wireless Lan" },</code></pre>
<p>Thanks,<br />Archimedes</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>