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 #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 - Bug #2638 (Feedback): Fix machdep.pmap_mmu_optimizehttps://bugs.dragonflybsd.org/issues/26382014-02-13T21:51:39Ztuxillo
<p>Fix machdep.pmap_mmu_optimize (currently off by default in commit 1ac5304a10366be7ed3129ceee7ca94beb0f3183 ). Affects apache and rtorrent for sure.</p>
<p>"might be fixed here: a44410dd8663abb121417692995d3b365f32fd6e<br />update: it's not fixed"</p> DragonFlyBSD - Bug #2396 (Feedback): Latest 3.1 development version core dumps while destroying m...https://bugs.dragonflybsd.org/issues/23962012-07-18T10:50:26Zsgeorgesgeorge.ml2@gmail.com
<p>Hi,</p>
<p>I was destroying a master PFS on the ROOT volume and the system ( v3.1.0.827.gf6167a5-DEVELOPMENT )core dumped.<br />I tried today's latest snapshot and got the same result.<br />The Coredump is uploaded to sgeorge@leaf:~/crash/Coredump20120718.tbz</p>
<p>panic: assertion "layer2->zone == zone" failed in hammer_blockmap_free at /usr/src/sys/vfs/hammer/hammer_blockmap.c:1020<br />cpuid = 0<br />Trace beginning at frame 0xffffffe09e20f178<br />panic() at panic+0x1fb 0xffffffff804bef68 <br />panic() at panic+0x1fb 0xffffffff804bef68 <br />hammer_blockmap_free() at hammer_blockmap_free+0x2e5 0xffffffff80691a0c <br />hammer_delete_at_cursor() at hammer_delete_at_cursor+0x4e2 0xffffffff806aac62 <br />hammer_pfs_rollback() at hammer_pfs_rollback+0x26c 0xffffffff806b0b20 <br />hammer_ioc_destroy_pseudofs() at hammer_ioc_destroy_pseudofs+0x77 0xffffffff806b0c6c <br />hammer_ioctl() at hammer_ioctl+0x80e 0xffffffff806a5b1e <br />hammer_vop_ioctl() at hammer_vop_ioctl+0x58 0xffffffff806be8d3 <br />vop_ioctl() at vop_ioctl+0x98 0xffffffff8053d244 <br />vn_ioctl() at vn_ioctl+0xfd 0xffffffff8053a4d9 <br />fo_ioctl() at fo_ioctl+0x46 0xffffffff804f026e <br />mapped_ioctl() at mapped_ioctl+0x493 0xffffffff804f0725 <br />sys_ioctl() at sys_ioctl+0x1c 0xffffffff804f07be <br />syscall2() at syscall2+0x370 0xffffffff807814c1 <br />Xfast_syscall() at Xfast_syscall+0xcb 0xffffffff8076ae2b <br />(null)() at 0 0 <br />(null)() at 0x723d524553550061 0x723d524553550061</p>
<p>Fatal trap 9: general protection fault while in kernel mode<br />cpuid = 0; lapic->id = 00000000<br />instruction pointer = 0x8:0xffffffff8077acf9<br />stack pointer = 0x10:0xffffffe09e20f010<br />frame pointer = 0x10:0xffffffe09e20f028<br />code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 0, def32 0, gran 1<br />processor eflags = interrupt enabled, resume, IOPL = 0<br />current process = 957<br />current thread = pri 10 <br />kernel: type 9 trap, code=0</p>
<p>CPU0 stopping CPUs: 0x00000002<br /> stopped<br />Physical memory: 3787 MB<br />Dumping 1055 MB: 1040 1024 1008 992 976 960 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16</p> DragonFlyBSD - Bug #2347 (Feedback): Hammer PFSes destroy does not give back full space allocated...https://bugs.dragonflybsd.org/issues/23472012-04-11T07:17:48Zsgeorgesgeorge.ml2@gmail.com
<p>I was mirroring PFSes from 3.1 dev to slaves in 3.02 and I found that<br />the PFSes took more space on the 3.02 slave.<br />Investigating I found this strange thing</p>
<p>94 GB is allocated for this slave PFS. But when it is removed only 52<br />GB is freed :-(</p>
<p>dfly-bkpsrv2# hammer dedup /pfs/software<br />Dedup running<br />Dedup /pfs/software succeeded<br />Dedup ratio = 1.06<br /> 100 GB referenced<br /> 94 GB allocated<br /> 4339 KB skipped<br /> 429 CRC collisions<br /> 0 SHA collisions<br /> 1 bigblock underflows<br /> 0 new dedup records<br /> 0 new dedup bytes</p>
<p>dfly-bkpsrv2# df -h<br />Filesystem Size Used Avail Capacity Mounted on<br />ROOT 459G 354G 106G 77% /<br />devfs 1.0K 1.0K 0B 100% /dev<br />/dev/serno/QM00001.s1a 756M 168M 527M 24% /boot<br />/pfs/<code>@-1:00001 459G 354G 106G 77% /var<br />/pfs/</code>@-1:00002 459G 354G 106G 77% /tmp<br />/pfs/<code>@-1:00003 459G 354G 106G 77% /usr<br />/pfs/</code>@-1:00004 459G 354G 106G 77% /home<br />/pfs/<code>@-1:00005 459G 354G 106G 77% /usr/obj<br />/pfs/</code>@-1:00006 459G 354G 106G 77% /var/crash<br />/pfs/<code>@-1:00007 459G 354G 106G 77% /var/tmp<br />procfs 4.0K 4.0K 0B 100% /proc<br />dfly-bkpsrv2# ls<br />home software usr var<br />var.tmp vms2-lxc<br />mysql-baks tmp usr.obj var.crash vms1-lxc<br />dfly-bkpsrv2# hammer pfs-destroy /pfs/software<br />You have requested that PFS#11 () be destroyed<br />This will irrevocably destroy all data on this PFS!!!!!<br />Do you really want to do this? y<br />Destroying PFS #11 () in 5 4 3 2 1.. starting destruction pass<br />pfs-destroy of PFS#11 succeeded!<br />dfly-bkpsrv2# df -h<br />Filesystem Size Used Avail Capacity Mounted on<br />ROOT 459G 302G 158G 66% /<br />devfs 1.0K 1.0K 0B 100% /dev<br />/dev/serno/QM00001.s1a 756M 168M 527M 24% /boot<br />/pfs/</code>@-1:00001 459G 302G 158G 66% /var<br />/pfs/<code>@-1:00002 459G 302G 158G 66% /tmp<br />/pfs/</code>@-1:00003 459G 302G 158G 66% /usr<br />/pfs/<code>@-1:00004 459G 302G 158G 66% /home<br />/pfs/</code>@-1:00005 459G 302G 158G 66% /usr/obj<br />/pfs/<code>@-1:00006 459G 302G 158G 66% /var/crash<br />/pfs/</code>@-1:00007 459G 302G 158G 66% /var/tmp<br />procfs 4.0K 4.0K 0B 100% /proc</p> DragonFlyBSD - Bug #2090 (Feedback): snd_hda does not support headphone automutehttps://bugs.dragonflybsd.org/issues/20902011-06-15T07:46:35Zjustin
<p>The hda sound driver does not notice jack insert/removal events. Even when<br />booted verbosely, there's no action, so attaching headphones does not mute<br />speaker audio.</p>
<p>An update to FreeBSD's sound/pci/hda expressly mentions solving this problem:</p>
<p><a class="external" href="http://svnweb.freebsd.org/base?view=revision&revision=182999">http://svnweb.freebsd.org/base?view=revision&revision=182999</a></p> DragonFlyBSD - Bug #1831 (Feedback): HAMMER "malloc limit exceeded" panichttps://bugs.dragonflybsd.org/issues/18312010-09-11T23:42:36Zeocallaghan
<p>I was able to reproduce with a hammer equivalent of issue1726 with the following<br />test case from vsrinivas in issue1726:</p>
<pre>
<code class="c syntaxhl" data-language="c"><span class="cp">#include</span> <span class="cpf"><unistd.h></span><span class="cp">
#include</span> <span class="cpf"><stdlib.h></span><span class="cp">
#include</span> <span class="cpf"><stdio.h></span><span class="cp">
</span>
<span class="n">main</span><span class="p">()</span> <span class="p">{</span>
<span class="kt">int</span> <span class="n">i</span><span class="p">;</span>
<span class="kt">char</span> <span class="n">id</span><span class="p">[</span><span class="mi">320</span><span class="p">]</span> <span class="o">=</span> <span class="p">{};</span>
<span class="k">for</span> <span class="p">(</span><span class="n">i</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">i</span> <span class="o"><</span> <span class="mi">10000000</span><span class="p">;</span> <span class="n">i</span><span class="o">++</span><span class="p">)</span> <span class="p">{</span>
<span class="n">sprintf</span><span class="p">(</span><span class="n">id</span><span class="p">,</span> <span class="s">"%09d"</span><span class="p">,</span> <span class="n">i</span><span class="p">);</span>
<span class="n">link</span><span class="p">(</span><span class="s">"sin.c"</span><span class="p">,</span> <span class="n">id</span><span class="p">);</span>
<span class="p">}</span>
<span class="k">return</span> <span class="mi">0</span><span class="p">;</span>
<span class="p">}</span>
</code><br /></pre>
<p>----<br /><pre>
(kgdb) bt
#0 _get_mycpu (di=0xc06d4ca0) at ./machine/thread.h:83
#1 md_dumpsys (di=0xc06d4ca0)
at /usr/src/sys/platform/pc32/i386/dump_machdep.c:263
#2 0xc0304d15 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:880
#3 0xc03052d5 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:387
#4 0xc030559e in panic (fmt=0xc05bb41b "%s: malloc limit exceeded")
at /usr/src/sys/kern/kern_shutdown.c:786
#5 0xc03032bb in kmalloc (size=25, type=0xc1d8f590, flags=258)
at /usr/src/sys/kern/kern_slaballoc.c:503
#6 0xc04aa5a3 in hammer_alloc_mem_record (ip=0xcb803d50, data_len=25)
at /usr/src/sys/vfs/hammer/hammer_object.c:280
#7 0xc04aa91f in hammer_ip_add_directory (trans=0xce350ad4,
dip=0xcb803d50, name=0xd3cdb1d0 "000452457", bytes=9, ip=0xce31df50)
at /usr/src/sys/vfs/hammer/hammer_object.c:666
#8 0xc04bbf8a in hammer_vop_nlink (ap=0xce350b2c)
at /usr/src/sys/vfs/hammer/hammer_vnops.c:1388
#9 0xc036cc1f in vop_nlink_ap (ap=0xce350b2c)
at /usr/src/sys/kern/vfs_vopops.c:1978
#10 0xc03717ca in null_nlink (ap=0xce350b2c)
at /usr/src/sys/vfs/nullfs/null_vnops.c:164
#11 0xc036d465 in vop_nlink (ops=0xcdbbe030, nch=0xce350c48,
dvp=0xce0913e8, vp=0xce2f04e8, cred=0xcdef1738)
at /usr/src/sys/kern/vfs_vopops.c:1397
---Type <return> to continue, or q <return> to quit---
---Type <return> to continue, or q <return> to quit---#12 0xc0365496 in
kern_link (nd=0xce350c80, linknd=0xce350c48)
at /usr/src/sys/kern/vfs_syscalls.c:2320
#13 0xc036ad49 in sys_link (uap=0xce350cf0)
at /usr/src/sys/kern/vfs_syscalls.c:2345
#14 0xc055f6b3 in syscall2 (frame=0xce350d40)
at /usr/src/sys/platform/pc32/i386/trap.c:1310
#15 0xc0547fb6 in Xint0x80_syscall ()
at /usr/src/sys/platform/pc32/i386/exception.s:876
#16 0x0000001f in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(kgdb)
</pre></p>
<p>Dump on my leaf account;<br /><a class="external" href="http://leaf.dragonflybsd.org/~evocallaghan/hammer_vfs_panic.7z">http://leaf.dragonflybsd.org/~evocallaghan/hammer_vfs_panic.7z</a></p>
<p>Cheers,<br />Edward.</p> DragonFlyBSD - Bug #1563 (Feedback): reset(1) doesn't reset terminal to the defaultshttps://bugs.dragonflybsd.org/issues/15632009-10-06T20:47:45Zhasso
<p>reset(1) doesn't reset terminal to the defaults. You can compare stty -e <br />outputs before and after the issuing reset(1). Output always differs, <br />more on some terminals, less on others.</p> DragonFlyBSD - Bug #1489 (Feedback): panic: ufs_dirbad: bad dirhttps://bugs.dragonflybsd.org/issues/14892009-09-06T17:08:20Zrumcic
<p>After a previous panic I got this panic while building world. After cleaning<br />out /usr/obj I have been unable to repeat this panic again, so it's not<br />reproducable (for now).</p>
<p>Dump at leaf:~rumko/crash/bad_dir/ and the backtrace is:<br />#0 dumpsys () at ./machine/thread.h:83<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0xc01e6d95 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:375<br /><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> 0xc01e705a in panic (fmt=0xc0447c39 "ufs_dirbad: bad dir")<br />at /usr/src/sys/kern/kern_shutdown.c:802<br /><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> 0xc0323b53 in ufs_dirbad (ip=0xf57c9e00, offset=0, how=0xc0447c90 "mangled<br />entry") at /usr/src/sys/vfs/ufs/ufs_lookup.c:610<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0xc0324463 in ufs_lookup (ap=0xf5dccabc)<br />at /usr/src/sys/vfs/ufs/ufs_lookup.c:275<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0xc0325faa in ufs_vnoperate (ap=0xf5dccabc)<br />at /usr/src/sys/vfs/ufs/ufs_vnops.c:2303<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 0xc0240948 in vop_old_lookup (ops=0xd554ca50, dvp=0xf5815ee8,<br />vpp=0xf5dccb24, cnp=0xf5dccb04) at /usr/src/sys/kern/vfs_vopops.c:172<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> 0xc022f252 in vop_compat_nresolve (ap=0xf5dccb58)<br />at /usr/src/sys/kern/vfs_default.c:225<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: make upgrade broken (Closed)" href="https://bugs.dragonflybsd.org/issues/8">#8</a> 0xc022ec59 in vop_defaultop (ap=0xf5dccb58)<br />at /usr/src/sys/kern/vfs_default.c:153<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: panic with HEAD (Closed)" href="https://bugs.dragonflybsd.org/issues/9">#9</a> 0xc0325faa in ufs_vnoperate (ap=0xf5dccb58)<br />at /usr/src/sys/vfs/ufs/ufs_vnops.c:2303<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: make buildworld broken (Closed)" href="https://bugs.dragonflybsd.org/issues/10">#10</a> 0xc0241092 in vop_nresolve (ops=0xd554ca50, nch=0xf5dccb98, dvp=0xf5815ee8,<br />cred=0xc5be6b98) at /usr/src/sys/kern/vfs_vopops.c:951<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: libstand cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/11">#11</a> 0xc022b87f in cache_resolve (nch=0xf5dccbd4, cred=0xc5be6b98)<br />at /usr/src/sys/kern/vfs_cache.c:2135<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/net cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/12">#12</a> 0xc0233f4d in nlookup (nd=0xf5dccc80)<br />at /usr/src/sys/kern/vfs_nlookup.c:499<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Buildworld error/panic (Closed)" href="https://bugs.dragonflybsd.org/issues/13">#13</a> 0xc023c576 in kern_stat (nd=0xf5dccc80, st=0xf5dccc18)<br />at /usr/src/sys/kern/vfs_syscalls.c:2444<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: zombie processes waiting for a lock, smth to worry about? (Closed)" href="https://bugs.dragonflybsd.org/issues/14">#14</a> 0xc023c714 in sys_stat (uap=0xf5dcccf0)<br />at /usr/src/sys/kern/vfs_syscalls.c:2485<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: savecore -z patch (Closed)" href="https://bugs.dragonflybsd.org/issues/15">#15</a> 0xc03fa8e9 in syscall2 (frame=0xf5dccd40)<br />at /usr/src/sys/platform/pc32/i386/trap.c:1339<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: install: net/bridge/*.h: No such file or directory (Closed)" href="https://bugs.dragonflybsd.org/issues/16">#16</a> 0xc03e7be6 in Xint0x80_syscall ()<br />at /usr/src/sys/platform/pc32/i386/exception.s:876<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Minor typos (Closed)" href="https://bugs.dragonflybsd.org/issues/17">#17</a> 0x08063527 in ?? ()<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #1429 (Feedback): vkernel bug - "mfree: m->m_nextpkt != NULL"https://bugs.dragonflybsd.org/issues/14292009-07-19T02:09:21Zdillon
<p>I get this in the vkernel, usually when I exhaust the mbuf objcache.</p>
<pre><code>The bug is the "mfree: m->m_nextpkt != NULL" message, not the mbuf<br /> exhaustion (while testing async write BIOs w/NFS I didn't slap any<br /> limits on how many it tried to run in parallel) &lt;GRIN&gt;.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre>
<ol>
<li>Warning, objcache(mbuf): Exhausted!<br />mfree: m->m_nextpkt != NULL<br />Trace beginning at frame 0x57869c58<br />m_free(8232e94,58bc9700,833791c,58bc97e4,57869c84) at 0x80ed998<br />m_free(58bc9700,1,576dabc8,57869cec,8159941) at 0x80ed998<br />m_freem(58bc9700,576dabc8,14,578c1f00,5847afe0) at 0x80ee444<br />ip_output(58bc9700,0,578c1efc,10000,0) at 0x8159941<br />udp_input(5847af00,0,58bc8d00,0,0) at 0x816a6d8<br />netmsg_pru_send(582feba8,0,82760e0,57869d84,8139e60) at 0x80f08a1<br />netmsg_service(582feba8,1,0,414003c0,833791c) at 0x8139a26<br />netmsg_service_loop(82760e0,0,0,0,0) at 0x8139e60<br />Warning, objcache(cluster mbuf): Exhausted!</li>
</ol> DragonFlyBSD - Bug #1387 (Feedback): zero-size malloc and ps: kvm_getprocs: Bad addresshttps://bugs.dragonflybsd.org/issues/13872009-05-24T09:39:35Zqhwt+dfly
<p>Hello.<br />On recent -DEVELOPMENT ps command displays a non-intuitive error message<br />on a non-existent pid:<br /> ps: kvm_getprocs: Bad address</p>
<p>Apparently the recent malloc reimplementation has changed malloc(3) family<br />so as malloc(0) now returns a pointer such that useracc() returns EFAULT<br />for it. kvm_getprocs() is one the functions affected by the new behavior<br />(no, I don't have the list of affected functions other than this<br />yet :). It used to return a non-NULL pointer and a 0 to *cnt, but now<br />it returns just NULL without affecting *cnt, so ps command displays the<br />error message. I think one way to fix is something like below (the fix<br />to the callers is taken from FreeBSD), but if we can restore the old<br />behavior of malloc(0), we don't need such fix.</p>
<p>%%%<br />diff --git a/bin/ps/ps.c b/bin/ps/ps.c<br />index 82e3e63..b66988a 100644<br />--- a/bin/ps/ps.c<br />+++ b/bin/ps/ps.c<br /><code>@ -385,7 +385,9 </code>@ main(int argc, char *<strong>argv)<br /> /</strong>
* select procs<br /> <strong>/<br />- if ((kp = kvm_getprocs(kd, what, flag, &nentries)) == NULL)<br />+ nentries = <del>1;<br />+ kp = kvm_getprocs(kd, what, flag, &nentries);<br />+ if ((kp == NULL && nentries > 0) || (kp != NULL && nentries < 0))<br /> errx(1, "%s", kvm_geterr(kd));<br /> if ((kinfo = malloc(nentries * sizeof(*kinfo))) NULL)<br /> err(1, NULL);<br />diff --git a/lib/libkvm/kvm_proc.c b/lib/libkvm/kvm_proc.c<br />index 1c39636..d0e388d 100644<br />--</del> a/lib/libkvm/kvm_proc.c<br />+<ins>+ b/lib/libkvm/kvm_proc.c<br /><code>@ -479,6 +479,10 </code>@ kvm_getprocs(kvm_t *kd, int op, int arg, int *cnt)<br /> _kvm_syserr(kd, kd->program, "kvm_getprocs");<br /> return (0);<br /> }<br /></ins> if (size 0) {<br />+ *cnt = 0;<br />+ return (0);<br />+ }<br /> do {<br /> size <ins>= size / 10;<br /> kd->procbase = (struct kinfo_proc *)<br />diff --git a/usr.bin/fstat/fstat.c b/usr.bin/fstat/fstat.c<br />index 133fff7..7a8545d 100644<br />--- a/usr.bin/fstat/fstat.c<br /></ins>++ b/usr.bin/fstat/fstat.c<br /><code>@ -241,7 +241,9 </code>@ main(int argc, char **argv)<br /> if (kvm_nlist(kd, nl) != 0)<br /> errx(1, "no namelist: <span>s", kvm_geterr(kd));<br /> #endif<br />- if ((p = kvm_getprocs(kd, what, arg, &cnt)) == NULL)<br />+ cnt = <del>1;<br />+ p = kvm_getprocs(kd, what, arg, &cnt);<br />+ if ((p == NULL &x%x</span> cnt > 0) || (p != NULL && cnt < 0))<br /> errx(1, "%s", kvm_geterr(kd));<br /> if (nflg)<br /> printf("USER <span></del></strong>.*s %<strong>.*s FD DEV %</strong>.*s MODE SZ|DV R/W", <br /></span>%%</p> DragonFlyBSD - Bug #1249 (Feedback): panic: ffs_vfree: freeing free inodehttps://bugs.dragonflybsd.org/issues/12492009-01-29T02:22:01Zrumcic
<p>As far as I know, it happened while another partition was being fsck-ed, but<br />other than that, there shouldn't have been much activity on the machine at the<br />time.</p>
<p>Unread portion of the kernel message buffer:<br />dev = #ad/0x20045, ino = 15, fs = /home<br />panic: ffs_vfree: freeing free inode<br />mp_lock = 00000000; cpuid = 0<br />Trace beginning at frame 0xdd0dd98c<br />panic(dd0dd9b0,c8520000,f1977000,c852012d,dd0dd9d8) at panic+0x14d<br />panic(c051a302,7,dd0dd9f4,0,0) at panic+0x14d<br />ffs_freefile(dd0ddae8,f,0,43ff) at ffs_freefile+0x186<br />handle_workitem_freefile(0,dd0ddce8,c5e4ab0c,dd0ddc8c,c02c5a67) at<br />handle_workitem_freefile+0x89<br />process_worklist_item(c5cfe400,49809881,c05a9ca0,0,c5be98c4) at<br />process_worklist_item+0x18c<br />softdep_process_worklist(0,c5cfe400,dd0ddd84,c02d5c86,0) at<br />softdep_process_worklist+0xa5<br />bio_ops_sync(0,49809881,c5cfe100,ff800000,c) at bio_ops_sync+0x2d<br />sched_sync(0,0,0,0,0) at sched_sync+0x16e<br />kthread_exit() at kthread_exit<br />boot() called on cpu#0<br />Uptime: 15m30s</p>
<p>dumping to dev #ad/0x20041, blockno 2107648<br />dump 3070 3069 3068 3067 3066 3065 3064 3063 3062 3061 3060 3059 3058 3057 3056 <br /><snip><br /> 4 3 2 1 0</p>
<p>GNU gdb 6.7.1<br />Copyright (C) 2007 Free Software Foundation, Inc.<br />License GPLv3+: GNU GPL version 3 or later <<a class="external" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>><br />This is free software: you are free to change and redistribute it.<br />There is NO WARRANTY, to the extent permitted by law. Type "show copying" <br />and "show warranty" for details.<br />This GDB was configured as "i386-dragonfly".<br />(kgdb) bt<br />#0 dumpsys () at ./machine/thread.h:83<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0xc02874e9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:376<br /><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> 0xc02877ae in panic (fmt=0xc051a302 "ffs_vfree: freeing free inode")<br />at /usr/src/sys/kern/kern_shutdown.c:801<br /><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> 0xc03ced7b in ffs_freefile (pvp=0xdd0ddae8, ino=15, mode=17407)<br />at /usr/src/sys/vfs/ufs/ffs_alloc.c:1700<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0xc03d58b8 in handle_workitem_freefile (freefile=0xc5a63e20)<br />at /usr/src/sys/vfs/ufs/ffs_softdep.c:3044<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0xc03d4f88 in process_worklist_item (matchmnt=0x0, flags=<value optimized<br />out>) at /usr/src/sys/vfs/ufs/ffs_softdep.c:735<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 0xc03d689f in softdep_process_worklist (matchmnt=0x0)<br />at /usr/src/sys/vfs/ufs/ffs_softdep.c:622<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> 0xc02d44f4 in bio_ops_sync (mp=0x0) at /usr/src/sys/kern/vfs_mount.c:1227<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: make upgrade broken (Closed)" href="https://bugs.dragonflybsd.org/issues/8">#8</a> 0xc02d5c86 in sched_sync () at /usr/src/sys/kern/vfs_sync.c:243<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: panic with HEAD (Closed)" href="https://bugs.dragonflybsd.org/issues/9">#9</a> 0xc027ac23 in suspend_kproc (td=Cannot access memory at address 0x8<br />) at /usr/src/sys/kern/kern_kthread.c:158<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #901 (Feedback): route show needs to get data from all cpushttps://bugs.dragonflybsd.org/issues/9012007-12-31T00:07:48Zcorecode
<p>when executing `route show' on my MP system, I will get varying results. <br />Additionally, it will print all temporary route entries as well, even for hosts<br />outside the local network.</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 #243 (Feedback): weird behavior in the shellhttps://bugs.dragonflybsd.org/issues/2432006-07-15T14:49:02Zswildner
<p>Hi,</p>
<p>I'm not sure if this is a 'real' bug but I'm curious if anyone knows the <br />cause. Check this:</p>
<p>zoot# echo $PATH<br />/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/xorg/bin:/home/s/bin<br />zoot# pwd<br />/usr/src/sys/dev/disk/md<br />zoot# .<br />/usr/sbin/.: Permission denied.<br />zoot# cd /<br />zoot# .<br />/usr/sbin/.: Permission denied.</p>
<p>In other words: The strange thing is that whereever I type . on the csh <br />prompt, I get the /usr/sbin/.: message regardless of what my current <br />directory is.</p>
<p>On a Solaris system I get ".: Permission denied." which is what I'd <br />expect rather.</p>
<p>So, can anyone enlighten me why DragonFly behaves like that?</p>
<p>Sascha</p>