DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082010-12-18T16:41:50ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #1939 (New): Panic on nightly build and stress test boxhttps://bugs.dragonflybsd.org/issues/19392010-12-18T16:41:50Zlentferj
<p>Tonight my VM that runs nightly builds of master and sysbench and <br />apachebench stress tests paniced.</p>
<p>db> trace<br />Debugger(c05ddab0) at Debugger+0x34<br />panic(c05e021b,ffffffff,34,c,34) at panic+0x17a<br />m_copydata(0,ffffffff,1,cfa808d4,cce0fb04) at m_copydata+0x1e<br />tcp_output(d0428cd8) at tcp_output+0xbc7<br />tcp_input(cce0fcb4,cce0fcb0,6) at tcp_input+0x36fa<br />transport_processing_oncpu(c0315528,14,0,0,0) at transport_processing_onc<br />ip_input(cfa80800) at ip_input+0xe46<br />ip_input_handler(cfa80818) at ip_input_handler+0xe<br />netmsg_service_loop(0,0,0,0,0) at netmsg_service_loop+0x58<br />lwkt_exit() at lwkt_exit</p>
<p>I put the core in my ~/crash on leaf, nbuild_panic.tar.bz2.</p>
<p>Jan</p> DragonFlyBSD - Bug #1935 (New): mouse does not work after switching between x and consolehttps://bugs.dragonflybsd.org/issues/19352010-12-13T18:06:55Zshamaz
<p>When I work with console with active X session and then go back into X, mouse<br />cursor doesn't move. Leds on keyboard are not working too. I use PS/2 mouse if<br />it matters.</p>
<p>To reproduse the bug do the following:</p>
<p>1. Start X session.<br />2. Switch back to termianl (by pressing Ctrl-Alf-F<something>)<br />3. Do somthing<br />4. Switch back to X and wait short time.<br />5. Repeat if needed</p>
<p>Also X.org prints "/dev/psm0: Device is busy" message</p>
<p>Bug appeared after this commit:</p>
<p><a class="external" href="http://gitweb.dragonflybsd.org/dragonfly.git/commit/91be4d718298a092b2279227bb6ce190622b3fc9">http://gitweb.dragonflybsd.org/dragonfly.git/commit/91be4d718298a092b2279227bb6ce190622b3fc9</a></p> DragonFlyBSD - Bug #1923 (New): Abysmal NFS performance with IPv6https://bugs.dragonflybsd.org/issues/19232010-11-25T21:16:16Zftigeot
<p>I have recently setup a NFS share with IPv6 addresses on a gigabit lan. The<br />performance is abysmal: 500 KB/s max.</p>
<p>Both server and client are running DragonFly-2.8.2/x86-64</p>
<p>The same machines on the same lan have no trouble reaching tens of<br />MB/s with IPv4. Disk speed becomes the limiting factor.</p>
<p>Time spent copying some big files from the server to a local disk:</p>
<p>v4: sent 86109382 bytes received 31 bytes 24602689.43 bytes/sec<br />v6: sent 49660678 bytes received 31 bytes 266277.26 bytes/sec</p>
<p>All mounts were using tcp.</p>
<p>IPv6 transfer speed is about 100 time slower than IPv4.</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 #1917 (New): panic: assertion: (RB_EMPTY(&ip->rec_tree) && (ip->flags & HAMMER...https://bugs.dragonflybsd.org/issues/19172010-11-21T19:23:17Zqhwt.dfly
<p>Hello.<br />Caught this while running pbulk on an Atom D510, running x86_64 kernel.<br />This one is new to me and I haven't seen this one before updating the<br />kernel. The current kernel was built from source whose commit hash is<br />c6aff4f7f0c74961380763de0bcb5dd49fb7faea, while the previous kernel was<br />from c4ce4f88f289f77826fecf470965d7e216274018. No hammer cleanup was<br />running when it panicked.</p>
<p>Unread portion of the kernel message buffer:<br /> 1548 1532 1516 1500 1484 1468SECONDARY PANIC ON CPU 3 THREAD 0xffffffe02c36cc70<br />SECONDARY PANIC ON CPU 1 THREAD 0xffffffe02c36c670<br />SECONDARY PANIC ON CPU 2 THREAD 0xffffffe0526d7a70<br /> 1452SECONDARY PANIC ON CPU 2 THREAD 0xffffffe052996870<br />SECONDARY PANIC ON CPU 2 THREAD 0xffffffe0526d6870<br />SECONDARY PANIC ON CPU 3 THREAD 0xffffffe052bac070<br />SECONDARY PANIC ON CPU 3 THREAD 0xffffffe0526dd470<br /> 1436SECONDARY PANIC ON CPU 3 THREAD 0xffffffe02c369070<br /> 1420 1404 1388 1372 1356 1340 1324 1308 1292 1276 1260 1244 1228 1212 1196 1180 1164 1148 1132 1116 1100 1084 1068 1052 1036 1020 1004 988 972 956 940 924 908 892 876 860 844 828 812 796 780 764 748 732 716 700 684 668 652 636 620 604 588 572 556 540 524 508 492 476 460 444 428 412 396 380 364 348 332 316 300 284 268 252 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12</p>
<p>Reading symbols from /boot/kernel/acpi.ko...done.<br />Loaded symbols for /boot/kernel/acpi.ko<br />Reading symbols from /boot/kernel/ahci.ko...done.<br />Loaded symbols for /boot/kernel/ahci.ko<br />Reading symbols from /boot/kernel/ehci.ko...done.<br />Loaded symbols for /boot/kernel/ehci.ko<br /><em>get_mycpu (di=0xffffffff80719020) at ./machine/thread.h:73<br />73 __asm ("movq %<span>gs:globaldata,%0" : "=r" (gd) : "m"(</em>_mycpu__dummy));<br />(kgdb) bt<br />#0 _get_mycpu (di=0xffffffff80719020) at ./machine/thread.h:73<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=0xffffffff80719020)<br /> at /usr/src/sys/platform/pc64/x86_64/dump_machdep.c:262<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> 0xffffffff802a5b6c in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:881<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> 0xffffffff802a62e9 in boot (howto=-2004318071)<br /> at /usr/src/sys/kern/kern_shutdown.c:388<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> 0xffffffff802a66a7 in panic (fmt=0xffffffff804d4f2a "assertion: %s in %s")<br /> at /usr/src/sys/kern/kern_shutdown.c:787<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> 0xffffffff804030f8 in hammer_flush_inode_done (ip=0xffffffe06fc17a78,<br /> error=<value optimized out>) at /usr/src/sys/vfs/hammer/hammer_inode.c:2421<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> 0xffffffff803ff587 in hammer_flusher_flush_inode (<br /> arg=<value optimized out>) at /usr/src/sys/vfs/hammer/hammer_flusher.c:525<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> hammer_flusher_slave_thread (arg=<value optimized out>)<br /> at /usr/src/sys/vfs/hammer/hammer_flusher.c:455<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> 0xffffffff802b1a2a in lwkt_deschedule_self (td=0x0)<br /> at /usr/src/sys/kern/lwkt_thread.c:258<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)<br />(kgdb) fr 5<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> 0xffffffff804030f8 in hammer_flush_inode_done (ip=0xffffffe06fc17a78,<br /> error=<value optimized out>) at /usr/src/sys/vfs/hammer/hammer_inode.c:2421<br />2421 <abbr title="(RB_EMPTY(&ip->rec_tree">KKASSERT</abbr> &x%x</span><br />(kgdb) p ip->rec_tree<br />$1 = {rbh_root = 0x0, rbh_inprog = 0x0}<br />(kgdb) p/x ip->flags<br />$2 = 0x1353813<br />(kgdb)</p>
<p>I'm preparing to upload the kern.18 and vmcore.18.</p> DragonFlyBSD - Bug #1916 (New): Constant crashes on x86_64 with UFShttps://bugs.dragonflybsd.org/issues/19162010-11-21T16:18:27Zlentferj
<p>On the VM that I provide for Justin to make bulk builds I am getting <br />constant panics after I enabled swapcache.</p>
<p><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> 0xffffffff8035d01f in panic (fmt=0xffffffff80685d46 "ffs_realloccg: <br />bad blockno") at /usr/src/sys/kern/kern_shutdown.c:785<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> 0xffffffff804fec9c in ffs_realloccg (ip=0xffffffe00096e698, <br />lbprev=<value optimized out>, bpref=8, osize=4096, nsize=5120,<br /> cred=0xffffffe000886900, bpp=0xffffffe02e4157f0) at <br />/usr/src/sys/vfs/ufs/ffs_alloc.c:230<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> 0xffffffff804ff338 in ffs_balloc (ap=0xffffffe02e415838) at <br />/usr/src/sys/vfs/ufs/ffs_balloc.c:183<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> 0xffffffff803cece0 in vop_balloc (ops=0xffffffe007fcea80, <br />vp=0xffffffe02e58b400, startoffset=<value optimized out>, size=<value <br />optimized out>,<br /> cred=<value optimized out>, flags=<value optimized out>, <br />bpp=0xffffffe02e415918) at /usr/src/sys/kern/vfs_vopops.c:936<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> 0xffffffff8050abba in ffs_write (ap=0xffffffe02e415958) at <br />/usr/src/sys/vfs/ufs/ufs_readwrite.c:348<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> 0xffffffff803cf738 in vop_write (ops=0xffffffe007fcea80, <br />vp=0xffffffe02e58b400, uio=<value optimized out>, ioflag=<value <br />optimized out>,<br /> cred=<value optimized out>) at /usr/src/sys/kern/vfs_vopops.c:427<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> 0xffffffff803cdb7b in vn_write (fp=0xffffffe00ab7d4a8, <br />uio=0xffffffe02e415ad8, cred=0xffffffe000886900, flags=<value optimized <br />out>)<br /> at /usr/src/sys/kern/vfs_vnops.c:724<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> 0xffffffff803871ef in dofilewrite (fd=6, auio=0xffffffe02e415ad8, <br />flags=0, res=0xffffffe02e415b48) at /usr/src/sys/sys/file2.h:72</p>
<p>Kernel is<br />DragonFly df64pkgbuilder.lan.net 2.9-DEVELOPMENT DragonFly <br />v2.9.0.116.ge61a8-DEVELOPMENT #0: Fri Nov 5 06:38:41 CET 2010 <br /><a class="email" href="mailto:root@df64pkgbuilder.lan.net">root@df64pkgbuilder.lan.net</a>:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64</p>
<p>Anyone seen this before?</p>
<p>Jan</p> DragonFlyBSD - Bug #1913 (New): panic: assertion: ip->flush_state != HAMMER_FST_FLUSH in hammer_f...https://bugs.dragonflybsd.org/issues/19132010-11-21T01:27:20Zswildner
<p>I hit this assertion while running a loop of</p>
<p>/tmp/fsstress -n 6400 -p 1</p>
<p>on a fresh HAMMER v4 file system which was mounted normally.</p>
<p>Before the box crashed, I got 3 messages of the type:</p>
<p>HAMMER Warning: depth limit reached on setup recursion, inode ... ...</p>
<p>This box is running latest 2.9 and the file system was also created <br />after updating.</p>
<p>The core is in ~swildner/crash/crash31.tbz on leaf.</p>
<p>Regards,<br />Sascha</p> DragonFlyBSD - Bug #1907 (New): Hammer crash in hammer_flusher_flush()https://bugs.dragonflybsd.org/issues/19072010-11-11T13:07:15Zswildner
<p>I've had another hammer crash on master while running fsstress. This <br />time it hit an assertion in hammer_flusher_flush(). The filesystem was <br />mounted -o nohistory.</p>
<p>Dump is in ~swildner/crash/crash29.tbz on leaf.</p>
<p>Panic message is:</p>
<p>Unread portion of the kernel message buffer:<br />panic: assertion: flg->refs == 0 in hammer_flusher_flush<br />mp_lock = 00000001; cpuid = 0<br />Trace beginning at frame 0xd91b5d2c<br />panic(ffffffff) at panic+0x174<br />panic(c05e1dd5,c060d920,c05cb4a2,d91a8124,d91a8154) at panic+0x174<br />hammer_flusher_master_thread(d91a8000,0,0,0,0) at <br />hammer_flusher_master_thread+0x345<br />lwkt_exit() at lwkt_exit<br />Debugger("panic")</p>
<p>Backtrace:</p>
<p>(kgdb) bt<br />#0 _get_mycpu (di=0xc07622e0) 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> md_dumpsys (di=0xc07622e0) at <br />/d1/src/sys/platform/pc32/i386/dump_machdep.c:263<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> 0xc030e041 in dumpsys () at /d1/src/sys/kern/kern_shutdown.c:881<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> 0xc017d441 in db_fncall (dummy1=2, dummy2=0, dummy3=-1068125532, <br />dummy4=0xd91b5bd8 "") at /d1/src/sys/ddb/db_command.c:542<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> 0xc017d932 in db_command () at /d1/src/sys/ddb/db_command.c:344<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> db_command_loop () at /d1/src/sys/ddb/db_command.c:470<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> 0xc017ffc4 in db_trap (type=3, code=0) at /d1/src/sys/ddb/db_trap.c:71<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> 0xc055b4a8 in kdb_trap (type=3, code=0, regs=0xd91b5cdc) at <br />/d1/src/sys/platform/pc32/i386/db_interface.c:152<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> 0xc05749b7 in trap (frame=0xd91b5cdc) at <br />/d1/src/sys/platform/pc32/i386/trap.c:831<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> 0xc055c827 in calltrap () at <br />/d1/src/sys/platform/pc32/i386/exception.s:785<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> 0xc055b2a4 in breakpoint (msg=0xc05fd655 "panic") at ./cpu/cpufunc.h:73<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> Debugger (msg=0xc05fd655 "panic") at <br />/d1/src/sys/platform/pc32/i386/db_interface.c:334<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> 0xc030e8d0 in panic (fmt=0xc05e1dd5 "assertion: %s in %s") at <br />/d1/src/sys/kern/kern_shutdown.c:785<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> 0xc04adeb8 in hammer_flusher_flush (arg=0xd91a8000) at <br />/d1/src/sys/vfs/hammer/hammer_flusher.c:398<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> hammer_flusher_master_thread (arg=0xd91a8000) at <br />/d1/src/sys/vfs/hammer/hammer_flusher.c:238<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> 0xc031839a in lwkt_deschedule_self (td=Cannot access memory at <br />address 0x8<br />) at /d1/src/sys/kern/lwkt_thread.c:258<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)</p> DragonFlyBSD - Bug #1882 (New): Idea for handling new USB vendor/device codeshttps://bugs.dragonflybsd.org/issues/18822010-10-20T17:22:04Zbmk
<p>This is just an idea / wish.</p>
<p>Have a config file called /etc/usb_hotwire.conf</p>
e.g.:
<ol>
<li>This file allows you to map a new unsupported usb vendor/device code</li>
<li>to an existing usb vendor/device code supported by a driver.</li>
<li>File Format:</li>
<li><unsupported vendor code>:<unsupported device code> <supported vendor<br />code>:<supported device code></li>
</ol>
<ol>
<li>The following makes my unsupported USB wireless adapter use the same driver<br />(rum) as a D-Link DWL-G122</li>
</ol>
<p>0x1044:0x2573 0x07d1:0x3c03</p> DragonFlyBSD - Bug #1861 (New): panic via kprintf (lockmgr called in a hard section)https://bugs.dragonflybsd.org/issues/18612010-10-05T08:05:32Zvsrinivasvsrinivas@ops101.org
<p>kbd_ioctl takes a lockmgr lock; kprintf calls kvcprintf, which enters a hard<br />section if it is calling kputchar (it is via kprintf). kbd_ioctl is called via<br />cnputc, from kputchar. This causes a panic.</p> DragonFlyBSD - Bug #1786 (New): Calling NULL function pointer initiates panic loophttps://bugs.dragonflybsd.org/issues/17862010-06-22T00:29:37Zsjg
<p>Further description in the commit message,</p>
<p><a class="external" href="http://gitweb.dragonflybsd.org/~sjg/dragonfly.git/log/refs/heads/null_fp">http://gitweb.dragonflybsd.org/~sjg/dragonfly.git/log/refs/heads/null_fp</a></p>
<p>Please review, I am not sure this is necessarily the best way to<br />address this, for instance, you don't actually see where the panic<br />occurred.</p>
<p>Sam</p> DragonFlyBSD - Bug #1538 (New): mountroot should probe file systemshttps://bugs.dragonflybsd.org/issues/15382009-09-28T01:48:34Zcorecode
<p>When mounting root from hammer, it is necessary to specify the file <br />system type in the vfs.root.mountfrom setting, otherwise the machine <br />will just be unhappy and issue the mountroot prompt (or rather, directly <br />go to ddb, see other bug report). This is very inconvenient and <br />irritating. The kernel should try all available file systems to mount root.</p>
<p>Possibly this should also be extended to mount itself, but this bug <br />report only deals with the mountroot issue.</p> DragonFlyBSD - Bug #1463 (New): Mountroot before drives are initializedhttps://bugs.dragonflybsd.org/issues/14632009-08-25T15:58:13Zelekktretterr
<p>Hi,</p>
<p>As per Sachas comment about splitting my previous bug report into separate<br />ones. here is an issue that has been bugging me on this box. (HP Proliant<br />DL180 G5)</p>
<p>It seems that mountroot is ran before da0 (and cd0) gets initialized on<br />this box. mountroot then complains that da0s1 is missing.</p>
<p>Here is a verbose dmesg:</p>
<p><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/bugs/2009-08/msg00128.html">http://leaf.dragonflybsd.org/mailarchive/bugs/2009-08/msg00128.html</a>.</p>
<p>Note that this problem seems to happen randomly when booting from live cd.<br />But happens all the time when booting from disk.</p>
<p>Petr</p> DragonFlyBSD - Bug #1430 (New): Buggy w(1)?https://bugs.dragonflybsd.org/issues/14302009-07-20T01:24:37Zhasso
<p>With single user logged in from X (kdm is in use):</p>
<p>$ w<br />w: /dev/:0: No such file or directory<br /> 9:21PM up 2 days, 3:21, 0 users, load averages: 0.00, 0.02, 0.00<br />USER TTY FROM LOGIN@ IDLE WHAT<br />$</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>