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 - 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 #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 #2556 (Feedback): DragonFly v3.5.0.81.gd3479 - Process signal weirdnesshttps://bugs.dragonflybsd.org/issues/25562013-05-07T22:59:34Ztuxillo
<p>Hi,</p>
<p>tmux has a memory leak somewhere and it was causing a lot of swap memory to be used. I started using truss(1) to see what it was doing and after 3-4 tracing attempts the tmux process was stuck in status "stopevent". After sending to it all sorts of signals (CONT, HUP, KILL) the process is kept stopped in the same situation. I also tried disabling tracing with ktrace(1) but it didn't help.</p>
<p>Eventually I tried to reboot the virtual machine but it got stuck for around 10 minutes without actually being able to shutdown. Last step was dropping to DDB and producing a dump. Dump is available on leaf on demand. See below the backtrace of the thread involved (tmux process)</p>
<p>Best regards,<br />Antonio Huete</p>
<hr />
<p>(kgdb) thread 26<br />[Switching to thread 26 (pid 835/0, tmux)]<br />#0 0xffffffff8050dfb0 in lwkt_switch () at /home/source/dfbsd/sys/kern/lwkt_thread.c:872<br />872 /home/source/dfbsd/sys/kern/lwkt_thread.c: No such file or directory.<br />(kgdb) bt<br />#0 0xffffffff8050dfb0 in lwkt_switch () at /home/source/dfbsd/sys/kern/lwkt_thread.c:872<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> 0xffffffff80518f0e in tsleep (ident=ident@entry=0xffffffe071efc990, flags=flags@entry=1024, <br /> wmesg=wmesg@entry=0xffffffff8097e168 "stopevent", timo=timo@entry=0) at /home/source/dfbsd/sys/kern/kern_synch.c:612<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> 0xffffffff80538091 in stopevent (p=p@entry=0xffffffe071efc780, event=event@entry=4, val=val@entry=7)<br /> at /home/source/dfbsd/sys/kern/sys_process.c:771<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> 0xffffffff808c5a7a in syscall2 (frame=0xffffffe07280e9f8) at /home/source/dfbsd/sys/platform/pc64/x86_64/trap.c:1229<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> 0xffffffff808af75b in ?? () at /home/source/dfbsd/sys/platform/pc64/x86_64/exception.S:323<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> 0x00000000000000c5 in ?? ()<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> 0x0000000000000000 in ?? ()</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 #2100 (Feedback): devfs related panichttps://bugs.dragonflybsd.org/issues/21002011-07-08T12:02:36Zsepherosa
<p>Hi all,</p>
<p><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> 0xffffffff802e8a1f in dssetmask (dev=0xffffffe085418f50,<br />mode=<value optimized out>, flags=<value optimized out>,<br /> sspp=<value optimized out>, info=<value optimized out>) at<br />/usr/src/sys/sys/diskslice.h:349<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> dsopen (dev=0xffffffe085418f50, mode=<value optimized out>,<br />flags=<value optimized out>, sspp=<value optimized out>,<br /> info=<value optimized out>) at /usr/src/sys/kern/subr_diskslice.c:741<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> 0xffffffff802e45ff in diskopen (ap=0xffffffe0ba9c3798) at<br />/usr/src/sys/kern/subr_disk.c:956<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> 0xffffffff802a3e1c in dev_dopen (dev=0xffffffe085418f50,<br />oflags=8192, devtype=195, cred=0x1f) at<br />/usr/src/sys/kern/kern_device.c:151<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> 0xffffffff803e9c02 in devfs_spec_open (ap=0xffffffe0ba9c3838) at<br />/usr/src/sys/vfs/devfs/devfs_vnops.c:919<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> 0xffffffff8033c61c in vop_open (ops=0xffffffe0ad0d2e00,<br />vp=0xffffffe0bb1d6c48, mode=1, cred=0xffffffe0ae317868,<br />fp=0xffffffe08518ad58)<br /> at /usr/src/sys/kern/vfs_vopops.c:289<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> 0xffffffff80339ec6 in vn_open (nd=0xffffffe0ba9c3a98, fp=<value<br />optimized out>, fmode=1, cmode=<value optimized out>)<br /> at /usr/src/sys/kern/vfs_vnops.c:284<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> 0xffffffff80336c5d in kern_open (nd=0xffffffe0ba9c3a98,<br />oflags=<value optimized out>, mode=<value optimized out>,<br /> res=<value optimized out>) at /usr/src/sys/kern/vfs_syscalls.c:1836<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> 0xffffffff80336eb6 in sys_open (uap=0xffffffe0ba9c3b58) at<br />/usr/src/sys/kern/vfs_syscalls.c:1946<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> 0xffffffff8048f652 in syscall2 (frame=0xffffffe0ba9c3c08) at<br />/usr/src/sys/platform/pc64/x86_64/trap.c:1188<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> 0xffffffff80487c1f in Xfast_syscall () at<br />/usr/src/sys/platform/pc64/x86_64/exception.S:320</p>
<p>core dump is uploaded to sephe@leaf:crash/vmcore0.tbz</p>
<p>It happened after following stuffs were done by my friend:<br />- a sata disk was plugged into the esata port, and the disk was detected as da1<br />- dd if=/dev/zero of=/dev/da1, something like that<br />- unplug the sata disk<br />- after a short while, another sata disk was plugged in the same esata port<br />- this time no message showed about anything related to /dev/da1<br />- run the above dd command again, panic</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #2081 (Feedback): Panic on device "detach" / "failure"https://bugs.dragonflybsd.org/issues/20812011-05-24T22:27:54Zvsrinivasvsrinivas@ops101.org
<p>...<br />ad10: FAILURE - device detached<br />subdisk10: detached<br />ad10: detached</p>
<p>Fatal trap 12: page fault while in kernel mode<br />fault virtual address = 0xa4<br />fault code = supervisor write, page not present<br />instruction pointer = 0x8:0xc03457e3<br />stack pointer = 0x10:0xc96aac44<br />frame pointer = 0x10:0xc96aac5c<br />code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1<br />processor eflags = interrupt enabled, resume, IOPL = 0<br />current process = Idle<br />current thread = pri 14 (CRIT)</p>
<p>trap number = 12<br />panic: page fault<br />Trace beginning at frame 0xc96aab20<br />panic(ffffffff,c07ace20,c064edd8,c96aab50,c96aabfc) at panic+0x101<br />panic(c064edd8,c067eace,1,1,1) at panic+0x101<br />trap_fatal(0,0,1,1,3130) at trap_fatal+0x33f<br />trap_pfault(c034d4b3,c7d8c9f8,0,c96aabe4,a4) at trap_pfault+0x13c<br />trap(c96aabfc) at trap+0x4c6<br />calltrap() at calltrap+0xd<br />--- trap 0, eip = 0x2, esp = 0x10296, ebp = 0x1 ---<br />Uptime: 2d21h28m20s<br />Physical memory: 502 MB<br />Dumping 204 MB: 189 173 157 141 125 109 93 77 61 45 29 13</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 #1580 (Feedback): Panic (Fatal trap 12: page fault while in kernel mode) while...https://bugs.dragonflybsd.org/issues/15802009-10-20T13:52:19Zrumcic
<p>Not quite sure if the problem is in either of the two aforementioned acts or in<br />the combination, but while doing that (with netif names I'm thinking<br />of "ifconfig some_netif name new_name") I was able to panic the machine.</p>
<p>After getting "kernel: Non-unique normal route, mask not entered" in the dmesg<br />(immediatelly after loading my custom pf.conf - do note, that it does not<br />happen all the time, loaded the rules quite a few times to get this message),<br />I loaded my pf.conf again (pfctl -f /etc/pf.conf) and the machine fortunately<br />panicked for me (in the previous two instances of this problem, the machine<br />hanged and was completely unresponsive ... to ping, serial console, everything<br />was dead).</p>
<p>The dump is located at leaf:~rumko/crash/pf/ 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> 0xc0209e2d in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:378<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> 0xc020a0f2 in panic (fmt=0xc0403d38 "%s")<br />at /usr/src/sys/kern/kern_shutdown.c:813<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> 0xc03d29f6 in trap_fatal (frame=0xddf26770, eva=<value optimized out>)<br />at /usr/src/sys/platform/pc32/i386/trap.c:1093<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> 0xc03d2b30 in trap_pfault (frame=0xddf26770, usermode=0, eva=305406860)<br />at /usr/src/sys/platform/pc32/i386/trap.c:994<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> 0xc03d314e in trap (frame=0xddf26770)<br />at /usr/src/sys/platform/pc32/i386/trap.c:674<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> 0xc03bd927 in calltrap ()<br />at /usr/src/sys/platform/pc32/i386/exception.s:785<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> 0xc02a3d21 in rn_walktree (h=0xc39f9080, f=0xc029d5db <pfr_walktree>,<br />w=0xddf267e0) at /usr/src/sys/net/radix.c:996<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> 0xc029bbe4 in pfr_mark_addrs (kt=0xdddf3c00)<br />at /usr/src/sys/net/pf/pf_table.c:723<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> 0xc029f1c1 in pfr_commit_ktable (kt=0xdddf3c00, tzero=1255984339)<br />at /usr/src/sys/net/pf/pf_table.c:1596<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> 0xc029f44a in pfr_ina_commit (trs=0xddf26a18, ticket=4, nadd=0x0,<br />nchange=0x0, flags=<value optimized out>)<br />at /usr/src/sys/net/pf/pf_table.c:1566<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> 0xc029792d in pfioctl (ap=0xddf26b8c)<br />at /usr/src/sys/net/pf/pf_ioctl.c:2669<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> 0xc01f05fe in dev_dioctl (dev=0xc3a24b80, cmd=3222029394,<br />data=0xddf26c18 "\r", fflag=3, cred=0xdd8f1478, msg=0xddf26cf0)<br /> at /usr/src/sys/kern/kern_device.c:174<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> 0xc032e7ef in devfs_specf_ioctl (fp=0xdd3e5958, com=3222029394,<br />data=0xddf26c18 "\r", ucred=0xdd8f1478, msg=0xddf26cf0)<br /> at /usr/src/sys/vfs/devfs/devfs_vnops.c:1354<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> 0xc022d92d in mapped_ioctl (fd=3, com=3222029394, uspc_data=0xbfbff584<br /><Address 0xbfbff584 out of bounds>, map=0x0, msg=0xddf26cf0)<br /> at /usr/src/sys/sys/file2.h:88<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> 0xc022d9b6 in sys_ioctl (uap=0xddf26cf0)<br />at /usr/src/sys/kern/sys_generic.c:521<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> 0xc03d37a9 in syscall2 (frame=0xddf26d40)<br />at /usr/src/sys/platform/pc32/i386/trap.c:1339<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> 0xc03bd9d6 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: extern uint64_t tsc_frequency missing (Closed)" href="https://bugs.dragonflybsd.org/issues/18">#18</a> 0x2811ac63 in ?? ()<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)<br />-- <br />Regards,<br />Rumko</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 #1332 (Feedback): DFBSD 2.2 - Booting usbcdrom/usbsticks on thinkpad hangs on ...https://bugs.dragonflybsd.org/issues/13322009-04-09T19:44:06Ztuxillo
<p>Hi</p>
<p>This is a bug reported by claus on the IRC and initally investigated by Jordan<br />(smtms).</p>
<p>It seems that booting USB cdrom/stick on a Thinkpad (model still to determine)<br />hangs and stops with BTX Halted.</p>
<p>claus reported that FBSD 7.1 booted without problems with that USB Cdrom drive,<br />but with FBSD 7.0 it crashes also.</p>
<p>This is a know issue on FreeBSD that was fixed in revision 177039. Also relevant<br />revisions are 181433, 181436 and 189017.</p>
<p>Cheers,<br />Antonio</p> DragonFlyBSD - Bug #1282 (Feedback): panic (trap 12) when booting SMP kernel on Atom 330 (dual core)https://bugs.dragonflybsd.org/issues/12822009-02-16T05:37:23Ztomaz.borstnar
<p>Hello!</p>
<pre><code>I am playing with Atom 330 Dual Core P945GC combination which works fine under generic kernel, but crashes with trap 12 <br />as soon as all physical and virtual cores are printed to the screen while booting. Anyone else playing with similar setup?</code></pre>
<p>Tomaž</p> DragonFlyBSD - Bug #806 (Feedback): boot error on MacBookhttps://bugs.dragonflybsd.org/issues/8062007-09-12T04:00:13Ztralamazza
<p>Hi,<br /> I'm trying to boot Dragonfly (1.10.1_REL) on a MacBook (1st gen). After the <br />booting process starts it enters a loop and displays "<db>" indefinitely.</p>
<p>On a side note Freebsd has a related project on google SoC: <br /><a class="external" href="http://wiki.freebsd.org/AppleMacbook">http://wiki.freebsd.org/AppleMacbook</a></p>
<p>thanks</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>