DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082012-05-16T21:29:52ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #2369 (New): panic: Bad link elm 0xffffffe07edf6068 next->prev != elmhttps://bugs.dragonflybsd.org/issues/23692012-05-16T21:29:52Zjaydg
<p>Another panic out of the blue, this time in the wireless stack.<br />Version String: DragonFly v3.1.0.704.gee39c-DEVELOPMENT</p>
<p>panic: Bad link elm 0xffffffe07edf6068 next->prev != elm<br />cpuid = 1<br />Trace beginning at frame 0xffffffe07eca3ac0<br />panic() at panic+0x1fb 0xffffffff802fa6e8<br />panic() at panic+0x1fb 0xffffffff802fa6e8<br />_ieee80211_free_node() at _ieee80211_free_node+0x76 0xffffffff803c598f<br />ieee80211_free_node() at ieee80211_free_node+0x3c 0xffffffff803c5d9a<br />rt2661_reset_tx_ring() at rt2661_reset_tx_ring+0x87 0xffffffff802b13a4<br />rt2661_stop_locked() at rt2661_stop_locked+0x232 0xffffffff802b2261<br />rt2661_ioctl() at rt2661_ioctl+0x7f 0xffffffff802b46a4<br />parent_updown_task() at parent_updown_task+0x3f 0xffffffff803cf007<br />taskqueue_run() at taskqueue_run+0xc2 0xffffffff8032a16f<br />taskqueue_thread_loop() at taskqueue_thread_loop+0x5e 0xffffffff8032a4e5<br />boot() called on cpu#1</p>
<p>The dump is available on leaf.</p> DragonFlyBSD - Bug #2362 (Closed): pw(8): Add an option to accept encrypted passwordshttps://bugs.dragonflybsd.org/issues/23622012-05-06T14:27:49Zjaydg
<p>Add a `-H <fd>' option that is like `-h <fd>', but accepts an already<br />encrypted password on the specified file descriptor.</p>
<p>Taken-from: FreeBSD SVN 124382</p>
<p>This patch will allow to use puppet's FreeBSD user provider on DragonFlyBSD.</p> DragonFlyBSD - Bug #2355 (Closed): panic: rtrequest1_msghandler: rtrequest table error was cpu4, ...https://bugs.dragonflybsd.org/issues/23552012-04-27T21:38:26Zjaydg
<p>I experimented with wlan and dhcp and had some trouble to get it to work.<br />To start from scratch, I've deleted the generated interface wlan0 after running /etc/rc.d/netif stop.<br />At some point after running /etc/rc.d/netif start again this panic occurs. This is reproducible.</p>
<p>Version String: DragonFly v3.1.0.347.g228a6-DEVELOPMENT <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>: Mon Mar 19 08:37:17 CET 2012</p>
<p>#0 _get_mycpu () at ./machine/thread.h:69<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=<optimized out>) at /usr/src/sys/platform/pc64/x86_64/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> 0xffffffff802f9b62 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:937<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> 0xffffffff802fa1c6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:387<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> 0xffffffff802fa47d in panic (fmt=0xffffffff805b26a8 "rtrequest1_msghandler: rtrequest table error was cpu%d, err %d\n") at /usr/src/sys/kern/kern_shutdown.c:843<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> 0xffffffff8039d657 in rtrequest1_msghandler (msg=<optimized out>) at /usr/src/sys/net/route.c:815<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> 0xffffffff8039bc70 in rtable_service_loop (dummy=<optimized out>) at /usr/src/sys/net/route.c:205<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> 0xffffffff80305300 in lwkt_deschedule_self (td=<unavailable>) at /usr/src/sys/kern/lwkt_thread.c:362<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)</p>
<p>A dump is available.</p> DragonFlyBSD - Bug #2353 (In Progress): panic: assertion "gd->gd_spinlocks_wr == 0" failed in bsd...https://bugs.dragonflybsd.org/issues/23532012-04-27T21:21:56Zjaydg
<p>Version String: DragonFly v3.1.0.322.gc231b-DEVELOPMENT #0: Fri Mar 16 20:31:33 CET 2012</p>
<p>#0 _get_mycpu () at ./machine/thread.h:69<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=<optimized out>) at /usr/src/sys/platform/pc64/x86_64/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> 0xffffffff802fb2d2 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:937<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> 0xffffffff802fb936 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:387<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> 0xffffffff802fbbed in panic (fmt=0xffffffff80585cf0 "assertion \"%s\" failed in %s at %s:%u") at /usr/src/sys/kern/kern_shutdown.c:843<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> 0xffffffff803036fb in bsd4_schedulerclock (lp=<optimized out>, period=<optimized out>, cpstamp=<optimized out>) at /usr/src/sys/kern/usched_bsd4.c:622<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> 0xffffffff802db16c in schedclock (info=0xffffffff820106e8, in_ipi=<optimized out>, frame=<optimized out>) at /usr/src/sys/kern/kern_clock.c:776<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> 0xffffffff802f9e03 in systimer_intr (timep=<optimized out>, in_ipi=<optimized out>, frame=0x0) at /usr/src/sys/kern/kern_systimer.c:102<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> 0xffffffff8054ad04 in lapic_timer_process_oncpu (gd=0xffffffff8200f000, frame=0x0) at /usr/src/sys/platform/pc64/apic/lapic.c:336<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> 0xffffffff8054ad3c in lapic_timer_process () at /usr/src/sys/platform/pc64/apic/lapic.c:342<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> 0xffffffff80540d69 in splz_timer () at /usr/src/sys/platform/pc64/x86_64/ipl.s:461<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> 0x0000000000000000 in ?? ()</p>
<p>Before dumping, several text blocks like this one were emitted:</p>
<p>Fatal trap 12: page fault while in kernel mode<br />cpuid = 0; lapic->id = 00000000<br />fault virtual address = 0x20<br />fault code = supervisor write data, page not present<br />instruction pointer = 0x8:0xffffffff802ec7fc<br />stack pointer = 0x10:0xffffffe0a8b4a980<br />frame pointer = 0x10:0xffffffe0a8b4a9c8<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 = 8139<br />current thread = pri 6 (CRIT)<br />kernel: type 12 trap, code=2</p>
<p>A dump is available.</p> DragonFlyBSD - Bug #2352 (Closed): panic: Bad link elm 0xffffffe0a3775670 next->prev != elmhttps://bugs.dragonflybsd.org/issues/23522012-04-27T21:08:47Zjaydg
<p>Though there already are some bugs open with a similar message, this one seems to be different:</p>
<p>Unread portion of the kernel message buffer:<br />panic: Bad link elm 0xffffffe0a3775670 next->prev != elm<br />cpuid = 1<br />Trace beginning at frame 0xffffffe0b7349948<br />panic() at panic+0x1fb 0xffffffff802fa588 <br />panic() at panic+0x1fb 0xffffffff802fa588 <br />proc_remove_zombie() at proc_remove_zombie+0x57 0xffffffff802f1f0e <br />kern_wait() at kern_wait+0x28e 0xffffffff802e5d25 <br />sys_wait4() at sys_wait4+0x44 0xffffffff802e5ff4 <br />syscall2() at syscall2+0x370 0xffffffff80547f61</p>
<p>This happens on DragonFly v3.1.0.586.g6c7e9-DEVELOPMENT x86_64.</p>
<p>A dump is available.</p> DragonFlyBSD - Bug #2308 (New): System freeze when unloading snd_hdahttps://bugs.dragonflybsd.org/issues/23082012-02-18T07:36:58Zjaydg
<p>When unloading snd_hda, the system (v3.1.0.197.gcc1635-DEVELOPMENT) freezes completely.<br />There is no panic; the screen just gets garbled and the system no longer responds to any interaction, may it be local or via network.</p>
<p>This shows up when loading the module:</p>
<p>pcm0: <NVidia MCP51 High Definition Audio Controller> mem 0xf2300000-0xf2303fff irq 21 at device 16.1 on pci0<br />pcm0: <HDA Codec: Realtek ALC260><br />pcm0: <HDA Driver Revision: 20071129_0050></p> DragonFlyBSD - Bug #2066 (Closed): tmpsf corruptionhttps://bugs.dragonflybsd.org/issues/20662011-05-07T21:58:03Zjaydg
<p>I've noticed that files stored on tmpfs gets corrupted when running the<br />hammer.sh installation script on a swapless machine.</p>
<p>Steps to reproduce:<br />1. Set up a virtual machine (tested on KVM and VirtualBox), 512 MB RAM<br />2. Boot from the installation CD (tested with 2.8.2 and 2.10.1)<br />3. Log in as root<br />4. # cp /usr/share/example/rconfig/hammer.sh .<br />5. Set the correct disk name in hammer.sh on line 18 <br />6. # csh hammer.sh</p>
<p>=> the script stops at line 154. Viewing the file reveals that it contains garbage.</p>
<p>During the execution of the script the following messages are logged on the<br />console when / is being copied to /mnt (see attached screenshot):</p>
<p>swap_pager_getswapspace: failed<br />tmpfs_write bwrite error 12<br />tmpfs_write bwrite error 12</p>
<p>Funny enough, the same issue occurs when enabling the newly-created swap device<br />after line 66 in hammer.sh. The swap space gets used and the messages are not<br />emitted, but nevertheless the script terminated too early and contains only garbage.</p>