DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082019-09-18T13:28:07ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3205 (Feedback): Go compiler net test failinghttps://bugs.dragonflybsd.org/issues/32052019-09-18T13:28:07ZAnonymous
<p>A recent commit appears to have broken the net test for the Go compiler:<br /><a class="external" href="https://build.golang.org/log/58be31cfd1a92ba9582fdf33e01f79e03184e59b">https://build.golang.org/log/58be31cfd1a92ba9582fdf33e01f79e03184e59b</a></p>
<p>This was working on commit be02f354 and started failing when I upgraded to b7d3e1.</p> DragonFlyBSD - Bug #2828 (New): On AMD APUs and Bulldozer CPUs, the machdep.cpu_idle_hlt sysctl s...https://bugs.dragonflybsd.org/issues/28282015-06-13T23:21:11Zvadaszi
<p>Power usage of a default install is unnecessarily high on current AMD CPUs. Setting the default value of the machdep.cpu_idle_hlt sysctl on these CPUs to 3 by default allows for significant power savings.</p>
<p>I'm not sure how setting machdep.cpu_idle_hlt=3 affects power usage on AMD Family 10h CPUs (e.g. Phenom CPUs).</p>
<p>Some quick benchmarking should be done if possible, to compare the performance difference.</p> DragonFlyBSD - Bug #2577 (New): virtio-blk iops performance is cpu limited on high end deviceshttps://bugs.dragonflybsd.org/issues/25772013-08-01T20:59:44Zgjs278gjs278@yahoo.com
<p>Qemu 1.5.2 on Gentoo AMD64 kernel 3.10.4 host with an i7 980x processor at 4.2ghz</p>
<p>qemu-system-x86_64 -machine accel=kvm -cpu host -drive file=/dev/fioa3,if=virtio,cache=none,aio=native -balloon virtio -smp 6 -m 6144M</p>
<p>/dev/fioa3 is a 160gb slc fusion-io card</p>
<p>DragonFlyBSD 3.4.2-RELEASE is the guest OS</p>
<ol>
<li>/tmp/rr1 /dev/vbd0<br />Device /dev/vbd0 bufsize 512 limit 10.800GB nprocs 32<br />randrand 1.001s 24293 loops = 41.202uS/loop<br />randrand 1.002s 24384 loops = 41.072uS/loop<br />randrand 1.001s 24633 loops = 40.640uS/loop</li>
</ol>
<ol>
<li>/tmp/rr1 /dev/vbd0 4096<br />Device /dev/vbd0 bufsize 4096 limit 10.800GB nprocs 32<br />randrand 1.001s 24333 loops = 41.119uS/loop<br />randrand 1.002s 24389 loops = 41.052uS/loop<br />randrand 1.001s 24367 loops = 41.093uS/loop</li>
</ol>
<ol>
<li>/tmp/rr1 /dev/vbd0 16384<br />Device /dev/vbd0 bufsize 16384 limit 10.800GB nprocs 32<br />randrand 1.001s 21006 loops = 41.619uS/loop<br />randrand 1.002s 21167 loops = 41.348uS/loop<br />randrand 1.001s 20520 loops = 48.850uS/loop</li>
</ol>
<p>cpu usage on the host nears 100% while /tmp/rr1 is running. at nprocs 32, the device should be capable of at least 100k iops. the same 25k limit is seen using an ssd array as well.</p> DragonFlyBSD - Bug #2496 (New): NTFS malloc limit exceededhttps://bugs.dragonflybsd.org/issues/24962013-01-21T22:15:44Zplasmobplasmob@gmail.com
<p>I core dumped on NTFS malloc limit exceeded error. /var/crash/core.0.txt is here <a class="external" href="http://www.pastebin.ca/2305534">http://www.pastebin.ca/2305534</a></p> DragonFlyBSD - Submit #2438 (Feedback): TRIM fixeshttps://bugs.dragonflybsd.org/issues/24382012-10-22T04:59:20ZAnonymous
<p>This patch is to fix bugs associated with TRIM.</p>
<p>If trim is on as a option, display that when typing "mount".</p>
<p>Change post-trim ffs_blkfree_cg() to use taskqueue_swi_mp and get mp token when modifying freemap.</p>
<p>Make sure TRIM works with softdep. Stash a copy of that vnode's mount point in the ufs inode so that if we are using softdep, we can get access to the mount point through the faked up inode (created in freeblocks). The original mount point path (ip->i_devvp->v_mount->mnt_flag) doesn't have the mount point options.</p>
<p>Tim</p> DragonFlyBSD - Bug #2416 (New): '.' entry can be removed on mounted nfs filesystemhttps://bugs.dragonflybsd.org/issues/24162012-09-01T09:18:14Zftigeot
<p>I use a shared /usr/pkgsrc/packages on various DragonFlyBSD machines</p>
<p>Just after doing a "rm *" to remove accumulated cruft in packages/All<br />on a client machine, I noticed the "." entry had disappeared.</p>
<p>On the client machine I typed the command on, ls(1) only shows a unique '..'<br />entry in /usr/pkgsrc/packages/All. /usr/pkgsrc/packages doesn't<br />contain a '.' entry anymore. None of its subdirectories do.</p>
<p>On other client machine, the '.' entry has also disappeared from<br />/usr/pkgsrc/packages and all its subdirectories.</p>
<p>The server still contains '.' and '..' entries in the exported directory and<br />all its subdirectories.</p>
<p>Clients and server machines are all running DragonFly-3.1.<br />mount points and all of is</p> DragonFlyBSD - Bug #2391 (In Progress): System lock with ahci and acpi enabled on ATI RS690 chips...https://bugs.dragonflybsd.org/issues/23912012-06-24T20:41:54Zjorisgiojoris@giovannangeli.fr
<p>Page fault during boot with ahci and acpi.<br />Kernel boot without ahci but locks in userspace after a fixed time.<br />Page fault without acpi but with ahci.</p> DragonFlyBSD - Bug #2370 (New): panic: ffs_valloc: dup allochttps://bugs.dragonflybsd.org/issues/23702012-05-16T21:40:41Zmarino
<p>core text file located: <a class="external" href="http://leaf.dragonflybsd.org/~marino/core/core.ffs_valloc_dup_alloc.txt">http://leaf.dragonflybsd.org/~marino/core/core.ffs_valloc_dup_alloc.txt</a><br />core dump located on leaf, ~/marino/crash</p>
<p>uname: DragonFly v3.1.0.634.gc6fd7-DEVELOPMENT <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a>: Sat May 5 09:02:18 CEST 2012 <a class="email" href="mailto:root@dracofly.synsport.com">root@dracofly.synsport.com</a>:/usr/obj/usr/src/sys/GENERIC</p>
<p>backtrace:<br />Unread portion of the kernel message buffer:<br />mode = 041777, inum = 4, fs = /mech<br />panic: ffs_valloc: dup alloc<br />cpuid = 1<br />Trace beginning at frame 0xe4b8b838<br />panic(ffffffff,1,c07290b3,e4b8b86c,d867f860) at panic+0x1a8 0xc039af00 <br />panic(c07290b3,43ff,4,defc10d4,e4b8b8f0) at panic+0x1a8 0xc039af00 <br />ffs_valloc(dee285d8,81a4,e00929e0,e4b8b8f0,c82dcc10) at ffs_valloc+0x518 0xc0542ad4 <br />ufs_makeinode(e4b8ba8c,d867f97c,dee285d8,dee67460,e4b8ba2c) at ufs_makeinode+0x71 0xc0556327 <br />ufs_create(e4b8ba38,e4b8ba68,c04139c0,e4b8ba38,c07d5b38) at ufs_create+0x2c 0xc0556692 <br />ufs_vnoperate(e4b8ba38,c07d5b38,dee67460,dee67460,c04043ef) at ufs_vnoperate+0x16 0xc0555bb6 <br />vop_old_create(dee67460,dee285d8,e4b8bbf0,e4b8ba8c,e4b8bb44) at vop_old_create+0x5b 0xc04139c0 <br />vop_compat_ncreate(e4b8badc,e4b8bad0,c0555bb6,e4b8badc,e4b8bb10) at vop_compat_ncreate+0x11d 0xc03f9813 <br />vop_defaultop(e4b8badc,e4b8bb10,c0412061,e4b8badc,c07d5c98) at vop_defaultop+0x16 0xc03f7f72 <br />ufs_vnoperate(e4b8badc,c07d5c98,dee67460,c7e6f2f8,0) at ufs_vnoperate+0x16 0xc0555bb6 <br />vop_ncreate(dee67460,e4b8bc74,dee285d8,e4b8bbf0,e00929e0) at vop_ncreate+0x64 0xc0412061 <br />vn_open(e4b8bc74,e3731f08,602,1a4,c77f211c) at vn_open+0x183 0xc0410eab <br />kern_open(e4b8bc74,601,1b6,e4b8bcf0,e372f7a8) at kern_open+0xa3 0xc040e0c7 <br />sys_open(e4b8bcf0,e4b8bd00,c,c03a6652,d867f860) at sys_open+0x54 0xc040e3a9 <br />syscall2(e4b8bd40) at syscall2+0x270 0xc067745c <br />Xint0x80_syscall() at Xint0x80_syscall+0x36 0xc0646466 <br />Debugger("panic")</p> DragonFlyBSD - Bug #2358 (In Progress): DFBSD v3.0.2.32.g928ca - panic: hammer: insufficient undo...https://bugs.dragonflybsd.org/issues/23582012-04-29T11:43:04Ztuxillo
<p>Hi,</p>
<p>HAMMER filesystem recently created on a LVM stripe of 5 disks. Box has 1GB with no swap.</p>
<p>databank# lvs<br /> LV VG Attr LSize Origin Snap% Move Log Copy% Convert<br /> lv_root main <del>wi-a</del> 186.17g</p>
<p>I got no dump but I have located which panic in the code was hit: <a class="external" href="http://pkgbox64.dragonflybsd.org/xref/DragonFly-master/sys/vfs/hammer/hammer_redo.c#91">http://pkgbox64.dragonflybsd.org/xref/DragonFly-master/sys/vfs/hammer/hammer_redo.c#91</a></p>
<p>Backtrace function call is:</p>
<p>panic()<br />panic()<br />hammer_generate_redo()<br />hammer_vop_write()<br />vop_write()<br />vn_write()<br />kern_pwritev()<br />sys_extpwrite()<br />syscall2()<br />Xint0x80_syscall()</p>
<p>Image: <a class="external" href="http://leaf.dragonflybsd.org/~tuxillo/archive/pics/panic_fifo.jpg">http://leaf.dragonflybsd.org/~tuxillo/archive/pics/panic_fifo.jpg</a></p>
<p>After rebooting and trying to mount again the HAMMER FS:</p>
<p>databank# mount -a<br />hammer: mount on /mnt/safe: Result too large</p>
<p>And dmesg shows:</p>
<p><abbr title="SAFE">HAMMER</abbr> recovery check seqno=00d791fe<br /><abbr title="SAFE">HAMMER</abbr> recovery range 30000000070ef490-3000000004a90000<br /><abbr title="SAFE">HAMMER</abbr> recovery nexto 3000000004a90000 endseqno=00e638f5<br /><abbr title="SAFE">HAMMER</abbr> recovery undo 30000000070ef490-3000000004a90000 (488246128 bytes)(RW)<br /><abbr title="SAFE">HAMMER</abbr> Found REDO_SYNC 30000000070ef490<br /><abbr title="SAFE">HAMMER</abbr> Ignoring extra REDO_SYNC records in UNDO/REDO FIFO.<br /><abbr title="SAFE">HAMMER</abbr> recovery complete<br /><abbr title="SAFE">HAMMER</abbr> recovery redo 30000000070ef490-3000000004a90000 (488246128 bytes)(RW)<br /><abbr title="SAFE">HAMMER</abbr> Find extended redo 30000000070ef490, 0 extbytes<br /><abbr title="SAFE">HAMMER</abbr> Find extended redo failed 34, unable to run REDO<br /><abbr title="SAFE">HAMMER</abbr> End redo recovery</p>
<p>I've activated swap and I'm going to try to reproduce it again and see if I can get a dump, but any tip would be appreciated :)</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #2113 (New): nmalloc threaded program fork leakhttps://bugs.dragonflybsd.org/issues/21132011-08-12T02:25:48Zvsrinivasvsrinivas@ops101.org
<p>When a threaded program forks, magazines held by threads other than the forkee<br />should be released along with their contents. Currently we leak those buffers.</p> DragonFlyBSD - Bug #1579 (Feedback): dfly 2.4.1 does not like HP DL360G4p and Smart Array 6400 wi...https://bugs.dragonflybsd.org/issues/15792009-10-19T20:57:34Ztomaz.borstnar
<p>Hello!</p>
<pre><code>I have a HP DL360G4p machine with 5 gigs of RAM, internal SATA disk and HP SmartArray 6400 controller (2 channels) with <br />6400EM card (additional 2 channels attached as daughter card) with MSA20 enclosure with SATA disks - configured as 4 <br />volumes. Install went fine, but dmesg prints some errors (full dmesg output attached), but here are relevant parts:</code></pre>
<p>bge0: <Broadcom BCM5704C Dual Gigabit Ethernet> mem 0xfddf0000-0xfddfffff irq 7 at device 2.0 on pci2<br />bge0: CHIP ID 0x21000000; ASIC REV 0x02; CHIP REV 0x21; PCI-X<br />alignment check failed<br />miibus0: <MII bus> on bge0<br />brgphy0: <BCM5704 10/100/1000baseT PHY> on miibus0<br />brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto<br />bge0: MAC address: 00:15:60:0f:b0:e8<br />bge1: <Broadcom BCM5704C Dual Gigabit Ethernet> mem 0xfdde0000-0xfddeffff irq 7 at device 2.1 on pci2<br />bge1: CHIP ID 0x21000000; ASIC REV 0x02; CHIP REV 0x21; PCI-X<br />alignment check failed<br />alignment check failed<br />miibus1: <MII bus> on bge1<br />brgphy1: <BCM5704 10/100/1000baseT PHY> on miibus1<br />brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto<br />bge1: MAC address: 00:15:60:0f:b0:e7</p>
<p>And...</p>
<p>CAM: Configuring 5 busses<br />CAM: finished configuring all busses (-2 left)<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xc015423d arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xc015423d arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xc015423d arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xc015423d arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xc015423d arg=0<br />Giving up, interrupt routing is probably hosed</p>
<p>But ciss is seen:<br />ciss0: <HP Smart Array 6400> port 0x5000-0x50ff mem 0xfdff0000-0xfdff1fff irq 7 at device 4.0 on pci11<br />ciss1: <HP Smart Array 6400 EM> port 0x5400-0x54ff mem 0xfdf70000-0xfdf71fff irq 5 at device 5.0 on pci11</p>
<p>Anything I can help to test?</p>
<p>Tomaž</p> DragonFlyBSD - Bug #1390 (In Progress): Use id_t type for {get,set}priority()https://bugs.dragonflybsd.org/issues/13902009-05-27T00:25:04ZAnonymous
<p>Salute!</p>
<p>Both get- and set-priority() functions take a `who' argument that may refer to <br />process ID, group ID or a user ID depending on the situation. The id_t type,<br />which is already available in our src tree, guarantees that it's large enough to<br />hold pid, gid, etc.</p>
<p>The attached patch replaces `int' with `id_t' wherever appropriate. I have done<br />a build{world,kernel} and install{world,kernel} and I don't broke anything. Plus<br />some test cases I have, continue to pass.</p>
<p>If anyone objects to this patch speak now or forever hold your peace!</p>
<p>Cheers,<br />Stathis</p> DragonFlyBSD - Bug #847 (Feedback): processes getting stuck on mount pointhttps://bugs.dragonflybsd.org/issues/8472007-11-23T07:03:06Zcorecode
<p>Hey,</p>
<p>I just experienced the infamous ``cache_lock: blocked on 0xd591d418 ""'' message. Checking why the process got stuck revealed that the lock is actually being held by another process which is in the process of doing a lstat(2) on /mnt, a nfs mount which server went away. The stuck process is doing the same, fwiw.</p>
<p>So here it is not a namecache bug, but rather an artifact of nfs being stuck. Anoying nevertheless. Anybody have a clue how to fix that? Yea, mount with -intr. Why don't we do that per default?</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #781 (In Progress): fdisk uses wrong geometry on usb flash driveshttps://bugs.dragonflybsd.org/issues/7812007-08-21T17:27:04Zcorecode
<p>hey,</p>
<p>fdisk uses some stupid geometry like 1/0/1 on usb flash drives. umass however detects the geometry correctly; it seems this information is not correctly passed along.</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #293 (Feedback): Various updates to the handbookhttps://bugs.dragonflybsd.org/issues/2932006-08-11T04:26:06Zvictor
<p>Hi,</p>
<p>there are 3 patches attached:</p>
<p>book.diff - Updates the copyright info relating to FreeBSD at the header<br /> of the handbook.</p>
<p>dfbsd-updating - Update cvsup port path to the current pkgsrc version in<br /> the chapter "Updating DragonFly".</p>
<p>basics.diff - Update various paths relating to pkgsrc and hier(7). Also<br /> make it use the new entity for pkgsrc <br /> tree/collection/framework.</p>