DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082022-08-08T19:15:54ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3323 (New): virtio (if_vtnet...) not detected on Hetzner cloud (AMD system)https://bugs.dragonflybsd.org/issues/33232022-08-08T19:15:54Zmneumann
<p>`pciconf -lv` lists a "Virtio network device"</p>
<p><img src="https://bugs.dragonflybsd.org/attachments/download/1724/clipboard-202208082105-nspru.png" alt="" loading="lazy" /></p>
<p>But it does not show up under `ifconfig`. Also the virtio SCSI harddisk is not detected.</p>
<p>Just curious if I am doing anything wrong.</p> DragonFlyBSD - Bug #3231 (New): wifi drops on 5.8https://bugs.dragonflybsd.org/issues/32312020-04-06T12:08:09Ztse
<p>Since upgrading to 5.8, my wifi occasionally drops out, and `doas service netif restart` does not bring it back. A reboot does though</p>
<p>I've tried it with each of:<br />#wpa_supplicant_program="/usr/sbin/wpa_supplicant" <br />#wpa_supplicant_program="/raven/sbin/wpa_supplicant" <br />wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"</p>
<p>`doas service netif restart`:</p>
<p>```<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: iwm_start_fw: Unable to init nic<br />iwm0: iwm_start_fw: failed 16<br />iwm0: Failed to start INIT ucode: 16<br />iwm_run_init_ucode: failed 16<br />iwm_init_hw failed 16<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: iwm_start_fw: Unable to init nic<br />iwm0: iwm_start_fw: failed 16<br />iwm0: Failed to start INIT ucode: 16<br />iwm_run_init_ucode: failed 16<br />iwm_init_hw failed 16<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />```</p>
<p>```<br />Mar 30 15:03:23 beloved kernel: iwm0: <Intel(R) Dual Band Wireless AC 7260> mem 0xf7900000-0xf7901fff at device 0.0 on pci4</p>
<p>Mar 30 15:03:23 beloved kernel: iwm0: hw rev 0x140, fw ver 17.352738.0, address ac:fd:ce:84:65:b6<br />```</p>
<p>Something like this also doesn't work, and produces the below output</p>
<p>```<br />doas service netif stop<br />doas kldunload if_iwm<br />doas kldunload iwm7260<br />doas kldunload iwm7260fw<br />doas kldload if_iwm<br />doas kldload iwm7260fw<br />doas service netif start<br />```</p>
<p>```<br />beloved kernel: iwm0: device timeout<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to remove station: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to change mac context: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to update smart FIFO: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: Failed to remove station. Id=0<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to remove station id: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_update_quotas: Failed to send quota: 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to update PHY quota: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to change mac context: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: Failed to send binding (action:3): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to remove channel ctx: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to change mac context: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_bring_down_firmware: failed to update power management<br />beloved kernel: iwm0: iwm_start_fw: Unable to init nic<br />beloved kernel: iwm0: iwm_start_fw: failed 16<br />beloved kernel: iwm0: Failed to start INIT ucode: 16<br />beloved kernel: iwm_run_init_ucode: failed 16<br />beloved kernel: iwm_init_hw failed 16<br />beloved kernel: iwm0: could not initiate scan<br />beloved last message repeated 7 times<br />beloved last message repeated 24 times<br />beloved last message repeated 12 times<br />beloved kernel: pf_test6: kif NULL, if_xname wlan0<br />beloved kernel: pf_test: kif NULL, if_xname wlan0<br />beloved kernel: iwm0: detached<br />beloved kernel: iwm0: <Intel(R) Dual Band Wireless AC 7260> mem 0xf7900000-0xf7901fff at device 0.0 on pci4<br />beloved kernel: iwm0: iwm_start_fw: Unable to init nic<br />beloved kernel: iwm0: iwm_start_fw: failed 16<br />beloved kernel: iwm0: Failed to start INIT ucode: 16<br />beloved kernel: iwm0: detached<br />beloved kernel: iwm0: <Intel(R) Dual Band Wireless AC 7260> mem 0xf7900000-0xf7901fff at device 0.0 on pci4<br />beloved kernel: iwm0: iwm_start_fw: Unable to init nic<br />beloved kernel: iwm0: iwm_start_fw: failed 16<br />beloved kernel: iwm0: Failed to start INIT ucode: 16<br />```</p> DragonFlyBSD - Bug #2840 (New): wrong voltage is reportedhttps://bugs.dragonflybsd.org/issues/28402015-09-12T01:09:37Zyellowrabbit2010
<p>lm0: <Winbond W83627DHG Hardware Monitor> at port 0x290-0x297 on isa0<br />hw.sensors.lm0.volt0: 0.76 VDC (VCore)<br />hw.sensors.lm0.volt1: 6.55 VDC (+12V)<br />hw.sensors.lm0.volt2: 3.31 VDC (+3.3V)<br />hw.sensors.lm0.volt3: 3.31 VDC (+3.3V)<br />hw.sensors.lm0.volt4: -22.93 VDC (-12V)<br /> ^<sup>^^</sup>^^^^^^^</p> DragonFlyBSD - Bug #2797 (In Progress): vkernels with & without machdep.pmap_mmu_optimizehttps://bugs.dragonflybsd.org/issues/27972015-02-28T00:09:38Zyellowrabbit2010
<p>Hello,</p>
<p>I tried vkernel64 according to vkernel(7) with & without machdep.pmap_mmu_optimize.</p>
<p>With machdep.pmap_mmu_optimize=0 vkernel boots with many <br /><code>ept_copyout: could not fault in vm map, gpa: 804928000</code> (addresses are changing)</p>
<p>With machdep.pmap_mmu_optimize=1 box paniced (no dump, keyboard hangs --- I can't type anything)<br /><pre>
panic: assertion "origpte == 0 || (origpte & pmap->pmap_bit[PG_MANAGED_IDX])
failed in pmap_enter at /usr/src/sys/platform/pc64/x86_64/pmap.c:4122
trace beginning at frame
panic() at panic+0x21f
panic() at panic+0x21f
pmap_enter() at pmap_enter+0x297
vm_fault() at vm_fault+0x5ab
vmx_vmrun() at vmx_vm_run+0xebe
vmx_vmrun() at vmx_vm_run+0x1f
CPU0 stopping CPUs: 0x0000000e
Stopped
Stopped at Debugger+0x38: movb $0,0x125d681(%rip)
db> panic: kqueue: checkloop failed i=0
cpuid = 0
</pre></p>
<p>===================<br /><code>DragonFly fly.home.net 4.1-DEVELOPMENT DragonFly v4.1.0.876.g2deaaa-DEVELOPMENT</code></p>
<p>===================<br /><pre>
CPU: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz (3400.03-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x306a9 Stepping = 9
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x77bae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,AVX,F16C,RDRND>
AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
Structured Extended Features=0x281<GSFSBASE,SMEP,ENHMOVSB>
Thermal and PM Features=0x77<SENSOR,TURBO,ARAT,PLN,ECMD,PTM>
MONITOR/MWAIT Features=0x3<CST,INTBRK>
real memory = 7995148288 (7624 MB)
avail memory = 7503593472 (7155 MB)
</pre></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 #2493 (New): vidcontrol: invalid video mode namehttps://bugs.dragonflybsd.org/issues/24932013-01-20T07:06:58ZSvarovsvarov@yahoo.com
<p>Hello.</p>
<p>I tried to change foreground/background color of the virt. console (ttyv1) with command `vidcontrol lightwhite black` but haven't got any success. The program reports "vidcontrol: invalid video mode name". The syntax seems to be correct because on FreeBSD (latest) it works fine.</p>
<p>Do I miss something or it's a bug?</p>
<p>Regards, Dmitry.
==================================<br />PC: Netbook Eee PC 900AX<br />OS: DragonFlyBSD 3.2.1<br />----------------------------------<br />I am sorry for my english, it's still very poor.<br />Hope that my message is understandable.</p> DragonFlyBSD - Bug #2412 (New): wlan0 fails to get address via dhclienthttps://bugs.dragonflybsd.org/issues/24122012-08-27T08:09:25Znonsolosoft
<p>I'm not able to connect via Atheros 2413 to TP-Link wifi router.<br />In attachment there is the shell session log.</p> DragonFlyBSD - Bug #2224 (New): v2.13.0.291.gaa7ec - Panic on fq while installing worldhttps://bugs.dragonflybsd.org/issues/22242011-11-18T00:57:18Ztuxillo
<p>Hi,</p>
<p>While installing world into an image file (vnconfig) I got this panic:</p>
<p>Unread portion of the kernel message buffer:<br />Xdblfault() at Xdblfault+0x93<br />fq_dispatch() at fq_dispatch+0x76<br />fq_queue() at fq_queue+0x271<br />dsched_queue() at dsched_queue+0x1cc<br />diskstrategy() at diskstrategy+0x6c<br />dev_dstrategy_chain() at dev_dstrategy_chain+0xc8<br />devfs_spec_strategy() at devfs_spec_strategy+0x14d<br />vop_strategy() at vop_strategy+0x8c<br />vn_strategy() at vn_strategy+0xe3<br />hammer_io_direct_read() at hammer_io_direct_read+0x1aa<br />hammer_vop_strategy_read() at hammer_vop_strategy_read+0x4cb<br />hammer_vop_strategy() at hammer_vop_strategy+0x45<br />vop_strategy() at vop_strategy+0x8c<br />vn_strategy() at vn_strategy+0xe3<br />breadnx() at breadnx+0x9c<br />hammer_vop_write() at hammer_vop_write+0x4f2<br />vop_write() at vop_write+0x88<br />vnstrategy() at vnstrategy+0x1fd<br />dev_dstrategy() at dev_dstrategy+0x12f<br />dsched_strategy_async() at dsched_strategy_async+0x5d<br />fq_dispatch() at fq_dispatch+0x76<br />fq_dispatcher() at fq_dispatcher+0x3ad<br />boot() called on cpu#3<br />Uptime: 22h2m30s<br />Physical memory: 6019 MB<br />Dumping 2114 MB: 2099 2083 2067 2051 2035 2019 2003 1987 1971 1955 1939 1923 1907 1891 1875 1859 1843 1827 1811 1795 1779 1763 1747 1731 1715 1699 1683 1667 1651 1635 1619 1603 1587 1571 1555 1539 1523 1507 1491 1475 1459 1443 1427 1411 1395 1379 1363 1347 1331 1315 1299 1283 1267 1251 1235 1219 1203 1187 1171 1155 1139 1123 1107 1091 1075 1059 1043 1027 1011 995 979 963 947 931 915 899 883 867 851 835 819 803 787 771 755 739 723 707 691 675 659 643 627 611 595 579 563 547 531 515 499 483 467 451 435 419 403 387 371 355 339 323 307 291 275 259 243 227 211 195 179 163 147 131 115 99 83 67 51 35 19 3</p>
<p>I got the coredump available on demand.</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #2154 (New): vkernel copyout() doesn't return EFAULT on errorhttps://bugs.dragonflybsd.org/issues/21542011-10-20T10:53:37Zvsrinivasvsrinivas@ops101.org
<p>copyout() is documented as returning 0 or EFAULT; the vkernel version doesn't do<br />so, it returns a VM error code, which needs translating.</p> DragonFlyBSD - Bug #1941 (New): wlan config crashhttps://bugs.dragonflybsd.org/issues/19412010-12-25T03:54:21Zabandon.every.hope
<p>Hello-<br />Found a potential bug configuring wlan using rc.conf. The following was<br />added to rc.conf on a fresh desktop install:</p>
<p>wlans_ral0="wlan0" <br />ifconfig_wlan0="WPA DHCP"</p>
<p>The associated wpa_supplicant.conf from /etc:</p>
<p>network={<br /> ssid="stuff" <br /> psk="secretstuff" <br />}</p>
<p>With these edits in the listed files the machine poops its pants on boot<br />(during network config, of course) and gives a:</p>
<p>"ad8: WARNING - SETFEATURES SET TRANSFER MODE ..."</p>
<p>At this point it's unrecoverable.</p>
<p>It looks like adding "ifconfig_ral0="up"" in rc.conf before the other<br />two lines listed below avoids the crash. I have configured other wlan<br />setups in the past and I don't remember having to explicitly make sure<br />the device was up. Maybe it is just the device?</p>
<p>The device from dmesg:<br />ral0: <Ralink Technology RT2561S> mem 0xcfef8000-0xcfefffff irq 10 at<br />device 10.0 on pci1</p>
<p>-ed</p> DragonFlyBSD - Bug #1921 (In Progress): we miss mlockallhttps://bugs.dragonflybsd.org/issues/19212010-11-24T16:19:21Zalexh
<p>We don't have the mlockall/munlockall syscalls as documented in [1]. We have at <br />least one tool in base that would benefit from it: cryptsetup. Hopefully someone <br />more familiar with the VM system can implement it without much effort as we <br />already have mlock/munlock.</p>
<p>Cheers,<br />Alex Hornung</p>
<p>[1]: <a class="external" href="http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html">http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html</a></p> DragonFlyBSD - Bug #1850 (New): volume-add on hammer root fs panichttps://bugs.dragonflybsd.org/issues/18502010-09-24T03:56:43ZJohannes.Hofmann
<p>Hi,</p>
<p>expanding a hammer root filesystem with hammer volume-add (which is<br />pretty cool btw) leads to a panic on shutdown:</p>
<p>panic: assertion: (bp->b_flags & B_LOCKED) 0 && iou->io.running <br />0 in hammer_io_deallocate</p>
<p>After a reboot everything is ok.<br />The problem can be reproduced in a vkernel.</p>
<pre><code>Johannes</code></pre>
<p>PS: One minor issue: The values df reports seem a bit off after<br /> the volume-add. They also are fine after a reboot.</p>
<p>Program received signal SIGTRAP, Trace/breakpoint trap.<br />Debugger (msg=0x8294114 "panic") at /usr/src/sys/platform/vkernel/i386/db_interface.c:334<br />334 in_Debugger = 0;<br />(gdb) bt<br />#0 Debugger (msg=0x8294114 "panic") at /usr/src/sys/platform/vkernel/i386/db_interface.c:334<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> 0x080e3bfd in panic (fmt=0x827b38c "assertion: %s in %s") at /usr/src/sys/kern/kern_shutdown.c:743<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> 0x08224a05 in hammer_io_deallocate (bp=0x5071f260) at /usr/src/sys/vfs/hammer/hammer_io.c:1093<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> 0x0812b79d in buf_deallocate (bp=0x5071f260) at /usr/src/sys/sys/buf2.h:239<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> brelse (bp=0x5071f260) at /usr/src/sys/kern/vfs_bio.c:1273<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> 0x0813f901 in vinvalbuf_bp (bp=0x5071f260, data=0x544659dc) at /usr/src/sys/kern/vfs_subr.c:424<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> 0x0813c8ae in buf_rb_tree_RB_SCAN (head=0x567de51c, scancmp=0x813c7bc <buf_rb_tree_SCANCMP_ALL>, <br /> callback=0x813f7e9 <vinvalbuf_bp>, data=0x544659dc) at /usr/src/sys/kern/vfs_subr.c:141<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> 0x0813f2b3 in vinvalbuf (vp=0x567de4c8, flags=1, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:334<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> 0x0813f434 in vclean_vxlocked (vp=0x567de4c8, flags=8) at /usr/src/sys/kern/vfs_subr.c:1142<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> 0x0813f622 in vgone_vxlocked (vp=0x567de4c8) at /usr/src/sys/kern/vfs_subr.c:1349<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> 0x0814212b in vflush_scan (mp=0x545c3fc0, vp=0x567de4c8, data=0x54465b4c) at /usr/src/sys/kern/vfs_mount.c:1252<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> 0x081422aa in vmntvnodescan (mp=0x545c3fc0, flags=2, fastfunc=0, slowfunc=0x81420ac <vflush_scan>, data=0x54465b4c)<br /> at /usr/src/sys/kern/vfs_mount.c:1068<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> 0x081424cd in vflush (mp=0x545c3fc0, rootrefs=0, flags=2) at /usr/src/sys/kern/vfs_mount.c:1184<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> 0x08213aa3 in devfs_unmount (mp=0x545c3fc0, mntflags=524288) at /usr/src/sys/vfs/devfs/devfs_vfsops.c:142<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> 0x08150d79 in vfs_unmount (mp=0x545c3fc0, mntflags=524288) at /usr/src/sys/kern/vfs_vfsops.c:123<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> 0x08145e40 in dounmount (mp=0x545c3fc0, flags=524288) at /usr/src/sys/kern/vfs_syscalls.c:755<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> 0x0813e3ae in vfs_umountall_callback (mp=0x545c3fc0, data=0x0) at /usr/src/sys/kern/vfs_subr.c:1714<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> 0x081427fb in mountlist_scan (callback=0x813e39b <vfs_umountall_callback>, data=0x0, how=<value optimized out>)<br /> at /usr/src/sys/kern/vfs_mount.c:900<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: extern uint64_t tsc_frequency missing (Closed)" href="https://bugs.dragonflybsd.org/issues/18">#18</a> 0x0813d9d3 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:1703<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: usched questions and a patch (Closed)" href="https://bugs.dragonflybsd.org/issues/19">#19</a> 0x080e3503 in boot (howto=8) at /usr/src/sys/kern/kern_shutdown.c:376<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: No detection of 8169S Gb interface (Closed)" href="https://bugs.dragonflybsd.org/issues/20">#20</a> 0x080e3801 in sys_reboot (uap=0x54465c94) at /usr/src/sys/kern/kern_shutdown.c:204<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: /etc/network.subr list_net_interfaces() fix (Closed)" href="https://bugs.dragonflybsd.org/issues/21">#21</a> 0x08271b77 in syscall2 (frame=0x54465d40) at /usr/src/sys/platform/vkernel/i386/trap.c:1221<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: RealTek 8169S/8110S support. (Closed)" href="https://bugs.dragonflybsd.org/issues/22">#22</a> 0x08271f42 in user_trap (frame=0x54465d40) at /usr/src/sys/platform/vkernel/i386/trap.c:410<br />#23 0x0827263e in go_user (frame=0x54465d38) at /usr/src/sys/platform/vkernel/i386/trap.c:1427<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: waitpid() with WUNTRACED flag? (was Re: Hang on ctrl+Z after the MPSAFE tsleep/wakeup commit) (Closed)" href="https://bugs.dragonflybsd.org/issues/24">#24</a> 0x0827290e in pmsg4 () at /usr/src/sys/platform/vkernel/i386/fork_tramp.s:103</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 #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>