DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082019-11-27T18:12:16ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3217 (New): rescue tools: make install fails if rescue folder doesn't existhttps://bugs.dragonflybsd.org/issues/32172019-11-27T18:12:16ZAnonymous
<p>boojum# ls -l /rescue<br />ls: /rescue: No such file or directory</p>
<p>boojum# make install<br />--------------------------------------------------------------</p>
<blockquote><blockquote><blockquote>
<p>installing rescue tools to /rescue ...</p>
</blockquote></blockquote></blockquote>
--------------------------------------------------------------<br />(cd /usr/src/initrd/oinit; LC_ALL=C make -m /usr/src/initrd/../share/mk BINDIR=/rescue install)<br />install -s -o root -g wheel -m 555 oinit /rescue<br />(cd /usr/src/initrd/rescue; LC_ALL=C make -m /usr/src/initrd/../share/mk BINDIR=/rescue install)<br />install -s -o root -g wheel -m 555 rescue /rescue<br />install -o root -g wheel -m 555 /usr/src/initrd/rescue/dowpa /rescue/dowpa<br />install: /rescue/dowpa: Not a directory
<ul>
<li>Error code 71</li>
</ul>
Stop.<br />make<sup><a href="#fn1">1</a></sup>: stopped in /usr/src/initrd/rescue
<ul>
<li>Error code 1</li>
</ul>
<p>Stop.<br />make: stopped in /usr/src/initrd</p> DragonFlyBSD - Bug #3194 (New): Hammer kernel crash on mirror-stream of PFS after upgrade (assert...https://bugs.dragonflybsd.org/issues/31942019-06-29T19:53:41ZAnonymous
<p>I operate two HAMMER arrays, each with PFSs that are mirrored via ``hammer mirror-stream`` from an array master to an array slave.</p>
<p>I recently upgraded to DragonFly 5.6.</p>
<p>After 18 hours of activity, I encountered a kernel fault that reliably can be provoked by running ``hammer mirror-stream`` on one PFS.</p>
<p>I've disabled PFS mirroring until this can be corrected.</p>
<p>Here is the transcribed error from the kernel fault:</p>
<p>```<br />panic: assertion "cursor->flags & HAMMER_CURSOR_ITERATE_CHECK" failed in hammer_btree_iterate at /usr/src/sys/vfs/hammer/hammer_btree.c:263<br />cpuid = 2<br />Trace beginning at frame 0xfffff801e6875158<br />hammer_btree_iterate() at hammer_btree_iterate+0x839 0xffffffff80900db9<br />hammer_btree_iterate() at hammer_btree_iterate+0x839 0xffffffff80900db9<br />hammer_mirror_delete_to.irsra.2() at hammer_mirror_delete_to.isra.2+0x12 0xffffffff80914d92<br />hammer_ioc_mirror_write() at hammer_ioc_mirror_write+0x3b7 0xffffffff809159a7<br />hammer_ioctl() at hammer_ioctl+0xebe 0xffffffff809143de<br />hammer_vop_ioctl() at hammer_vop_ioctl+0x48 0xffffffff8092d458<br />Debugger("panic")</p>
<p>CPU2 stopping CPUs: 0x0000000b<br /> stopped<br />Stopped at Debugger+0x7c: movb $0,0xfc9be9(%rip)<br />db> <br />```</p>
<p>Unfortunately, nothing was saved to /var/crash for this fault except an empty ``kern.0`` file.</p> DragonFlyBSD - Submit #3041 (New): firmware: Remove embedding of multiple images in one module.https://bugs.dragonflybsd.org/issues/30412017-05-25T12:23:23ZAnonymous
<p>Hello,</p>
<p>this patch removes possibility of embedding more than one firmware image in one kernel module through the parent reference in the firmware_register() function.</p>
<p>This patch is a preparation for firmware subsystem modification for moving firmware images from kernel modules to userland.</p>
<p>The mechanism is not used and it can be functionally fully replaced by putting each firmware image in its own module.</p>
<p>Removing the functionality significantly simplifies handling of firmware images. If firmware images are moved to userland the logical grouping of modules could be expressed by putting the related firmware images into one directory if needed.</p>
<p>jan</p> DragonFlyBSD - Bug #3006 (New): boot0cfg: panic in kern_udev.c in function _udev_dict_set_cstr wh...https://bugs.dragonflybsd.org/issues/30062017-04-01T21:22:17ZMichiGreat
<p>When installing DragonFlyBSD 4.8 in VirtualBox 5.1.16 (host is running Ubuntu MATE 16.04, Linux 4.4.0-66-generic) on a virtual 30 GB IDE harddisk, boot0cfg crashes:</p>
<p>,-<<< Executing `/sbin/disklabel64 <del>B ad0s1'<br />`</del>>>> Exit status 0:</p>
<p>swap_pager: out of swap space<br />,-<<< Executing `/usr/sbin/boot0cfg -B -o packet ad0'</p>
<p>panic: assertion "dict != NULL" failed in _udev_dict_set_cstr at /home/justin/release/4_8/sys/kern/kern_udev.c:139<br />cpuid = 2<br />Trace beginning at frame 0xffffff8060723730<br />panic() at panic+0x236 0xffffffff805e5d76<br />panic() at panic+0x236 0xffffffff805e5d76<br />_udev_dict_set_cstr() at _udev_dict_set_cstr+0x99 0xffffffff805eb219<br />disk_probe_slice() at disk_probe_slice+0x554 0xffffffff80612a84<br />disk_probe() at disk_probe+0x2d3 0xffffffff80613593<br />disk_msg_core() at disk_msg_core+0x2fa 0xffffffff80613a0a<br />Debugger("panic")</p>
<p>CPU2 stopping CPUs: 0x0000000b<br /> stopped<br />Stopped at Debugger+0x7c: movb $0,0xd9cb79(%rip)</p>
<p>However, when the VM is being booted from the virtual hard disk, the system is usable.</p> DragonFlyBSD - Bug #2915 (New): Hammer mirror-copy problemhttps://bugs.dragonflybsd.org/issues/29152016-05-17T00:23:36ZAnonymous
<p>DragonFly v4.5.0.843.gfe3b7-DEVELOPMENT</p>
<p>When I mirror copy a master to a slave and then upgrade the slave, the new master pfs can't be mirror copied. This is reproducible but only between two distinct hammer filesystems. If you do it all on the same filesystem, the problem doesn't appear to occur.</p>
<p>boojum# hammer pfs-master /pfs/master<br />Creating PFS <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> succeeded!<br />/pfs/master<br /> sync-beg-tid=0x0000000000000001<br /> sync-end-tid=0x00000001b44c0b20<br /> shared-uuid=1191b9a4-1bc4-11e6-8e1d-418d5cb760e2<br /> unique-uuid=1191b9aa-1bc4-11e6-8e1d-418d5cb760e2<br /> label="" <br /> prune-min=00:00:00<br /> operating as a MASTER<br /> snapshots directory defaults to /var/hammer/<pfs><br />boojum# cp /COPYRIGHT /pfs/master/ <br />boojum# ls <del>l /pfs/master/<br />total 13<br />-r--r--r-</del> 1 root wheel 6686 16-May-2016 17:12 COPYRIGHT<br />boojum# hammer <del>y mirror-copy /pfs/master /volumes/BACKUP3/pfs/slave <br />PFS slave /volumes/BACKUP3/pfs/slave does not exist. Auto create new slave PFS!<br />Creating PFS <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: panic (Closed)" href="https://bugs.dragonflybsd.org/issues/31">#31</a> succeeded!<br />/volumes/BACKUP3/pfs/slave<br /> sync-beg-tid=0x0000000000000001<br /> sync-end-tid=0x0000000000000001<br /> shared-uuid=1191b9a4-1bc4-11e6-8e1d-418d5cb760e2<br /> unique-uuid=2e551d04-1bc4-11e6-8e1d-418d5cb760e2<br /> label="" <br /> prune-min=00:00:00<br /> operating as a SLAVE<br /> snapshots directory defaults to /var/hammer/<pfs><br />Prescan to break up bulk transfer<br />Prescan 1 chunks, total 0 MBytes (7296)<br />Mirror-read /pfs/master succeeded<br />boojum# ls -l /volumes/BACKUP3/pfs/slave/<br />total 13<br />-r--r--r-</del> 1 root wheel 6686 16-May-2016 17:12 COPYRIGHT<br />boojum# hammer pfs-upgrade /volumes/BACKUP3/pfs/slave <br />pfs-upgrade of PFS#31 () succeeded<br />boojum# hammer -y mirror-copy /volumes/BACKUP3/pfs/slave /volumes/BACKUP3/pfs/slave2<br />PFS slave /volumes/BACKUP3/pfs/slave2 does not exist. Auto create new slave PFS!<br />Creating PFS <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Better news about that wi panic (Closed)" href="https://bugs.dragonflybsd.org/issues/32">#32</a> succeeded!<br />/volumes/BACKUP3/pfs/slave2<br /> sync-beg-tid=0x0000000000000001<br /> sync-end-tid=0x0000000000000001<br /> shared-uuid=1191b9a4-1bc4-11e6-8e1d-418d5cb760e2<br /> unique-uuid=5ef43f68-1bc4-11e6-8e1d-418d5cb760e2<br /> label="" <br /> prune-min=00:00:00<br /> operating as a SLAVE<br /> snapshots directory defaults to /var/hammer/<pfs><br />Prescan to break up bulk transfer<br />Prescan 1 chunks, total 0 MBytes (0)<br />Mirror-read /volumes/BACKUP3/pfs/slave succeeded<br />boojum# ls -l /volumes/BACKUP3/pfs/slave2 <br />lrwxr-xr-x 1 root wheel 10 16-May-2016 17:14 /volumes/BACKUP3/pfs/slave2 -> @@0x00000001000420d0:00032<br />boojum# ls -l /volumes/BACKUP3/pfs/slave2/<br />ls: /volumes/BACKUP3/pfs/slave2/: No such file or directory<br />boojum#</p> DragonFlyBSD - Bug #2806 (New): failed to configure a link-local address on ath0 (errno = 22)https://bugs.dragonflybsd.org/issues/28062015-03-16T07:28:08ZChingyuanphil.cyc@gmail.com
<p>Hello,</p>
<p>My Laptop's wireless device is "Qualcomm Atheros AR9485 rev 01".</p>
<p>Athought DFB can detect it, it can not be initialized.</p>
<p>The error message as follows :</p>
<p>#ifconfig ath0 up</p>
<p>ath0: _ath_power_restore_power_state : refcnt=0?<br />kernel : in6_ifattach_linklocal : failed to configure a link-local address on ath0 (errno = 22)</p> DragonFlyBSD - Bug #2620 (New): moused problemhttps://bugs.dragonflybsd.org/issues/26202013-12-20T18:32:02ZFilippoMofilippomore@yahoo.com
<p>I set up rc.conf according to your instruction.It did not fix the problem but I got a new message in dmesg<br />moused error opening /dev/ums0 Device Busy<br />Filippo</p> DragonFlyBSD - Bug #2618 (New): mouse problem on RELEASE-3_6_0https://bugs.dragonflybsd.org/issues/26182013-12-20T11:26:32ZFilippoMofilippomore@yahoo.com
<p>By default the system runs moused on port /dev/ums0<br />ps waux | grep moused<br />moused -p /dev/ums0<br />I will try to set it in rc.conf anyway.<br />Filippo</p> DragonFlyBSD - Bug #2453 (New): panic: assertion "gd->gd_spinlocks == 0" failedhttps://bugs.dragonflybsd.org/issues/24532012-11-12T20:54:50ZJohannes.Hofmann
<p>On an i386 SMP system (b373db6a1) I got this panic:</p>
<p>#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=0xc0755700)<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> 0xc01accde in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:913<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> 0xc01ad2f4 in boot (howto=<optimized out>)<br /> at /usr/src/sys/kern/kern_shutdown.c:373<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> 0xc01ad564 in panic (<br /> fmt=0xc03b923c "assertion \"%s\" failed in %s at %s:%u")<br /> at /usr/src/sys/kern/kern_shutdown.c:819<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> 0xc01b8374 in dfly_schedulerclock (lp=<unavailable>, period=286364, <br /> cpstamp=2464609796) at /usr/src/sys/kern/usched_dfly.c:720<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> 0xc01b427b in usched_schedulerclock (lp=0xd59ec500, periodic=286364, <br /> time=2464609796) at /usr/src/sys/kern/kern_usched.c:158<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> 0xc018c0c7 in schedclock (info=0xff80ad18, in_ipi=1, frame=0x0)<br /> at /usr/src/sys/kern/kern_clock.c:778<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> 0xc01ab882 in systimer_intr (timep=0xc0888db8, in_ipi=1, frame=0x0)<br /> at /usr/src/sys/kern/kern_systimer.c:100<br />---Type <return> to continue, or q <return> to quit---<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> 0xc01bdc1c in lwkt_process_ipiq_core (sgd=<optimized out>, <br /> ip=0xc461a40c, frame=<optimized out>)<br /> at /usr/src/sys/kern/lwkt_ipiq.c:668<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> 0xc01bddec in lwkt_process_ipiq ()<br /> at /usr/src/sys/kern/lwkt_ipiq.c:494<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> 0xc01bdf33 in lwkt_wait_ipiq (target=0xff800000, seq=869270)<br /> at /usr/src/sys/kern/lwkt_ipiq.c:427<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> 0xc01ca1fe in callout_stop (c=0xc0888dd0)<br /> at /usr/src/sys/kern/kern_timeout.c:488<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> 0xc01ca46f in callout_reset (c=0xc0888dd0, to_ticks=10, <br /> ftn=0xc03a42c7 <sysbeepstop>, arg=0x0)<br /> at /usr/src/sys/kern/kern_timeout.c:361<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> 0xc03a4b1a in sysbeep (pitch=2982, period=10)<br /> at /usr/src/sys/platform/pc32/isa/clock.c:483<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> 0xc0360a40 in sc_bell (scp=<unavailable>, pitch=<unavailable>, <br /> duration=10) at /usr/src/sys/dev/misc/syscons/syscons.c:3792<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> 0xc03626bb in scioctl (ap=0xd96f6b54)<br />---Type <return> to continue, or q <return> to quit---<br /> at /usr/src/sys/dev/misc/syscons/syscons.c:1228<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> 0xc018dfc2 in dev_dioctl (dev=0xd5b12420, cmd=536890120, <br /> data=0xd96f6c08 <error reading variable>, fflag=7, cred=0xd688ae60, <br /> msg=0xd96f6cf0) at /usr/src/sys/kern/kern_device.c:243<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> 0xc02b9a90 in devfs_fo_ioctl (fp=0xd90177c8, com=536890120, <br /> data=0xd96f6c08 <error reading variable>, ucred=0xd688ae60, <br /> msg=0xd96f6cf0) at /usr/src/sys/vfs/devfs/devfs_vnops.c:1446<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> 0xc01de9f8 in fo_ioctl (fp=0xd90177c8, com=536890120, <br /> data=0xd96f6c08 <error reading variable>, cred=0xd688ae60, <br /> msg=0xd96f6cf0) at /usr/src/sys/sys/file2.h:88<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> 0xc01deed3 in mapped_ioctl (fd=5, com=536890120, <br /> uspc_data=0x640ba6 <Address 0x640ba6 out of bounds>, map=0x0, <br /> msg=0xd96f6cf0) at /usr/src/sys/kern/sys_generic.c:733<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> 0xc01def82 in sys_ioctl (uap=0xd96f6cf0)<br /> at /usr/src/sys/kern/sys_generic.c:552<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> 0xc039d99c in syscall2 (frame=0xd96f6d40)<br /> at /usr/src/sys/platform/pc32/i386/trap.c:1321<br />---Type <return> to continue, or q <return> to quit---<br />#23 0xc036c4f6 in Xint0x80_syscall ()<br /> at /usr/src/sys/platform/pc32/i386/exception.s:878<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: waitpid() with WUNTRACED flag? (was Re: Hang on ctrl+Z after the MPSAFE tsleep/wakeup commit) (Closed)" href="https://bugs.dragonflybsd.org/issues/24">#24</a> 0x0000001f in ?? ()</p> DragonFlyBSD - Bug #2297 (New): strange NFS (client) error messages / problemshttps://bugs.dragonflybsd.org/issues/22972012-02-02T14:28:09ZAnonymous
<p>Hi,</p>
<p>I have DragonFly mounting my home dir via NFS (server is running Fedora 16) and noticed the following warnings on the console:</p>
<p>dfly.my.lan kernel log messages:</p>
<blockquote>
<p>nfs send error 32 for server f16srv:/home/cosmicdj<br />receive error 54 from nfs server f16srv:/home/cosmicdj<br />nfs send error 32 for server f16srv:/home/cosmicdj<br />receive error 54 from nfs server f16srv:/home/cosmicdj</p>
</blockquote>
<p>+ tons more, always error 32 or 54</p>
<p>Today, I got this:</p>
<p>cosmicdj@dfly:/home/cosmicdj> ls<br />^T<br />load: 0.00 cmd: ls 3244 [getblk] 0.00u 0.00s 0% 2496k<br />^C<br />^T<br />load: 0.00 cmd: ls 3244 [getblk] 0.00u 0.00s 0% 2496k<br />^C<br />^Z<br />^T<br />load: 0.00 cmd: ls 3244 [getblk] 0.00u 0.00s 0% 2496k</p>
<p>Connection to dflyclosed. (<- killed my shell)</p>
<p>I tried to kill 'ls', even via -9. Didn't help. So I ended up killing the shell and tried to umount/remount my NFS homedir via console:</p>
<p>root@dfly # umount /home/cosmicdj<br />^T<br />load: 0.00 cmd: umount 3295 [clock] 0.00u 0.00s 0% 1444k<br />[diagnostic] cache_lock: blocked on 0xffffffe07d31e7f8 ".history_beastie" <br />^C<br />^Z<br />^T<br />load: 0.00 cmd: umount 3295 [clock] 0.00u 0.09s 0% 1444k<br />[diagnostic] cache_lock: blocked on 0xffffffe07d319158 "" <br />[diagnostic] cache_lock: blocked on 0xffffffe07d319158 "" <br />[diagnostic] cache_lock: blocked on 0xffffffe07d319158 ""</p>
<p>I get "[diagnostic] cache_lock: blocked on 0xffffffe07d319158 """ errors when I try to login via ssh again (I guess sshd tries to read my key...)</p>
<p>So it was working fine, but after, say 1 day uptime it doesn't work anymore :(</p> DragonFlyBSD - Bug #2292 (New): re interface with jumbo frames (mtu larger than 1500) hangs after...https://bugs.dragonflybsd.org/issues/22922012-01-27T09:04:09ZAnonymous
<p>How to reproduce:<br />ifconfig re0 mtu 4088<br />cd /usr; make pkgsrc-create<br />wait a bit<br />re0 completely hangs; no ping; nothing when tcpdumping; nothing dmesg either</p>
<p>doing a<br />ifconfig re0 mtu 1500<br />gets it back to life though...</p>
<p>uname:<br />DragonFly v3.1.0.47.ge2743-DEVELOPMENT #0: Tue Jan 24 09:47:50 UTC 2012<br /> <a class="email" href="mailto:root@pkgbox64.dragonflybsd.org">root@pkgbox64.dragonflybsd.org</a>:/usr/obj/usr/src/sys/X86_64_GENERIC</p>
<p>dmesg:<br />re0: <RealTek 8111/8168 PCIe Gigabit Ethernet> port 0xe800-0xe8ff mem 0xfbffc000-0xfbffffff,0xfbffb000-0xfbffbfff irq 36 at device 0.0 on pci5<br />re0: Hardware rev. 0x2c000000; MAC ver. 0x2e; PCI-E 125MHz<br />miibus0: <MII bus> on re0<br />rgephy0: <8211B/RTL8169S/8110S media interface> on miibus0<br />rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto</p> DragonFlyBSD - Bug #2052 (New): Kernel panic: CPU APIC ID out of rangehttps://bugs.dragonflybsd.org/issues/20522011-04-21T19:38:13ZAnonymous
<p>Hello,</p>
<p>booting DragonFly BSD from a CD ends with a kernel panic. A screenshot of the console is attached. The machine is a Dell PowerEdge M610 blade. The same problem occurs on both of our M610s, one with older 45nm Xeons and one with newer 32nm Xeons. I'd like to run some performance benchmarks of the Hammer file system on the machines, so a fully working SMP system with ACPI support is probably needed. If you need more debugging information, please let me know how to get it. A piece of advice on how to circumvent this issue would be very helpful. :-)</p>
<p>Andrej</p> DragonFlyBSD - Bug #1850 (New): volume-add on hammer root fs panichttps://bugs.dragonflybsd.org/issues/18502010-09-24T03:56:43ZJohannes.Hofmann
<p>Hi,</p>
<p>expanding a hammer root filesystem with hammer volume-add (which is<br />pretty cool btw) leads to a panic on shutdown:</p>
<p>panic: assertion: (bp->b_flags & B_LOCKED) 0 && iou->io.running <br />0 in hammer_io_deallocate</p>
<p>After a reboot everything is ok.<br />The problem can be reproduced in a vkernel.</p>
<pre><code>Johannes</code></pre>
<p>PS: One minor issue: The values df reports seem a bit off after<br /> the volume-add. They also are fine after a reboot.</p>
<p>Program received signal SIGTRAP, Trace/breakpoint trap.<br />Debugger (msg=0x8294114 "panic") at /usr/src/sys/platform/vkernel/i386/db_interface.c:334<br />334 in_Debugger = 0;<br />(gdb) bt<br />#0 Debugger (msg=0x8294114 "panic") at /usr/src/sys/platform/vkernel/i386/db_interface.c:334<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> 0x080e3bfd in panic (fmt=0x827b38c "assertion: %s in %s") at /usr/src/sys/kern/kern_shutdown.c:743<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> 0x08224a05 in hammer_io_deallocate (bp=0x5071f260) at /usr/src/sys/vfs/hammer/hammer_io.c:1093<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> 0x0812b79d in buf_deallocate (bp=0x5071f260) at /usr/src/sys/sys/buf2.h:239<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> brelse (bp=0x5071f260) at /usr/src/sys/kern/vfs_bio.c:1273<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> 0x0813f901 in vinvalbuf_bp (bp=0x5071f260, data=0x544659dc) at /usr/src/sys/kern/vfs_subr.c:424<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> 0x0813c8ae in buf_rb_tree_RB_SCAN (head=0x567de51c, scancmp=0x813c7bc <buf_rb_tree_SCANCMP_ALL>, <br /> callback=0x813f7e9 <vinvalbuf_bp>, data=0x544659dc) at /usr/src/sys/kern/vfs_subr.c:141<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> 0x0813f2b3 in vinvalbuf (vp=0x567de4c8, flags=1, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:334<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> 0x0813f434 in vclean_vxlocked (vp=0x567de4c8, flags=8) at /usr/src/sys/kern/vfs_subr.c:1142<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> 0x0813f622 in vgone_vxlocked (vp=0x567de4c8) at /usr/src/sys/kern/vfs_subr.c:1349<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> 0x0814212b in vflush_scan (mp=0x545c3fc0, vp=0x567de4c8, data=0x54465b4c) at /usr/src/sys/kern/vfs_mount.c:1252<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> 0x081422aa in vmntvnodescan (mp=0x545c3fc0, flags=2, fastfunc=0, slowfunc=0x81420ac <vflush_scan>, data=0x54465b4c)<br /> at /usr/src/sys/kern/vfs_mount.c:1068<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> 0x081424cd in vflush (mp=0x545c3fc0, rootrefs=0, flags=2) at /usr/src/sys/kern/vfs_mount.c:1184<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> 0x08213aa3 in devfs_unmount (mp=0x545c3fc0, mntflags=524288) at /usr/src/sys/vfs/devfs/devfs_vfsops.c:142<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> 0x08150d79 in vfs_unmount (mp=0x545c3fc0, mntflags=524288) at /usr/src/sys/kern/vfs_vfsops.c:123<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> 0x08145e40 in dounmount (mp=0x545c3fc0, flags=524288) at /usr/src/sys/kern/vfs_syscalls.c:755<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> 0x0813e3ae in vfs_umountall_callback (mp=0x545c3fc0, data=0x0) at /usr/src/sys/kern/vfs_subr.c:1714<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> 0x081427fb in mountlist_scan (callback=0x813e39b <vfs_umountall_callback>, data=0x0, how=<value optimized out>)<br /> at /usr/src/sys/kern/vfs_mount.c:900<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> 0x0813d9d3 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:1703<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> 0x080e3503 in boot (howto=8) at /usr/src/sys/kern/kern_shutdown.c:376<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> 0x080e3801 in sys_reboot (uap=0x54465c94) at /usr/src/sys/kern/kern_shutdown.c:204<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> 0x08271b77 in syscall2 (frame=0x54465d40) at /usr/src/sys/platform/vkernel/i386/trap.c:1221<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> 0x08271f42 in user_trap (frame=0x54465d40) at /usr/src/sys/platform/vkernel/i386/trap.c:410<br />#23 0x0827263e in go_user (frame=0x54465d38) at /usr/src/sys/platform/vkernel/i386/trap.c:1427<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: waitpid() with WUNTRACED flag? (was Re: Hang on ctrl+Z after the MPSAFE tsleep/wakeup commit) (Closed)" href="https://bugs.dragonflybsd.org/issues/24">#24</a> 0x0827290e in pmsg4 () at /usr/src/sys/platform/vkernel/i386/fork_tramp.s:103</p> DragonFlyBSD - Bug #1695 (New): NFS-related system breakdownhttps://bugs.dragonflybsd.org/issues/16952010-03-14T06:22:19ZAnonymous
<p>Hi all.</p>
<p>I do a cp(1) from /mnt/nfs (which is a zfs fileystem NFS-exported by an<br />opensolaris installation) to my /home/beket directory (HAMMER fs).</p>
<p>After a few MBs having being copied, cp(1) process stalls in 'getblk' state.<br />Also it is unkillable by ^C. From that point there's downhill.</p>
<p>Many commands will block if I issue them, such as 'mount' or 'df'. I can still<br />view top(1) update its contents but the system is on the edge. dmesg shows<br />sparse messages 'nfs server 10.0.0.1:/export/nfs: not responding' or<br />'[diagnostic]: $address block on cache_something ""'. If I break into the<br />debugger, I get nothing unusual. scgetc < sckbdevent < kbd_xxxx < taskqueue_yyyy<br />etc.</p>
<p>I tried to kill X and the system hang to the point that a cold reset was<br />necessary. I once managed to resume after typing 'c' in db> prompt, but that<br />doesn't always succeed.</p>
<p>This situation is, I think, 100% reproducible. Also, I don't have problems<br />copying stuff from|to a linux NFS client.</p>
<p>Cheers</p> DragonFlyBSD - Bug #989 (New): installer/fdisk trouble with wrapped valueshttps://bugs.dragonflybsd.org/issues/9892008-04-14T00:50:05ZDiscodestroyer
<p>Hi there,</p>
<p>I installed DF 2 days ago (the 1.12.1 release). I've choosen a primary partition for the installation (/dev/hda2 in linux slang) and installed the bootlocker on ad0.</p>
<p>After the reboot my laptop hung immediately. I couldn't even see the BIOS password dialog anymore. Whenever I try to reach my bios setup via F2 it crashes on the way.</p>
<p>Without the harddisk it is possible to boot the notebook without any problems.</p>
<p>I bought an external HD case and tried to mount the HD with a live CD: no partition table...</p>
<p>I can't find any reports for that issue, so I thought I will let you know.</p>
<p>Do you need any further information about my hardware?</p>
<p>And is there a way to recover the table?</p>
<p>greets from Germany.</p>
<p>HennR<br />-- <br />GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!<br />Jetzt dabei sein: <a class="external" href="http://www.shortview.de/?mc=sv_ext_mf@gmx">http://www.shortview.de/?mc=sv_ext_mf@gmx</a></p>