DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082013-05-01T02:44:36ZDragonFlyBSD bugtracker
Redmine 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 #2252 (New): snd_hda not useable if loaded via /boot/loader.confhttps://bugs.dragonflybsd.org/issues/22522011-12-05T19:58:43Zxbit
<p>When loading snd_hda from /boot/loader.conf it is loaded, but cannot be used and configured. At least audio/moc does not work, it is unable to use the OSS interface. But after unloading and loading snd_hda again the sound card is useable.</p>
<p>As a workaround I added "/sbin/kldload snd_hda" to /etc/rc.local and then the soundcard is useable form audio/moc as OSS device.</p>
<p>snd_hda was the only sound kernel module that has been loaded via /boot/loader.conf.</p>
<p>Kernel configuration is GENERIC x86_64 (v2.12.0.23.gec4cf).</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 #1982 (New): There is no linuxulator on x86-64https://bugs.dragonflybsd.org/issues/19822011-02-04T21:53:04Zherrgard
<p>The linuxulator would have to be ported from x86.</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 #1714 (New): hwpmchttps://bugs.dragonflybsd.org/issues/17142010-04-03T18:59:28Zalexh
<p>I've put together Aggelos' original patches to import hwpmc from FreeBSD into <br />one place. Each file is prefixed with a number indicating the order of the <br />original submissions,<br /><a class="external" href="http://leaf.dragonflybsd.org/~alexh/hwpmc/">http://leaf.dragonflybsd.org/~alexh/hwpmc/</a></p>
<p>FWIW I think this is a nice thing to have and it would be nice if someone would <br />step up to firstly make the patches apply cleanly to master, then import them as <br />commits into git and if possible, make all the features work ;)</p>
<p>Cheers,<br />Alex</p>
<p>The original mail to submit@ was:<br />Hello,</p>
<p>this port of hwpmc ( start here: <a class="external" href="http://wiki.freebsd.org/PmcTools">http://wiki.freebsd.org/PmcTools</a> ) has<br />been stagnating on my hard disk for some months now. I'm finally<br />submitting it for inclusion because</p>
<p>a) the parts that work might be useful to someone and, more importantly,<br />b) complaints and bug reports might help get me off my butt and fix the<br /> remaining issues.</p>
<p>I've taken the time to split the patches so that people can review them<br />easily (the original freebsd code is submitted as .tgz since I'm not<br />interested in your review of that).</p>
<p>Please apply patches / extract tarballs in numerical order. I'll be a<br />bit surprised if there are no omissions/duplicate patches, but at least<br />my build test for world/kernel worked.</p>
<p>You will need these lines in your kernel config. See the manual pages<br />for usage examples.</p>
<p>options HWPMC_HOOKS<br />#device hwpmc</p>
<p>Testing status:</p>
<p>feature test status</p>
<p>global counting pmc tested, works<br />process counting pmc tested, works [0]<br />descendent tracking for<br />process counting pmc tested, works [0]<br />global sampling pmc possibly broken<br />process sampling pmc broken<br />logfile output untested<br />mapfilename untested<br />gprof execution profiles untested<br />SMP untested [1]<br />threaded (lwp) programs untested</p>
<p>[0] May still have bugs of course, test it out!<br />[1] Not even compile-tested</p> DragonFlyBSD - Bug #1538 (New): mountroot should probe file systemshttps://bugs.dragonflybsd.org/issues/15382009-09-28T01:48:34Zcorecode
<p>When mounting root from hammer, it is necessary to specify the file <br />system type in the vfs.root.mountfrom setting, otherwise the machine <br />will just be unhappy and issue the mountroot prompt (or rather, directly <br />go to ddb, see other bug report). This is very inconvenient and <br />irritating. The kernel should try all available file systems to mount root.</p>
<p>Possibly this should also be extended to mount itself, but this bug <br />report only deals with the mountroot issue.</p> DragonFlyBSD - Bug #1532 (New): jemalloc doesn't work on DragonFlyhttps://bugs.dragonflybsd.org/issues/15322009-09-25T19:10:21Zhasso
<p>jemalloc is a malloc(3) implementation from FreeBSD and for some reason <br />increasingly popular in various software pieces dealing ECMAscript and related <br />stuff. This means browsers (Firefox, Chrome), but also Gnash for example. <br />Unfortunately jemalloc doesn't work with DragonFly. Matt explained why some <br />time ago:</p>
<p><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/users/2009-04/msg00162.html">http://leaf.dragonflybsd.org/mailarchive/users/2009-04/msg00162.html</a></p> DragonFlyBSD - Bug #1313 (New): Signal code in kernel needs major overhaul (signal queues, si_cod...https://bugs.dragonflybsd.org/issues/13132009-03-13T15:04:10Zhasso
<p>Although our siginfo structure has a si_code member, we don't use it and <br />don't even have a defines related to it.</p>
<p><a class="external" href="http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html">http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html</a></p> DragonFlyBSD - Bug #679 (New): Netgraph backward compatibility for old *LEN constantshttps://bugs.dragonflybsd.org/issues/6792007-06-05T07:56:01Znant
<p>Maintain the old *LEN netgraph constants around for some time to allow<br />the building of earlier mpd (Multi-link PPP Daemon).</p>
<p>Pointed out by: Alexander Motin <<a class="email" href="mailto:mav@freebsd.org">mav@freebsd.org</a>><br />Obtained from: FreeBSD</p>
<p>BTW: Do we need a BURN_BRIDGES kernel option?</p>
<p>Thanks,<br />Nuno</p> DragonFlyBSD - Bug #600 (New): /sys/libkern/karc4randomhttps://bugs.dragonflybsd.org/issues/6002007-04-11T17:14:04Zrobin_carey5
<p>What is the point of keeping/using the in-kernel arc4<br />random number generator when you already have a very<br />good/superior IBAA/L15 random number generator.</p>
<p>If you need a u_int32_t quantity then simply add a<br />function to /sys/kern/kern_nrandom.c to produce a<br />u_int32_t.</p>
<p>--</p>
<p>Some issues with /sys/libkern/karc4random.c :</p>
<p>(a) If you intend to keep /sys/libkern/karc4random.c I<br />recommend you make a modification to it to improve<br />performance: Every time the karc4_random() function is<br />called it calls getmicrotime(), to check the time, and<br />it also checks the number of runs made, to see if it<br />should reseed itself. You can make a big performance<br />improvement by removing this call to getmicrotime()<br />and instead simply checking the number of runs to<br />determine when it should reseed itself.</p>
<p>(b) The karc4random.c file uses u_int8_t types for<br />arc4_i, arc4_j and arc4_t so there is no need for the<br />% 256 operation - another performance improvement.</p>
<p>(c) In arc4_init() you are throwing away 256*4 bytes<br />of output, when you only need to throw away the first<br />256 bytes of output.</p>
<p>Sincerely,<br />R Carey.</p>
<pre><code>_<em><i></em></i>__<em>_</em>_______________________________________________<br />Yahoo! Answers - Got a question? Someone out there knows the answer. Try it<br />now.<br /><a class="external" href="http://uk.answers.yahoo.com/">http://uk.answers.yahoo.com/</a></code></pre>