DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082023-03-30T20:41:10ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3348 (New): Panic when trying to mount_hammer2 a filehttps://bugs.dragonflybsd.org/issues/33482023-03-30T20:41:10Zzabolekar
<p>Dragonfly 6.4.0.</p>
<p>Observed behavior: when I create a HAMMER2 file system on a regular file and try to mount it, I get a panic.<br />Expected behavior: Maybe the program should exit with an error message? I suspect I'm not supposed to do this kind of thing: the man page of mount_hammer2 says the file should be <em>special</em>.</p>
<p>To reproduce, as root:</p>
<pre><code class="shell syntaxhl" data-language="shell"><span class="nb">truncate</span> <span class="nt">-s</span> 1G hammer2.img
newfs_hammer2 hammer2.img
<span class="nb">mkdir </span>mnt
mount_hammer2 ~/hammer2.img mnt
</code></pre>
<p>This is the output after the last command:</p>
<pre>
hammer2_mount: devstr="/root/hammer2.img@DATA"
hammer2_mount: device="/root/hammer2.img" label="DATA" rdonly=0
panic: assertion "strncmp(path, "/dev/", 5) == 0" failed in hammer2_init_devvp a
t /usr/src/sys/vfs/hammer2/hammer2_ondisk.c:197
cpuid = 0
Trace beginning at frame 0xfffff800a9bbac18
hammer2_init_devvp() at hammer2_init_devvp+0x48b 0xffffffff8098589b
hammer2_init_devvp() at hammer2_init_devvp+0x48b 0xffffffff8098589b
hammer2_vfs_mount() at hammer2_vfs_mount+0x379 0xffffffff8096a4d9
sys_mount() at sys_mount+0x33b 0xffffffff80702d7b
syscall2() at syscall2+0x11e 0xffffffff80bdc0ae
Debugger("panic")
CPU0 stopping CPUs: 0x00000000
stopped
Stopped at Debugger+0x7c: movb $0,0xbcbd09(%rip)
db>
</pre> DragonFlyBSD - Bug #3224 (New): Kernel panic when trying to ping6https://bugs.dragonflybsd.org/issues/32242020-03-08T15:55:05Zzhtwroot@zta.lk
<p>I got a kernel panic on my vkernel trying to ping6 another vkernel on the same host.<br />I might have done an incorrect network configuration, but I guess it shouldn't panic anyway.</p>
<p>Here is what I've done.</p>
<p>Two fresh vkernels with ipv6_enable=yes in rc.conf started with:</p>
<p>/boot/kernel/kernel -m 1g -r /vhost/vm0.img -I /var/run/vknet</p>
<p>and</p>
<p>/boot/kernel/kernel -m 1g -r /vhost/vm1.img -I /var/run/vknet</p>
<p>vknetd is executed as "/usr/sbin/vknetd -U -t tap0".</p>
<p>I run the following version of DragonFly (on all three machines: host and both vkernels):</p>
<ol>
<li>uname -a<br />DragonFly 5.8-RELEASE DragonFly v5.8.0rc1.28.g3e3e37-RELEASE <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 1 17:46:44 CET 2020 <a class="email" href="mailto:root@fi.zta.lk">root@fi.zta.lk</a>:/usr/obj/usr/src/sys/VKERNEL64 x86_64</li>
</ol>
<p>On one of the vkernels I first check that I can ping the other one:</p>
<ol>
<li>ping6 fe80::201:71ff:fe0c:f607%vke0<br /><abbr title="56=40+8+8 bytes">PING6</abbr> fe80::201:68ff:fef8:f5f8%vke0 --> fe80::201:71ff:fe0c:f607%vke0<br />16 bytes from fe80::201:71ff:fe0c:f607%vke0, icmp_seq=1 hlim=64 time=0.371 ms<br />16 bytes from fe80::201:71ff:fe0c:f607%vke0, icmp_seq=2 hlim=64 time=0.262 ms<br />^C<br />--- fe80::201:71ff:fe0c:f607%vke0 ping6 statistics ---<br />3 packets transmitted, 2 packets received, 33.3% packet loss<br />round-trip min/avg/max/std-dev = 0.262/0.317/0.371/0.054 ms</li>
</ol>
<p>Then do the following to get the panic:</p>
<ol>
<li>route add -inet6 fe80::201:71ff:fe0c:f607 -iface vke0<br />add host fe80::201:71ff:fe0c:f607: gateway vke0</li>
</ol>
<ol>
<li>ping6 fe80::201:71ff:fe0c:f607<br /><abbr title="56=40+8+8 bytes">PING6</abbr> fe80::201:68ff:fef8:f5f8%vke0 --> fe80::201:71ff:fe0c:f607<br />panic: assertion "sdl->sdl_family == AF_LINK && sdl->sdl_alen != 0" failed in nd6_resolve at /usr/src/sys/netinet6/nd6.c:2031<br />cpuid = 0<br />Trace beginning at frame 0x8026783680<br />nd6_resolve() at 0x60ab55<br />nd6_resolve() at 0x60ab55<br />ether_output_frame() at 0x59427c<br />ip6_output() at 0x6026a1<br />rip6_output() at 0x610e9f<br />rip6_output() at 0x611446<br />Debugger("panic")</li>
</ol>
<p>CPU0 stopping CPUs: 0x0000000000000002<br /> stopped<br />Stopped at 0x70bde9: movb $0,0xa0c83c(%rip)<br />db> trace<br />Debugger() at 0x70bde9<br />panic() at 0x4c7710<br />nd6_resolve() at 0x60ab55<br />ether_output_frame() at 0x59427c<br />ip6_output() at 0x6026a1<br />rip6_output() at 0x610e9f<br />rip6_output() at 0x611446<br />netmsg_sync_handler() at 0x5a1739</p>
<p>--<br />Aleksej Lebedev</p> DragonFlyBSD - Bug #3124 (New): DragonFlyBSD 5.0.2 with Hammer2 with UEFI install doesn't boothttps://bugs.dragonflybsd.org/issues/31242018-03-04T09:01:41Zwiesl
<p>DragonFlyBSD 5.0.2 with Hammer2 with UEFI install doesn't boot<br />FATAL: Could not read from the boot medium! System halted.<br />Legacy BIOS install is OK.<br />Looks like that the boot installer isn't run.</p> DragonFlyBSD - Bug #2886 (New): dragonfly mail agent: sending a testmail causes high system loadhttps://bugs.dragonflybsd.org/issues/28862016-02-05T13:53:40Zworfitsuperhack@web.de
<p>When sending an email from dragonfly mail agent to a mailserver in the local network, the system load<br />increases up to > 80%. The remote mailserver (Postfix) speaks TLS via port 587 (submission)</p>
<p>However, the email cannot be sent:</p>
<p>remote delivery deferred: Peer did not provide certificate: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure</p>
<p>Since other mail servers - such as exim4, postfix, etc. - are able to send emails to the remote server,<br />I figure the problem is somewhere at the DMA.</p>
<p>This problem has been encountered on an IPFire (<a class="external" href="http://www.ipfire.org/">http://www.ipfire.org/</a>) firewall system running on an<br />ARM-board. Please see <a class="external" href="https://bugzilla.ipfire.org/show_bug.cgi?id=11036">https://bugzilla.ipfire.org/show_bug.cgi?id=11036</a> for the ticket in their bugtracker.</p>
<p>Best regards,<br />Timmothy Wilson</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 #2490 (New): nmalloc should color addresses to avoid cache bank conflictswhttps://bugs.dragonflybsd.org/issues/24902013-01-16T07:38:34Zvsrinivasvsrinivas@ops101.org
<p>nmalloc returns addresses without regard as to whether those addresses<br />will result in cache bank conflicts; cache bank conflicts will result<br />in wasting a fair amount of a CPU's load bandwidth, as seen in the<br />Himeno matrix benchmark, among others.</p>
<p>commit 8120f5e2a46e669c06a7afdd7de60fa6d6996f9d added simple cache<br />coloring to nmalloc for 32KB allocations, offsetting them by 4KB. While<br />it does work (and restores Himeno's performance), it can be substantially<br />improved on. We should look at doing so.</p>
<p>-- vs;</p> DragonFlyBSD - Bug #2489 (New): nmalloc doesn't cache VA for allocations > 8KBhttps://bugs.dragonflybsd.org/issues/24892013-01-16T01:00:42Zvsrinivasvsrinivas@ops101.org
<p>Recently x86-64's default C library allocator was switched back to nmalloc<br />from dmalloc for fragmentation concerns exposed by xulrunner. nmalloc doesn't<br />cache address space in userland for buffers larger than 8KB, which mean<br />hitting mmap allocations for any of those requests. Some limited form of<br />VA caching should improve performance in general and mitigate some-to-all<br />of the performance hit going back from dmalloc to nmalloc.</p>
<p>-- vs;</p> DragonFlyBSD - Bug #2324 (New): natacotrol support > 2TB not working even after the ftigeot patchhttps://bugs.dragonflybsd.org/issues/23242012-03-03T09:00:05Zzennygarbytrash@gmail.com
<p>natacontrol does not support above 2TB even after applying the patch (<a class="external" href="http://leaf.dragonflybsd.org/mailarchive/users/2012-02/msg00084.html">http://leaf.dragonflybsd.org/mailarchive/users/2012-02/msg00084.html</a>)</p> DragonFlyBSD - Bug #2287 (New): HAMMER(ROOT) Illegal UNDO TAIL signature at 300000001967c000https://bugs.dragonflybsd.org/issues/22872012-01-23T02:55:24Zy0n3t4n1
<p>Hello.</p>
<p>After having experienced a few panics, the root filesystem is<br />no longer able to be mounted, even in read-only mode:</p>
(booted from a USB stick)
<ol>
<li>mount -thammer -o ro /dev/da0s1d /mnt<br /><abbr title="ROOT">HAMMER</abbr> recovery check seqno=3364b54c<br /><abbr title="ROOT">HAMMER</abbr> Illegal UNDO TAIL signature at 300000001967c000<br /><abbr title="ROOT">HAMMER</abbr> recovery failure during seqno fwdscan<br /><abbr title="ROOT">HAMMER</abbr> recovery complete<br />Failed to recover HAMMER filesystem on mount<br />hammer: mount on /mnt: Input/output error</li>
</ol>
<p>I haven't tried `hammer recover' yet, as I have no idea what it does.<br />Is there anything I can do to recover from this situation? This is<br />a machine dedicated to testing DragonFly stability, so I can install<br />from scratch in the worst case.</p>
<p>The error message looks similar to the one described in issue1984,<br />but in this case even R/O mount fails.</p>
<p>The current kernel is built from 4f459, and it occasionally panics<br />even under almost no CPU or disk load. It could be a hardware failure,<br />but I couldn't find any indication of it as far as I watched the console<br />while it booted with the USB stick.<br />The previous kernel was built from 190f1b64, and it survived 10 days<br />without panic under pbulk load.</p>
<p>Best Regards,<br />YONETANI Tomokazu.</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 #2136 (New): socketpair() doesn't free file descriptors on copyout failurehttps://bugs.dragonflybsd.org/issues/21362011-09-24T23:04:13Zvsrinivasvsrinivas@ops101.org
<p>Hi,</p>
<p>sys_socketpair() has a copyout() to copy two file descriptors back to userspace;<br />if this copyout fails, the socketpair file descriptors are not freed.</p>
<p>-- vs</p> DragonFlyBSD - Bug #2085 (New): panic: assertion: (m->flags & PG_MAPPED) == 0 in vm_page_free_toqhttps://bugs.dragonflybsd.org/issues/20852011-06-10T14:48:55Zvsrinivasvsrinivas@ops101.org
<p>panic: assertion: (m->flags & PG_MAPPED) == 0 in vm_page_free_toq<br />cpuid = 0<br />Trace beginning at frame 0x5a353a3c<br />panic(ffffffff,0,82aca08,5a353a70,59e225e0) at 0x80ece4d<br />panic(82aca08,82f40e2,82f4611,5c17f0bc,b8aa3b29) at 0x80ece4d<br />vm_page_free_toq(506f4b28,5a28306c,5a353aa4,506f4b28,506f4b28) at 0x8281544<br />vm_object_deallocate(506f4b28,0,0,0,0) at 0x827ea1d<br />vm_page_rb_tree_RB_SCAN(5a411aa0,827f1e0,827e9b4,0,59e225e0) at 0x827f2e6<br />vm_object_terminate(5a411a8c,5a353b0c,80f9b91,83cf7c0,59e226f4) at 0x827d45c<br />vm_object_deallocate_locked(5a411a8c,5a353b88,8279076,5a411a8c,843db0c) at 0x827e7e2<br />vm_object_deallocate(5a411a8c,843db0c,28238000,5a353b68,82a7a9c) at 0x827e855<br />vm_map_delete(5721e1b8,0,bfc00000,5a353ba0,12) at 0x8279076<br />vm_map_remove(5721e1b8,0,bfc00000,59b99f60,59aea648) at 0x8279109<br />vm_map_remove(5721e1b8,59b99f60,5a353bf0,5721e2bc,59e225e0) at 0x827918d<br />_sysref_put(5721e2bc,0,82a54d6,50458248,59b99f60) at 0x80c3872<br />exit1(0,5a353cc0,82a2365,5a353c7c,5a353c8c) at 0x80d997b<br />sys_exit(5a353c7c,5a353c8c,4,571a5305,5721e1b8) at 0x80d9d30<br />syscall2(5a353d40,40400bf4,5a353cf0,0,0) at 0x82a2365<br />user_trap(5a353d40,1,5a353d40,59e2280c,28338360) at 0x82a25d9<br />go_user(5a353d38,0,0,7b,0) at 0x82a2ad7</p>
<p>Panic with most recent vm_object token fixes on a vkernel (so no kernel<br />core/dump). Running vm stress program: <a class="external" href="http://leaf.dragonflybsd.org/~vsrinivas/vm.c">http://leaf.dragonflybsd.org/~vsrinivas/vm.c</a></p> DragonFlyBSD - Bug #2071 (New): Panic on assertion: (int)(flg->seq - seq) > 0 in hammer_flusher_f...https://bugs.dragonflybsd.org/issues/20712011-05-14T19:20:34Zvsrinivasvsrinivas@ops101.org
<p>ad10: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1500424384<br />ad10: FAILURE - WRITE_DMA48 status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND><br />LBA=1500424384<br /><abbr title="NEWTANK">HAMMER</abbr>: Critical error inode=-1 error=5 while flushing meta-data<br /><abbr title="NEWTANK">HAMMER</abbr>: Forcing read-only mode<br />hammer: debug: forcing async flush ip 000000032433ccec<br />hammer: debug: forcing async flush ip 000000032433ccec<br />panic: assertion: (int)(flg->seq - seq) > 0 in hammer_flusher_flush<br />Trace beginning at frame 0xcbfadd10<br />panic(ffffffff,c07ace20,c064b39b,cbfadd40,cbfa00fc) at panic+0x101<br />panic(c064b39b,c067760e,c06353b6,0,cbfa0108) at panic+0x101<br />hammer_flusher_master_thread(cbfa0000,0,0,0,0) at hammer_flusher_master_thread+0x14e<br />lwkt_exit() at lwkt_exit<br />Uptime: 5d16h20m44s<br />Physical memory: 502 MB<br />Dumping 205 MB: 190 174 158 142 126 110 94 78 62 46 30 14</p>
<p>After an inode failure, HAMMER paniced on an assertion in hammer_flusher_flush.<br />ad10 was a WD EARS 1.5TB disk attached to a Silicon Image 3114 controller,<br />running via nata. The only I/O to the disk was a mirror-stream.</p>
<p>core and kernel are on leaf.dragonflybsd.org, /home/vsrinivas/hammerpanic.</p> DragonFlyBSD - Bug #1920 (New): system hangshttps://bugs.dragonflybsd.org/issues/19202010-11-22T16:59:00Zzhtwroot@zta.lk
<p>System hangs once in a while leaving on the console these messages:</p>
<p>====<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed<br />pfr_unroute_kentry: delete failed</p>
<p>panic: IP header no in one mbuf<br />mp_lock = ffffffff; cpuid=1<br />Trace beginning at frame 0xffffffe03d9b0a60<br />panic() at panic+0x239<br />panic() at panic+0x239<br />ip_input() at ip_input+0x153<br />ip_input_handler() at ip_input_handler+0xd<br />netmsg_service_lookp() at netmsg_service_loop_0x6f<br />Debugger("panic")</p>
<p>CPU1 stopping CPU: 0x00000001<br />stopped<br />Stopped at Debugger+0x39 movh $0,0x387060(%rid)
====</p>
<p>I couldn't grub this from the screen and copied it by hands, so there can be typos.</p>
<ol>
<li>uname -a<br />DragonFly chinua.zzz.umc8.ru 2.8-RELEASE DragonFly v2.8.2.38.gb1139-RELEASE <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>:<br />Mon Nov 22 10:06:11 MSK 2010 <br /><a class="email" href="mailto:root@chinua.zzz.umc8.ru">root@chinua.zzz.umc8.ru</a>:/usr/obj/usr/src/sys/X86_64_GENERIC_SMP x86_64</li>
</ol>
<p>The dmesg.boot is in attach</p> DragonFlyBSD - Bug #1185 (New): need a tool to merge changes into /etchttps://bugs.dragonflybsd.org/issues/11852008-12-20T07:47:08Zwa1ter
<p>I run mergemaster occasionally because it catches files that<br />make upgrade misses. Today it misses about half a dozen or<br />so, including aliases, ftpusers, /usr/Makefile, and maybe a<br />few others I can't remember.</p>
<p>Thanks.</p>