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 #2721 (Feedback): Some few zalloc calls to objcache ones replacementshttps://bugs.dragonflybsd.org/issues/27212014-08-30T17:12:51Zdclinkdevnexen@gmail.comDragonFlyBSD - Bug #2617 (Feedback): Possible issue with wireless mouse on 3.6 releasehttps://bugs.dragonflybsd.org/issues/26172013-12-20T09:52:27ZFilippoMofilippomore@yahoo.com
<p>I have a possible bug to report on RELEASE_3_6_0 on i386 arch.<br />I have a usb cordless mouse that does'not work.It is correctly identified<br />as ums0 and there is a /dev/ums0 on the same receiver there is a keyboard that works and the hardware works on other OSes.<br />I killed moused and started moused -p /dev/sysmouse but it did not work.<br />Filippo</p>
<p>On Thursday, December 19, 2013 9:00 PM, "<a class="email" href="mailto:bugs-request@dragonflybsd.org">bugs-request@dragonflybsd.org</a>" <<a class="email" href="mailto:bugs-request@dragonflybsd.org">bugs-request@dragonflybsd.org</a>> wrote:</p>
<p>Send Bugs mailing list submissions to<br /> <a class="email" href="mailto:bugs@dragonflybsd.org">bugs@dragonflybsd.org</a></p>
<p>To subscribe or unsubscribe via the World Wide Web, visit<br /> <a class="external" href="http://lists.dragonflybsd.org/mailman/listinfo/bugs">http://lists.dragonflybsd.org/mailman/listinfo/bugs</a><br />or, via email, send a message with subject or body 'help' to<br /> <a class="email" href="mailto:bugs-request@dragonflybsd.org">bugs-request@dragonflybsd.org</a></p>
<p>You can reach the person managing the list at<br /> <a class="email" href="mailto:bugs-owner@dragonflybsd.org">bugs-owner@dragonflybsd.org</a></p>
<p>When replying, please edit your Subject line so it is more specific<br />than "Re: Contents of Bugs digest..."</p>
<p>Today's Topics:</p>
<p> 1. [DragonFlyBSD - Bug <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a>] (Resolved) panic while running gdb<br /> test suite (Pierre Abbat via Redmine)</p>
<hr />
<p>Message: 1<br />Date: Wed, 18 Dec 2013 22:35:30 -0800<br />From: Pierre Abbat via Redmine<br /> <<a class="email" href="mailto:bugtracker-admin@leaf.dragonflybsd.org">bugtracker-admin@leaf.dragonflybsd.org</a>><br />To: undisclosed-recipients:;<br />Subject: [DragonFlyBSD - Bug <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a>] (Resolved) panic while running gdb<br /> test suite<br />Message-ID:<br /> <<a class="email" href="mailto:redmine.journal-11682.20131219063529.7a9eb072d3b04776@leaf.dragonflybsd.org">redmine.journal-11682.20131219063529.7a9eb072d3b04776@leaf.dragonflybsd.org</a>><br /> <br />Content-Type: text/plain; charset=UTF-8</p>
<p>Issue <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a> has been updated by phma.</p>
<p>Status changed from New to Resolved</p>
<p>It is fixed. Thanks.</p>
<p>----------------------------------------<br />Bug <a class="issue tracker-1 status-3 priority-5 priority-high3 closed" title="Bug: panic while running gdb test suite (Resolved)" href="https://bugs.dragonflybsd.org/issues/2615">#2615</a>: panic while running gdb test suite<br /><a class="external" href="http://bugs.dragonflybsd.org/issues/2615#change-11682">http://bugs.dragonflybsd.org/issues/2615#change-11682</a></p>
<ul>
<li>Author: phma</li>
<li>Status: Resolved</li>
<li>Priority: High</li>
<li>Assignee: </li>
<li>Category: </li>
<li>Target version: <br />----------------------------------------<br />see <a class="external" href="https://github.com/DragonFlyBSD/DPorts/wiki/Run-GDB-testsuite">https://github.com/DragonFlyBSD/DPorts/wiki/Run-GDB-testsuite</a></li>
</ul>
<p>I ran the testsuite on gdb 7.6.1 and it crashed partway through. This is as far as it got:</p>
<p>Running ./gdb.base/fileio.exp ...<br />FAIL: gdb.base/fileio.exp: Open for write but no write permission returns <br />EACCES<br />FAIL: gdb.base/fileio.exp: Unlinking a file in a directory w/o write access <br />returns EACCES<br />Running ./gdb.base/gcore-relro.exp ...<br />Running ./gdb.base/huge.exp ...<br />Running ./gdb.base/find.exp ...<br />Running ./gdb.base/ctxobj.exp ...<br />Running ./gdb.base/cond-eval-mode.exp ...<br />Running ./gdb.base/arrayidx.exp ...<br />Running ./gdb.base/eval-skip.exp ...<br />Running ./gdb.base/attach.exp ...</p>
<p>It crashed in the same place both times. The kernel dumps are numbers 2 and 3 in leaf:/home/phma/crash/zyxomma/. I need this fixed so that I can fix the thread bug in gdb.</p>
<p>-- <br />You have received this notification because you have either subscribed to it, or are involved in it.<br />To change your notification preferences, please click here: <a class="external" href="http://bugs.dragonflybsd.org/my/account">http://bugs.dragonflybsd.org/my/account</a></p>
<hr />
<p>_<em><i></em></i>__<em>_</em>___________________________________<br />Bugs mailing list<br /><a class="email" href="mailto:Bugs@dragonflybsd.org">Bugs@dragonflybsd.org</a><br /><a class="external" href="http://lists.dragonflybsd.org/mailman/listinfo/bugs">http://lists.dragonflybsd.org/mailman/listinfo/bugs</a></p>
End of Bugs Digest, Vol 16, Issue 10
<hr /> DragonFlyBSD - Submit #2438 (Feedback): TRIM fixeshttps://bugs.dragonflybsd.org/issues/24382012-10-22T04:59:20ZAnonymous
<p>This patch is to fix bugs associated with TRIM.</p>
<p>If trim is on as a option, display that when typing "mount".</p>
<p>Change post-trim ffs_blkfree_cg() to use taskqueue_swi_mp and get mp token when modifying freemap.</p>
<p>Make sure TRIM works with softdep. Stash a copy of that vnode's mount point in the ufs inode so that if we are using softdep, we can get access to the mount point through the faked up inode (created in freeblocks). The original mount point path (ip->i_devvp->v_mount->mnt_flag) doesn't have the mount point options.</p>
<p>Tim</p> DragonFlyBSD - Bug #1824 (Feedback): kernel panic, x86, 2.7.3.859.ge5104https://bugs.dragonflybsd.org/issues/18242010-09-08T06:25:18Zakirchhoff135014
<p>SMP enabled, otherwise a GENERIC kernel.</p>
<p>Full backtrace:</p>
<p>(kgdb) bt<br />#0 _get_mycpu (di=0xc06ebee0) 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=0xc06ebee0) at <br />/usr/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> 0xc0315d31 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:880<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> 0xc03162f1 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> 0xc03165ba in panic (fmt=0xc06122c4 "m_copym, length > size of mbuf <br />chain")<br /> at /usr/src/sys/kern/kern_shutdown.c:786<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> 0xc034f662 in m_copym (m=0x0, off0=32, len=24, wait=4) at <br />/usr/src/sys/kern/uipc_mbuf.c:1113<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> 0xc03ec2e6 in tcp_output (tp=0xdcc96d88) at <br />/usr/src/sys/netinet/tcp_output.c:723<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> 0xc03f38da in tcp_usr_send (so=0xc6a73698, flags=<value optimized out>, <br />m=0xe20ca900, nam=0x0, control=0x0, <br /> td=0xdcc96988) at /usr/src/sys/netinet/tcp_usrreq.c:762<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> 0xc03518a4 in netmsg_pru_send (msg=0xe5c15b5c) at <br />/usr/src/sys/kern/uipc_msg.c:548<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> 0xc03a4674 in netmsg_service (msg=0xe5c15b5c, mpsafe_mode=1, mplocked=0) <br />at /usr/src/sys/net/netisr.c:310<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> 0xc03a478a in netmsg_service_loop (arg=0xc068cda0) at <br />/usr/src/sys/net/netisr.c:357<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> 0xc031f2ae in lwkt_deschedule_self (td=Cannot access memory at address 0x8<br />) at /usr/src/sys/kern/lwkt_thread.c:278<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)</p>
<p>I was building some packages in the background at the time. I was ssh'ed in <br />from a linux box, and running x2x to allow me to move the mouse and keyboard <br />from the linux box to the DF box. At the time of the lock up, I was moving <br />the mouse around on the DF box. Though I have no idea if that's related to <br />the crash, that's the only thing that comes to mind.</p>
<p>Adam</p> DragonFlyBSD - Bug #1718 (Feedback): IDE disk drive not detected by x86_64 2.6.1 Live CDhttps://bugs.dragonflybsd.org/issues/17182010-04-08T10:54:30Zbcox
<p>I've been attempting to install DragonFly 2.6.1 (x86_64 version) onto an IDE<br />hard drive with no luck so far. I have a Gigabyte EP45-DS3L motherboard with a<br />JMicron JMB368 IDE controller, a SATA DVD drive, a SATA2 WD Caviar disk drive<br />and an older WD Caviar IDE drive. Both SATA drives are running in AHCI mode and<br />are detected by the kernel just fine. (Unfortunately, I don't have enough<br />contiguous free space to install DragonFly with the HAMMER filesystem on the<br />SATA disk drive, hence the reason I tried to use the older spare IDE drive.)</p>
<p>FreeBSD 8.0 Live CD and Debian Linux 2.6.32 can see all three drives just fine,<br />but for some reason the IDE disk isn't getting attached by DragonFly. I tried<br />turning off AHCI mode and running the SATA drives in legacy IDE mode, and<br />DragonFly finds the SATA drives (as IDE devices) just fine, but still no<br />attachment of the IDE disk. My BIOS also has an option to run SATA drives in<br />"native IDE" mode, but that caused all sorts of problems involving<br />"TEST_UNIT_READY taskqueue timeout" and "xft: func = 0xffffffff8016b5d8 arg=0" <br />error messages and resulted in the kernel getting stuck in timeout loops. I<br />should note that the JMicron controller itself is detected in all cases.</p>
<p>Matt Dillon helped me out on the IRC channel and suggested some things like<br />booting without ACPI, but nothing worked in the end. He suspects that there's a<br />PCI resource issue involved.</p>
<p>Attached is the verbose dmesg output with AHCI mode enabled for the SATA drives. <br />In it I found that device_probe_and_attach is returning error code 6 when<br />probing the JMicron controller (atapci0).</p> DragonFlyBSD - Bug #1618 (Feedback): collision for 'struct pmap' when using RPC and <sys/user.h>https://bugs.dragonflybsd.org/issues/16182009-11-30T14:26:50Zcarenas
<p>resulting on the following FTBS for ganglia monitoring on recent versions of<br />DragonFlyBSD (confirmed with 2.4.1 and also 2.5.1.302.gc4e67-DEVELOPMENT)</p>
<pre><code>libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -I../../include -g -O2 -Wall -MT metrics.lo -MD -MP -MF .deps/metrics.Tpo -c metrics.c -fPIC -D PIC -o .libs/metrics.o In file included from /usr/include/rpc/rpc.h:73,<br /> from ../libmetrics.h:14,<br /> from metrics.c:36:<br /> /usr/include/rpc/pmap_prot.h:89: error: redefinition of 'struct pmap'</code></pre>
<p>the problem isn't specific to ganglia though as it comes from a conflict<br />from the system headers :</p>
<pre><code>/usr/include/machine/pmap.h (pulled from sys/user.h)<br /> /usr/include/rpc/pmap_prot.h (pulled from rpc/rpc.h)</code></pre>
<p>FreeBSD has also a similar problem which is worked around by removing that<br />header and their dependents from the include before including <sys/user.h></p>
<pre><code>#define <em>MACHINE_PMAP_H</em><br /> #define <em>VM_MAP</em><br /> #include &lt;sys/user.h&gt;</code></pre>
<p>and as a similar workaround the following has been implemented for DFBSD</p>
<pre><code>/*
* XXX: HACK HACK HACK - avoid including machine/pmap.h and things that
* depend on it to avoid collision with struct pmap in rpc/pmap_prot.h<br /> */<br /> #define <em>MACHINE_PMAP_H</em><br /> #define <em>VM_VM_MAP_H</em><br /> #include &lt;sys/user.h&gt;</code></pre>
<p>this problem was introduced around release of 2.4.0 as previous releases<br />didn't have any conflicts.</p>
<p>Carlo</p> DragonFlyBSD - Bug #1587 (Feedback): can't gdb across forkhttps://bugs.dragonflybsd.org/issues/15872009-10-25T23:56:18Zcorecode
<p>When the debugged process performs a fork(), gdb/ptrace won't notice and <br />will not be able to remove breakpoints in the new child. When the child <br />then hits a breakpoint, it will receive a SIGTRAP and dump core.</p>
<p>gdb needs to be aware of forks, so that it will be able to remove the <br />breakpoints in the child.</p>
<p>Test: gdb sh and break stalloc.</p> DragonFlyBSD - Bug #1521 (Feedback): amd64 2.4 livecd won't mount root at boothttps://bugs.dragonflybsd.org/issues/15212009-09-19T06:11:09Zbolapara
<p>Hello,</p>
<p>I've got an x64 machine with an ich9 sata disk controller. With the<br />i386 live dvd, I can boot the live system all the way and perform an<br />installation. With x64, it will boot no further than trying to mount<br />the rootfs from the live cd and will fail and drop me to the<br />mountroot> prompt. I then tried to manually mount each of the<br />available devices and got nothing but error code 22. I've attached<br />the boot logs in order to help debug. I did jump on IRC and talk to a<br />few people but it boiled down to the suggestion to send a report to<br />this address. Thanks!</p>
<p>Josh</p> DragonFlyBSD - Bug #1481 (Feedback): panic: assertion: kva_p(buf) in soopt_from_kbuf (after ipfw ...https://bugs.dragonflybsd.org/issues/14812009-09-01T22:10:50Zcombiner
<p>Host panics when root does "ipfw pipe show".<br />Doesn't matter if dummynet.ko is loaded via kldload <br />or it is loaded with loader.<br />Recompilation of dummynet.ko doesn't solve this.<br />Dumps availible on <a class="external" href="http://Sahara.org.ua/~planner/{vmcore,kernel}.{0,1">http://Sahara.org.ua/~planner/{vmcore,kernel}.{0,1</a>}<br />(first dump with release binary, second - with module compiled from git branch <br />v2.2.1)<br />kgdb output follows:</p>
<p>Unread portion of the kernel message buffer:<br />panic: assertion: kva_p(buf) in soopt_from_kbuf<br />Trace beginning at frame 0xc8cccb98<br />panic(c8cccbbc,0,cb6cfca0,c06845b4,c8cccbc8) at panic+0x8c<br />panic(c0570d57,c058c319,c054fa2c,0,c8cccd30) at panic+0x8c<br />soopt_from_kbuf(cb6cfca0,fffffff8,0,c1525440,cacaf000) at soopt_from_kbuf+0x7a<br />ip_dn_sockopt(cb6cfca0) at ip_dn_sockopt+0xe4<br />rip_ctloutput(c1622b00,cb6cfca0,1,c8cccd68,c037a3fd) at rip_ctloutput+0xaa<br />netmsg_pru_ctloutput(cb6cfbfc) at netmsg_pru_ctloutput+0x10<br />netmsg_service(cb6cfbfc,0,1,c06845b4,ff800000) at netmsg_service+0x53<br />netmsg_service_loop(c0688014,0,0,0,0) at netmsg_service_loop+0x18<br />lwkt_exit() at lwkt_exit</p>
<p>syncing disks... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 <br />done<br />Uptime: 5d23h58m0s</p>
<p>dumping to dev #ad/0x20001, blockno 1590920<br />dump 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 <br />229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 <br />209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 <br />189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 <br />169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 <br />149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 <br />129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 <br />109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 <br />86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 <br />60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 <br />34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 <br />7 6 5 4 3 2 1 0</p>
<p>GNU gdb 6.7.1<br />Copyright (C) 2007 Free Software Foundation, Inc.<br />License GPLv3+: GNU GPL version 3 or later <<a class="external" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>><br />This is free software: you are free to change and redistribute it.<br />There is NO WARRANTY, to the extent permitted by law. Type "show copying" <br />and "show warranty" for details.<br />This GDB was configured as "i386-dragonfly".<br />(kgdb) bt<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> 0xc02e3ea6 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:375<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> 0xc02e3fc7 in panic (fmt=0xc0570d57 "assertion: %s in %s") at /usr/src/sys/<br />kern/kern_shutdown.c:800<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> 0xc0313061 in soopt_from_kbuf (sopt=0x0, buf=0xfffffff8, len=0) at /usr/src/<br />sys/kern/uipc_socket.c:1451<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> 0xc03a070e in ip_dn_sockopt (sopt=0xcb6cfca0) at /usr/src/sys/net/dummynet/<br />ip_dummynet_glue.c:499<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> 0xc03a69a9 in rip_ctloutput (so=0x0, sopt=0x0) at /usr/src/sys/netinet/<br />raw_ip.c:362<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> 0xc0312dc8 in netmsg_pru_ctloutput (msg=0xcb6cfbfc) at /usr/src/sys/kern/<br />uipc_msg.c:652<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> 0xc037a3fd in netmsg_service (msg=0x0, mpsafe_mode=0, mplocked=1) at /usr/<br />src/sys/net/netisr.c:307<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> 0xc037a8ad in netmsg_service_loop (arg=0xc0688014) at /usr/src/sys/net/<br />netisr.c:333<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> 0xc02eaa5e in lwkt_deschedule_self (td=Cannot access memory at address 0x8<br />) at /usr/src/sys/kern/lwkt_thread.c:253<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)<br />(kgdb)</p>
<p>DragonFly 2.2.1-RELEASE #0: Sun Apr 26 18:38:14 GMT 2009 <br /><a class="email" href="mailto:root@test29.backplane.com">root@test29.backplane.com</a>:/usr/obj/usr/src/sys/DFLYLIVE i386</p> DragonFlyBSD - Bug #1397 (Feedback): jobs -l output inconsistency when called from scripthttps://bugs.dragonflybsd.org/issues/13972009-06-08T00:49:49ZAnonymous
<p>Salute.</p>
<p>The jobs(1) utility gives different output when called from a script and when<br />from an interactive shell.</p>
<pre>
[beket@voyager ~] cat testjobs.sh
#!/bin/sh
sleep 30 &
jobs -l
[beket@voyager ~] sh testjobs.sh
[1] + 10005 Running
[beket@voyager ~] sleep 30 &
[1] 10006
[beket@voyager ~] jobs -l
[1]+ 10006 Running sleep 30 &
[beket@voyager ~]
</pre>
<p>It is not clear whether the jobs(1) should work at all inside a script. POSIX<br />says that since it doesn't fall into the 'special' built-in category a new<br />environment (subshell?) would be created upon its invocation. Even this is true,<br />the jobs aren't specific to the shell environment, so they should be visible to<br />jobs(1). And in any case, the command should either print nothing or print all<br />the fields.</p>
<p>NetBSD 5.0:<br /><pre>
$ sh testjobs.sh
[1] + 27159 Running sleep 30
</pre></p>
<p>SunOS 5.10:<br /><pre>
tuxillo@solaris$ /usr/xpg4/bin/sh testjobs.sh
[1] + 11754 Running <command unknown>
</pre></p>
<p>FreeBSD: same as us. (kindly reported by vstemen at #dragonflybsd).</p>
<p>Any thoughts ?</p>
<p>Best regards,<br />Stathis</p> DragonFlyBSD - Bug #1287 (Feedback): altq configuration doesn't workhttps://bugs.dragonflybsd.org/issues/12872009-02-18T20:47:35Zcorecode
<p>There seem to be serious issues with ALTQ.</p>
<p>Just now I tried to disable it, by removing altq queue definitions from pf.conf<br />+ resync, by disabling pf and also by flushing all pf data. Nevertheless it<br />kept on doing bandwidth shaping. Had to reboot to get rid of this.</p>
<p>Also I had the feeling that changing the altq queue parameters + resync did not<br />have any effect on the queueing behavior (changed from 560kbps -> 5kbps), but I<br />could be mistaken in that regard.</p> DragonFlyBSD - Bug #911 (Feedback): kldload/kernel linker can exceed malloc reserve and panic systemhttps://bugs.dragonflybsd.org/issues/9112008-01-11T06:31:28Zcorecode
<p>hey,</p>
<p>I just booted with hw.physmem=64m and got a panic when trying to load a module:</p>
<p>panic: kld: malloc limit exceeded</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> 0xc018450c in boot (howto=256) at /usr/build/src/sys/kern/kern_shutdown.c:375<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> 0xc0184661 in panic (fmt=Variable "fmt" is not available.<br />) at /usr/build/src/sys/kern/kern_shutdown.c:800<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> 0xc0182129 in kmalloc (size=78, type=0xc02f5600, flags=2)<br /> at /usr/build/src/sys/kern/kern_slaballoc.c:445<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> 0xc01678b4 in linker_make_file (pathname=0xc641b000 "./nvidia.ko", priv=0xc63ea028, <br /> ops=0xc02f5bc8) at /usr/build/src/sys/kern/kern_linker.c:369<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> 0xc016a773 in link_elf_load_module (filename=0xc641b000 "./nvidia.ko", result=0xc83efc7c)<br /> at /usr/build/src/sys/kern/link_elf.c:604<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> 0xc01684e0 in linker_load_file (filename=0xc641b000 "./nvidia.ko", result=0xc83efca8)<br /> at /usr/build/src/sys/kern/kern_linker.c:272<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> 0xc016871c in sys_kldload (uap=0xc83efcf0) at /usr/build/src/sys/kern/kern_linker.c:724</p>
<p>the problem seems to be that M_LINKER already used 10% of all memory (allegedly). In this case kmalloc() simply panics if passing M_WAITOK without M_NULLOK. This is quite unfortunate. Shouldn't we try to stay alive and print a warning and block, hoping that the problem will resolve itself?</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #901 (Feedback): route show needs to get data from all cpushttps://bugs.dragonflybsd.org/issues/9012007-12-31T00:07:48Zcorecode
<p>when executing `route show' on my MP system, I will get varying results. <br />Additionally, it will print all temporary route entries as well, even for hosts<br />outside the local network.</p> DragonFlyBSD - Bug #847 (Feedback): processes getting stuck on mount pointhttps://bugs.dragonflybsd.org/issues/8472007-11-23T07:03:06Zcorecode
<p>Hey,</p>
<p>I just experienced the infamous ``cache_lock: blocked on 0xd591d418 ""'' message. Checking why the process got stuck revealed that the lock is actually being held by another process which is in the process of doing a lstat(2) on /mnt, a nfs mount which server went away. The stuck process is doing the same, fwiw.</p>
<p>So here it is not a namecache bug, but rather an artifact of nfs being stuck. Anoying nevertheless. Anybody have a clue how to fix that? Yea, mount with -intr. Why don't we do that per default?</p>
<p>cheers<br /> simon</p>