DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082017-12-17T19:17:50ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3113 (In Progress): Booting vKernel fails due being out of swap spacehttps://bugs.dragonflybsd.org/issues/31132017-12-17T19:17:50Ztcullen
<p>The step by step directions at <a class="external" href="https://www.dragonflybsd.org/docs/handbook/vkernel/">https://www.dragonflybsd.org/docs/handbook/vkernel/</a> fail because when you attempt to boot the vkernel you never get a shell prompt because the shell is instantly and repeatedly killed due to a never ending stream of "out of swap space" error messages.</p> DragonFlyBSD - Bug #3111 (In Progress): Mouse lags every second heavily under X11https://bugs.dragonflybsd.org/issues/31112017-12-10T17:30:40Zmneumann
<p>Mouse moves normal for one second, then completely stops for roughly one second, then moves again for a second.<br />The whole repeats infinitivly.</p>
<p>This commit has <strong>no</strong> mouse lag: e0a1e7abb95f53e4b0c633f57fbd3ba163a98e73<br />This commit has mouse lag: d6c92fb146a95bd38feaa94c8d2bafda63600e8e</p>
<p>I first assumed it is either one of the commits related to evdev support, so I reverted them:</p>
<pre><code>d3d1dd3e4513b2ab753f8ba52f144dc916420ba6<br /> 3ea800bb832ad69c10f85ce9bce98efd8e892285<br /> eaf0d054af4aa304548c1efc497aad966b86a590</code></pre>
<p>But the mouse lag still happens. Next I reverted the recent drm/radeon commit:</p>
<pre><code>d235ee5f3490f63ba738915974154a0e2e49378d</code></pre>
<p>But mouse lag still there. So I assume it must be one of dillon's commits on 5th or 6th December.</p>
<p>Anyone else seeing the problem? I can easily bisect the problem, as it's only 6 commits. But maybe dillon can see the problem faster.</p> DragonFlyBSD - Bug #2736 (New): kernel panics on acpi_timer_probe functionhttps://bugs.dragonflybsd.org/issues/27362014-11-17T19:14:54Zcnbcneirabustos@gmail.com
<p>Booting with acpi module enable and hpet disabled in loader.conf results in a kernel panic, I'm unable to type anything in ddb as the the system is frozen<br />The hardware is a gobook vr-2 general dynamics itronix IX605 bios version 124. I'll update to bios version 125 and update the ticket if needed.</p> DragonFlyBSD - Bug #2735 (New): iwn panics SYSSASSERThttps://bugs.dragonflybsd.org/issues/27352014-11-14T22:04:08Zcnbcneirabustos@gmail.com
<p>iwn driver panics with SYSASSERT error that is described in this link<br /><a class="external" href="http://lists.freebsd.org/pipermail/freebsd-wireless/2013-July/003653.html">http://lists.freebsd.org/pipermail/freebsd-wireless/2013-July/003653.html</a></p> DragonFlyBSD - Bug #2547 (New): crashed while doing a dry run of pkg_rolling-replacehttps://bugs.dragonflybsd.org/issues/25472013-04-14T05:52:07Zphma
<p>I rebooted into a kernel compiled from sources I updated just a few days ago. I ran pkg_rolling-replace -nuv and it ran for a few hours, then crashed. The kernel dump is number 14 in my crash directory. The version is v3.5.0.25.g97861-DEVELOPMENT.</p>
<p>(kgdb) #0 _get_mycpu () at ./machine/thread.h:79<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> md_dumpsys (di=0xc03e8b35)<br /> at /usr/src/sys/platform/pc32/i386/dump_machdep.c:266<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> 0xc09646a0 in db_command_table ()<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> 0xc03e8b35 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:913<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> 0xc01968a3 in db_fncall (dummy1=-831973476, dummy2=0, dummy3=-1065827167, <br /> dummy4=0xce691798 "(\361~\300\336L\212\300")<br /> at /usr/src/sys/ddb/db_command.c:539<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> 0xc0196ca2 in db_command (aux_cmd_tablep_end=<optimized out>, <br /> aux_cmd_tablep=<optimized out>, cmd_table=<optimized out>, <br /> last_cmdp=0xc09f9318) at /usr/src/sys/ddb/db_command.c:401<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> db_command_loop () at /usr/src/sys/ddb/db_command.c:467<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> 0xc019984b in db_trap (type=type@entry=12, code=code@entry=0)<br /> at /usr/src/sys/ddb/db_trap.c:71<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> 0xc07903d0 in kdb_trap (type=type@entry=12, code=code@entry=0, <br /> regs=regs@entry=0xce69190c)<br /> at /usr/src/sys/platform/pc32/i386/db_interface.c:149<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> 0xc07c2602 in trap_fatal (frame=frame@entry=0xce69190c, eva=eva@entry=136)<br /> at /usr/src/sys/platform/pc32/i386/trap.c:1107<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> 0xc07c27bd in trap_pfault (frame=frame@entry=0xce69190c, usermode=0, <br /> usermode@entry=136, eva=eva@entry=136)<br /> at /usr/src/sys/platform/pc32/i386/trap.c:1018<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> 0xc07c2dc3 in trap (frame=0xce69190c)<br /> at /usr/src/sys/platform/pc32/i386/trap.c:695<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> 0xc0791c37 in calltrap ()<br /> at /usr/src/sys/platform/pc32/i386/exception.s:787<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> 0xc0686b17 in fq_balance_self (tdio=0xc09edf00)<br /> at /usr/src/sys/kern/dsched/fq/fq_core.c:351<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)</p>
<p>I also saw it freeze the first time I started a kde session after rebooting.</p> DragonFlyBSD - Bug #2499 (In Progress): DRAGONFLY_3_2 lockd not responding correctlyhttps://bugs.dragonflybsd.org/issues/24992013-01-22T08:41:27ZNerzhul
<p>Hello,<br />i must use lockd for concurrent access on a webserver with nfs extended storage. There is some concurrent access and lockd isn't responding correctly.</p>
<p>On the NFSv3 client, timeout appears and console logs:<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd is alive again<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd is alive again<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd is alive again<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd is alive again<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd is alive again<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd not responding<br />nfs server A.B.C.65:/nfs/fbsd_pkg: lockd is alive again</p>
<p>After "netstat -an -f inet" i see there is a queue on rpc socket</p>
<p>netstat -an -f inet</p>
<p>Active Internet connections (including servers)<br />Proto Recv-Q Send-Q Local Address Foreign Address (state)<br />tcp4 0 0 A.B.C.65.nfsd WebCluster1.977 ESTABLISHED<br />tcp4 0 0 A.B.C.65.nfsd WebCluster1.611 ESTABLISHED<br />tcp4 0 0 localhost.smtp <strong>.* LISTEN<br />tcp4 0 0 *.ssh *.</strong> LISTEN<br />tcp4 0 0 <strong>.1017 *.</strong> CLOSED<br />tcp4 0 0 <strong>.1020 *.</strong> LISTEN<br />tcp4 0 0 <strong>.nfsd *.</strong> LISTEN<br />tcp4 0 0 <strong>.1023 *.</strong> LISTEN<br />tcp4 0 0 <strong>.1022 *.</strong> LISTEN<br />tcp4 0 0 <strong>.sunrpc *.</strong> LISTEN<br />tcp4 0 0 A.B.C.65.nfsd A.B.C.96.811 ESTABLISHED<br />tcp4 0 0 A.B.C.65.nfsd WebCluster1.972 ESTABLISHED<br />tcp4 0 48 A.B.C.65.ssh 129.175.196.190.60067 ESTABLISHED<br />udp4 0 0 <strong>.918 *.</strong> <br />udp4 0 0 A.B.C.65.1028 ntp.u-psud.fr.ntp <br />udp4 456 0 <strong>.1017 *.</strong> <br />udp4 18656 0 <strong>.1018 *.</strong> <br />udp4 0 0 <strong>.nfsd *.</strong> <br />udp4 0 0 <strong>.1021 *.</strong> <br />udp4 0 0 <strong>.1020 *.</strong> <br />udp4 0 0 <strong>.1022 *.</strong> <br />udp4 0 0 <strong>.sunrpc *.</strong></p>
<p>When i see that, i make tcpdump -nni em0 to see what's happening:</p>
<p>22:12:42.781597 IP 10.117.100.95.961 > 10.117.100.65.1017: UDP, length 212<br />22:12:48.801935 IP 10.117.100.95.961 > 10.117.100.65.1017: UDP, length 212<br />22:12:54.669917 IP 10.117.100.95.961 > 10.117.100.65.1017: UDP, length 212<br />22:13:00.148965 IP 10.117.100.95.961 > 10.117.100.65.1017: UDP, length 212</p>
<p>After a little time, lockd respond to all request, but many failed because of timeout</p>
<p>On the dragonflyBSD server i can see this in /var/log/messages</p>
<p>Jan 21 22:14:19 webfiler1 rpc.lockd: duplicate lock from WebCluster1.srv.<br />Jan 21 22:14:19 webfiler1 last message repeated 3 times<br />Jan 21 22:14:19 webfiler1 rpc.lockd: no matching entry for WebCluster1.srv.<br />Jan 21 22:14:29 webfiler1 dntpd<sup><a href="#fn571">571</a></sup>: issuing offset adjustment: 0.026637s<br />Jan 21 22:14:44 webfiler1 rpc.lockd: rpc to statd failed: RPC: Timed out<br />Jan 21 22:14:44 webfiler1 rpc.lockd: duplicate lock from WebCluster1.srv.<br />Jan 21 22:14:44 webfiler1 last message repeated 3 times<br />Jan 21 22:14:44 webfiler1 rpc.lockd: no matching entry for WebCluster1.srv.</p>
<p>I think there is a problem on DragonFlyBSD which queue many lockd requests.</p> DragonFlyBSD - Bug #2423 (New): After multiple panics/locks, hitting KKASSERT in hammer_init_cursorhttps://bugs.dragonflybsd.org/issues/24232012-09-17T17:12:40Zrumcic
<p>After quite a few locks (machine stopped responding, nothing on serial console, unable to panic the machine), the hammer FS (v6) got a corrupted(?) UNDO.</p>
<p>Booting the latest snapshot and mounting with ro,noatime it looked as if it was able to rerun the UNDO/FIFO. But trying to mount the "clean" FS result in triping over a KKASSERT (error == 0 at hammer_cursor.c:202)</p> DragonFlyBSD - Bug #2296 (In Progress): panic: assertion "m->wire_count > 0" failedhttps://bugs.dragonflybsd.org/issues/22962012-02-02T06:56:02Zthomas.nikolajsen
<p>With recent (29/1-12) master and rel3_0 I get this panic<br />during parallel make release and buildworld, e.g.:<br />'make MAKE_JOBS=10 release' (i.e. make -j10)<br />i386 STANDARD<br />(custom kernel, includes INCLUDE_CONFIG_FILE)<br />on 8 core host (opteron).</p>
<p>Got this panic twice; succeeds w/o MAKE_JOBS</p>
<p>Core dump at leaf: ~thomas:crash/octopus.i386.3</p> DragonFlyBSD - Bug #2141 (New): loader and/or documentation brokenhttps://bugs.dragonflybsd.org/issues/21412011-10-09T14:15:29Zsjg
<p>For example,</p>
<pre><code>The ehci driver is automatically loaded upon boot. To disable this<br /> behavior temporarily, the ehci_load variable can be unset at the loader<br /> prompt (see loader(8)). To disable it permanently, the<br /> hint.ehci.0.disabled tunable can be set to 1 in /boot/loader.conf.</code></pre>
<p>But when operating from the loader prompt the ehci_load variable has no effect <br />at all, it seems to only be checked from the menu, which is useless if you are <br />operating from the prompt.</p>
<p>This is confusing at best, but I am leaning more towards steaming pile. The <br />loader or the documentation needs to be reworked.</p> DragonFlyBSD - Bug #2140 (New): hammer_io_delallocate panic with 'duplicate entry' messagehttps://bugs.dragonflybsd.org/issues/21402011-10-06T20:04:53Zttw
<p>Getting regular panics on HAMMER FSs when transferring large quantities of data <br />over the network. initally saw the issue with NFS but eliminated that and now <br />seeing it with 'tar' piped across 'ssh'. was most prevelant when using USB or <br />FW storage but most recent test to internal IDE drive has thrown up the same <br />error.</p>
<p>NB: transfers are generally across unreliable links (i.e. wireless) and oft-<br />times, long stalls (i.e. minutes) occur -- most recent crash was after i had <br />paused a 'tar/ssh' transfer using CTL-Z.</p>
<p>NB: turning on crashdumps and re-executing tests but may take hours to fail - <br />any pointers in the meantime would be excellent.</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> DragonFlyBSD - Bug #884 (In Progress): Performance/memory problems under filesystem IO loadhttps://bugs.dragonflybsd.org/issues/8842007-12-14T18:34:28Zhasso
<p>During testing drive with dd I noticed that there are serious performance <br />problems. Programs which need disk access, block for 10 and more seconds. <br />Sometimes they don't continue the work until dd is finished. Raw disk access <br />(ie not writing to file, but directly to the disk) is reported to be OK (I <br />can't test it myself).</p>
<p>All tests are done with this command:<br />dd if=/dev/zero of=./file bs=4096k count=1000</p>
<p>Syncing after each dd helps to reproduce it more reliably (cache?).</p>
<p>There is one more strange thing in running these tests. I looked at memory <br />stats in top before and after running dd.</p>
<p>Before:<br />Mem: 42M Active, 40M Inact, 95M Wired, 304K Cache, 53M Buf, 795M Free<br />After:<br />Mem: 70M Active, 679M Inact, 175M Wired, 47M Cache, 109M Buf, 1752K Free</p>
<p>And as a side effect - I can't get my network interfaces up any more after <br />running dd - "em0: Could not setup receive strucutres".</p> DragonFlyBSD - Bug #599 (New): 1.9.0 reproducable panichttps://bugs.dragonflybsd.org/issues/5992007-04-11T10:24:26Zpavalos
<p>Here's a panic I'm getting with some pretty serious network (www) load, then <br />doing a netstat -an:</p>
<p>Unread portion of the kernel message buffer:<br />panic: m_copydata, negative off -1<br />mp_lock = 00000000; cpuid = 0; lapic.id = 00000000<br />boot() called on cpu#0</p>
<p>syncing disks... 5<br />done<br />Uptime: 12d22h0m32s</p>
<p>(kgdb) bt<br />#0 dumpsys () at 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> 0xc01954bb in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:370<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> 0xc01957c0 in panic (fmt=Variable "fmt" is not available.<br />) at /usr/src/sys/kern/kern_shutdown.c:767<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> 0xc01c3a32 in m_copydata (m=0x0, off=0, len=0, cp=0xee9534b0 "\001\001<br />\b\n\006¦*$\035\bͬ") at /usr/src/sys/kern/uipc_mbuf.c:1014<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> 0xc020fc25 in tcp_output (tp=0xdae0c720) <br />at /usr/src/sys/netinet/tcp_output.c:690<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> 0xc02152bf in tcp_timer_persist (xtp=0xdae0c720) <br />at /usr/src/sys/netinet/tcp_timer.c:363<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> 0xc01a6423 in softclock_handler (arg=0xc0386a80) <br />at /usr/src/sys/kern/kern_timeout.c:307<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> 0xc019d037 in lwkt_deschedule_self (td=Variable "td" is not available.<br />) at /usr/src/sys/kern/lwkt_thread.c:207<br />Previous frame inner to this frame (corrupt stack?)</p>
<p>The kernel and vmcore is being uploaded to leaf. The source is from March 28.</p>
<p>--Peter</p>