DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082018-10-26T14:34:46ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3152 (Feedback): Console's size in ttyv0 and single user mode is sticking to ...https://bugs.dragonflybsd.org/issues/31522018-10-26T14:34:46Zovertime
<p>I had try</p> DragonFlyBSD - Submit #3142 (Feedback): lib/libdmsg: Unbreak using new API EVP_CIPHER_CTX_new()https://bugs.dragonflybsd.org/issues/31422018-07-08T11:18:33Ztkusumikusumi.tomohiro@gmail.com
<p><a class="external" href="https://github.com/kusumi/DragonFlyBSD/commit/e6833c80bc898c2674e180828fe62cd0b53226e7">https://github.com/kusumi/DragonFlyBSD/commit/e6833c80bc898c2674e180828fe62cd0b53226e7</a></p>
<p>--<br />The upstream OpenSSL no longer publicly expose definition of<br />EVP_CIPHER_CTX (struct evp_cipher_ctx_st).</p>
<p>Due to this change clients need to have it as a pointer instead<br />of as a value, and allocate or free EVP_CIPHER_CTX instance by<br />EVP_CIPHER_CTX_new()/EVP_CIPHER_CTX_free().</p>
<blockquote>
<p><a class="external" href="https://github.com/openssl/openssl/issues/962#issuecomment-208792020">https://github.com/openssl/openssl/issues/962#issuecomment-208792020</a></p>
</blockquote> DragonFlyBSD - Bug #2958 (Feedback): Hammer FS dies during pruning after massive write loadhttps://bugs.dragonflybsd.org/issues/29582016-10-09T11:11:20Zneilbkyuupichan@gmail.com
<p>I have one or two apps that use leveldb badly, and read and write a lot of data to disk.</p>
<p>I have a 256GB SSD, and to avoid running out of space within an hour or two of starting these apps, I have them use the DB on a no history PFS and clean the FS intraday. This kernel freezes around 40% of the time during pruning. The other operations are never a problem.</p>
<p>I don't really know what I can give as useful information. Normal usage without these apps is fine; hammer never gives a problem. Just after 100s of GBs of writes pruning sometimes kills the kernel. The FS is always fine and not corrupt after rebooting, and redoing the clean usually then succeeds (though once it died again, after making progress freeing space).</p>
<p>Incidentally, during these pruning phases that do succeed, X completely freezes for 20-30s several times; the mouse doesn't move and the desktop clock I have stops ticking. Not losing userspace interactivity would be nice.</p>
<p>$ uname -a<br />DragonFly zotac.akihabara.co.uk 4.5-DEVELOPMENT DragonFly v4.5.0.681.g2e03c8-DEVELOPMENT <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a>: Sun Mar 20 21:54:05 JST 2016 <a class="email" href="mailto:root@zotac.akihabara.co.uk">root@zotac.akihabara.co.uk</a>:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64</p> DragonFlyBSD - Bug #2957 (Feedback): swapoff -a followed by swapon -a doesn't give your swap backhttps://bugs.dragonflybsd.org/issues/29572016-10-09T11:06:08Zneilbkyuupichan@gmail.com
<p>I did swapoff -a taking all my swap away. I think I got an error message about an interrupted syscall from the program at the end of it. If you're trying to reproduce you should probably have swap space in use.</p>
<p>I then did swapon -a. It doesn't complain, and I can't remember if swap is shown as existing, but if it is the swap is not used.</p>
<p>A few hours later the kernel killed a process and in the sys logs there was a warning saying no swap space. None was used, it's that there wasn't any available at all, used or unused.</p>
<p>This has been a bug for a while; I remember it for 1-2 years at least.</p>
<p>$ uname -a<br />DragonFly zotac.akihabara.co.uk 4.5-DEVELOPMENT DragonFly v4.5.0.681.g2e03c8-DEVELOPMENT <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a>: Sun Mar 20 21:54:05 JST 2016 <a class="email" href="mailto:root@zotac.akihabara.co.uk">root@zotac.akihabara.co.uk</a>:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64</p> DragonFlyBSD - Submit #2721 (Feedback): Some few zalloc calls to objcache ones replacementshttps://bugs.dragonflybsd.org/issues/27212014-08-30T17:12:51Zdclinkdevnexen@gmail.comDragonFlyBSD - Submit #2717 (Feedback): Out of range numeric handlinghttps://bugs.dragonflybsd.org/issues/27172014-08-22T12:36:50Zdclinkdevnexen@gmail.com
<p>In a similar way than OpenBSD, the numeric values overflows are checked.</p> DragonFlyBSD - Bug #2644 (Feedback): 3.6.0-REL trap 9 on boothttps://bugs.dragonflybsd.org/issues/26442014-02-20T06:53:30Zmemmerto
<p>Booting 3.6.0-REL on my not-quite-ancient IBM x3400 (with Intel E5310 QC processor) traps:</p>
<p>CPU0 stopping CPUs: 0x0000000e<br /> stopped<br />Stopped vmx_set_ctl_setting+0x36: rdmsr<br />db> where<br />vmx_set_ctl_setting() at vmx_set_ctl_setting+0x36 0xffffffff809721f6<br />vmx_set_default_settings() at vmx_set_default_settings+0x1e 0xffffffff80972326<br />vmx_init() at vmx_init+0x5c 0xffffffff8097305e<br />vmm_init() at vmm_init+0xa3 0xffffffff80971c1f<br />mi_startup() at mi_startup+0xb1 0xffffffff80532775<br />db></p>
<p>For reference, 3.4.2-REL worked fine on this machine.</p> DragonFlyBSD - Bug #2636 (Feedback): Add -x flag to iostat (a la solaris)https://bugs.dragonflybsd.org/issues/26362014-02-13T21:50:00Ztuxillo
<p>Add -x flag to iostat (a la solaris)</p> DragonFlyBSD - Bug #2617 (Feedback): Possible issue with wireless mouse on 3.6 releasehttps://bugs.dragonflybsd.org/issues/26172013-12-20T09:52:27ZFilippoMofilippomore@yahoo.com
<p>I have a possible bug to report on RELEASE_3_6_0 on i386 arch.<br />I have a usb cordless mouse that does'not work.It is correctly identified<br />as ums0 and there is a /dev/ums0 on the same receiver there is a keyboard that works and the hardware works on other OSes.<br />I killed moused and started moused -p /dev/sysmouse but it did not work.<br />Filippo</p>
<p>On Thursday, December 19, 2013 9:00 PM, "<a class="email" href="mailto:bugs-request@dragonflybsd.org">bugs-request@dragonflybsd.org</a>" <<a class="email" href="mailto:bugs-request@dragonflybsd.org">bugs-request@dragonflybsd.org</a>> wrote:</p>
<p>Send Bugs mailing list submissions to<br /> <a class="email" href="mailto:bugs@dragonflybsd.org">bugs@dragonflybsd.org</a></p>
<p>To subscribe or unsubscribe via the World Wide Web, visit<br /> <a class="external" href="http://lists.dragonflybsd.org/mailman/listinfo/bugs">http://lists.dragonflybsd.org/mailman/listinfo/bugs</a><br />or, via email, send a message with subject or body 'help' to<br /> <a class="email" href="mailto:bugs-request@dragonflybsd.org">bugs-request@dragonflybsd.org</a></p>
<p>You can reach the person managing the list at<br /> <a class="email" href="mailto:bugs-owner@dragonflybsd.org">bugs-owner@dragonflybsd.org</a></p>
<p>When replying, please edit your Subject line so it is more specific<br />than "Re: Contents of Bugs digest..."</p>
<p>Today's Topics:</p>
<p> 1. [DragonFlyBSD - Bug <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a>] (Resolved) panic while running gdb<br /> test suite (Pierre Abbat via Redmine)</p>
<hr />
<p>Message: 1<br />Date: Wed, 18 Dec 2013 22:35:30 -0800<br />From: Pierre Abbat via Redmine<br /> <<a class="email" href="mailto:bugtracker-admin@leaf.dragonflybsd.org">bugtracker-admin@leaf.dragonflybsd.org</a>><br />To: undisclosed-recipients:;<br />Subject: [DragonFlyBSD - Bug <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a>] (Resolved) panic while running gdb<br /> test suite<br />Message-ID:<br /> <<a class="email" href="mailto:redmine.journal-11682.20131219063529.7a9eb072d3b04776@leaf.dragonflybsd.org">redmine.journal-11682.20131219063529.7a9eb072d3b04776@leaf.dragonflybsd.org</a>><br /> <br />Content-Type: text/plain; charset=UTF-8</p>
<p>Issue <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a> has been updated by phma.</p>
<p>Status changed from New to Resolved</p>
<p>It is fixed. Thanks.</p>
<p>----------------------------------------<br />Bug <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a>: panic while running gdb test suite<br /><a class="external" href="http://bugs.dragonflybsd.org/issues/2615#change-11682">http://bugs.dragonflybsd.org/issues/2615#change-11682</a></p>
<ul>
<li>Author: phma</li>
<li>Status: Resolved</li>
<li>Priority: High</li>
<li>Assignee: </li>
<li>Category: </li>
<li>Target version: <br />----------------------------------------<br />see <a class="external" href="https://github.com/DragonFlyBSD/DPorts/wiki/Run-GDB-testsuite">https://github.com/DragonFlyBSD/DPorts/wiki/Run-GDB-testsuite</a></li>
</ul>
<p>I ran the testsuite on gdb 7.6.1 and it crashed partway through. This is as far as it got:</p>
<p>Running ./gdb.base/fileio.exp ...<br />FAIL: gdb.base/fileio.exp: Open for write but no write permission returns <br />EACCES<br />FAIL: gdb.base/fileio.exp: Unlinking a file in a directory w/o write access <br />returns EACCES<br />Running ./gdb.base/gcore-relro.exp ...<br />Running ./gdb.base/huge.exp ...<br />Running ./gdb.base/find.exp ...<br />Running ./gdb.base/ctxobj.exp ...<br />Running ./gdb.base/cond-eval-mode.exp ...<br />Running ./gdb.base/arrayidx.exp ...<br />Running ./gdb.base/eval-skip.exp ...<br />Running ./gdb.base/attach.exp ...</p>
<p>It crashed in the same place both times. The kernel dumps are numbers 2 and 3 in leaf:/home/phma/crash/zyxomma/. I need this fixed so that I can fix the thread bug in gdb.</p>
<p>-- <br />You have received this notification because you have either subscribed to it, or are involved in it.<br />To change your notification preferences, please click here: <a class="external" href="http://bugs.dragonflybsd.org/my/account">http://bugs.dragonflybsd.org/my/account</a></p>
<hr />
<p>_<em><i></em></i>__<em>_</em>___________________________________<br />Bugs mailing list<br /><a class="email" href="mailto:Bugs@dragonflybsd.org">Bugs@dragonflybsd.org</a><br /><a class="external" href="http://lists.dragonflybsd.org/mailman/listinfo/bugs">http://lists.dragonflybsd.org/mailman/listinfo/bugs</a></p>
End of Bugs Digest, Vol 16, Issue 10
<hr /> 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 #1428 (Feedback): POSIX.1e implementation is too oldhttps://bugs.dragonflybsd.org/issues/14282009-07-17T02:08:53Zhasso
<p>Our posix1e(3) implementation is too old and not compatible with any <br />recent enough piece of software.</p> DragonFlyBSD - Bug #1127 (Feedback): cdrom drive not detectedhttps://bugs.dragonflybsd.org/issues/11272008-08-22T22:48:07Ztgr
<p>Hi, I've got a bit of a problem with the install CD. I've tested this on<br />2.0 and 2.1.0-DEV (i.e. the daily iso downloadable on 2008.08.22). This<br />happens way before I can make any sort of FS, but the same machine's<br />booted up XP, Kubuntu and FBSD5.4.</p>
<p>Anyway, what I can see on the bootup screen of that machine now is as<br />follows:</p>
<p><quote><br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:acd0<br />no disk named 'acd0'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:acd1<br />no disk named 'acd1'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:/dev/acd0a<br />no disk named 'acd0a'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br /></quote></p>
<p>When I then type "panic", the following appears:</p>
<p><quote><br />panic: panic from console<br />Trace beginning at frame 0xc872ca8<br />panic(c05ce64a,c06bc720,c05d0be3,c0872cd8,6) at panic+0x99<br />panic(c05d0be3,c05ce4a6,696e6170,c0560063,8) at panic+0x99<br />vfs_mountroot_ask(c4360b70,c06702dc,d7886c3c,87d000,c0872d98) at<br />vfs_mountroot_ask+0xd7<br />vfs_mountroot(0,87d000,86fc00,87d000,0) at fvs_mountroot+oxcf<br />mi_startup(86f000,d,c06b2a38,c0872c24,c0872c0c) at mi_startup+0x99<br />begin() at begin+0x42<br />Debugger("panic")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0<br /></quote></p>
<p>I've run this twice in a row just to verify all the values, in case they<br />changed. They didn't.</p>
<p>If there is any more information I can provide, please do tell. This<br />system is not in use in any other way, all data on the HDs etc is<br />discardable, so anything goes.</p> DragonFlyBSD - Bug #385 (Feedback): Mail archive address removalhttps://bugs.dragonflybsd.org/issues/3852006-11-22T22:22:03Zjustin
<p>Here's a question for everyone: I had originally the mail archive to<br />completely remove mail addresses, but it seems to mostly be annoying -<br />contacting someone from an archived email would be a dead end unless you<br />happened to already know the person's email address. Meanwhile, the<br />DragonFly lists are archived other places like MARC and Gmane, and<br />addresses are at best mildly obfusticated there.</p>
<p>Opinions? If anyone is significantly bothered by this, I'll keep the<br />addresses completely hidden.</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> 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>