DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082018-10-26T14:34:46ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3152 (Feedback): Console's size in ttyv0 and single user mode is sticking to ...https://bugs.dragonflybsd.org/issues/31522018-10-26T14:34:46Zovertime
<p>I had try</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 #2644 (Feedback): 3.6.0-REL trap 9 on boothttps://bugs.dragonflybsd.org/issues/26442014-02-20T06:53:30Zmemmerto
<p>Booting 3.6.0-REL on my not-quite-ancient IBM x3400 (with Intel E5310 QC processor) traps:</p>
<p>CPU0 stopping CPUs: 0x0000000e<br /> stopped<br />Stopped vmx_set_ctl_setting+0x36: rdmsr<br />db> where<br />vmx_set_ctl_setting() at vmx_set_ctl_setting+0x36 0xffffffff809721f6<br />vmx_set_default_settings() at vmx_set_default_settings+0x1e 0xffffffff80972326<br />vmx_init() at vmx_init+0x5c 0xffffffff8097305e<br />vmm_init() at vmm_init+0xa3 0xffffffff80971c1f<br />mi_startup() at mi_startup+0xb1 0xffffffff80532775<br />db></p>
<p>For reference, 3.4.2-REL worked fine on this machine.</p> DragonFlyBSD - Bug #2636 (Feedback): Add -x flag to iostat (a la solaris)https://bugs.dragonflybsd.org/issues/26362014-02-13T21:50:00Ztuxillo
<p>Add -x flag to iostat (a la solaris)</p> DragonFlyBSD - Bug #2556 (Feedback): DragonFly v3.5.0.81.gd3479 - Process signal weirdnesshttps://bugs.dragonflybsd.org/issues/25562013-05-07T22:59:34Ztuxillo
<p>Hi,</p>
<p>tmux has a memory leak somewhere and it was causing a lot of swap memory to be used. I started using truss(1) to see what it was doing and after 3-4 tracing attempts the tmux process was stuck in status "stopevent". After sending to it all sorts of signals (CONT, HUP, KILL) the process is kept stopped in the same situation. I also tried disabling tracing with ktrace(1) but it didn't help.</p>
<p>Eventually I tried to reboot the virtual machine but it got stuck for around 10 minutes without actually being able to shutdown. Last step was dropping to DDB and producing a dump. Dump is available on leaf on demand. See below the backtrace of the thread involved (tmux process)</p>
<p>Best regards,<br />Antonio Huete</p>
<hr />
<p>(kgdb) thread 26<br />[Switching to thread 26 (pid 835/0, tmux)]<br />#0 0xffffffff8050dfb0 in lwkt_switch () at /home/source/dfbsd/sys/kern/lwkt_thread.c:872<br />872 /home/source/dfbsd/sys/kern/lwkt_thread.c: No such file or directory.<br />(kgdb) bt<br />#0 0xffffffff8050dfb0 in lwkt_switch () at /home/source/dfbsd/sys/kern/lwkt_thread.c:872<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> 0xffffffff80518f0e in tsleep (ident=ident@entry=0xffffffe071efc990, flags=flags@entry=1024, <br /> wmesg=wmesg@entry=0xffffffff8097e168 "stopevent", timo=timo@entry=0) at /home/source/dfbsd/sys/kern/kern_synch.c:612<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> 0xffffffff80538091 in stopevent (p=p@entry=0xffffffe071efc780, event=event@entry=4, val=val@entry=7)<br /> at /home/source/dfbsd/sys/kern/sys_process.c:771<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> 0xffffffff808c5a7a in syscall2 (frame=0xffffffe07280e9f8) at /home/source/dfbsd/sys/platform/pc64/x86_64/trap.c:1229<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> 0xffffffff808af75b in ?? () at /home/source/dfbsd/sys/platform/pc64/x86_64/exception.S:323<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> 0x00000000000000c5 in ?? ()<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> 0x0000000000000000 in ?? ()</p> DragonFlyBSD - Bug #1727 (Feedback): CD boot panic (2.6.1) (usb?)https://bugs.dragonflybsd.org/issues/17272010-04-14T08:55:06Zkiril
<p>dfly Live CD 2.6.1 panics on boot. logging a bug report with photos attached <br />as per SW's request. booting with ehci does not make any difference.</p>
<p>please let me know if a .zip it not an acceptable format.</p> DragonFlyBSD - Bug #1592 (Feedback): AcpiOSUnmapMemory : Warning, deallocation did not track allo...https://bugs.dragonflybsd.org/issues/15922009-10-31T23:37:47Zeocallaghan
<p>Each time the machine shuts down, dmesg throws a nasty looking message:</p>
<p>Shutting down ACPI<br />AcpiOsUnmapMemory : Warning, deallocation did not track allocation:<br />0xda627f60/000000a0 (actual was 0xda628000/00000032)</p>
<p>ver, 2.4.1 , i386, Lenovo X301.</p>
<p>Regards,<br />Edward.</p> DragonFlyBSD - Bug #1428 (Feedback): POSIX.1e implementation is too oldhttps://bugs.dragonflybsd.org/issues/14282009-07-17T02:08:53Zhasso
<p>Our posix1e(3) implementation is too old and not compatible with any <br />recent enough piece of software.</p> DragonFlyBSD - Bug #1411 (Feedback): Burning doesn't work with ahci(4)https://bugs.dragonflybsd.org/issues/14112009-06-28T02:21:19Zhasso
<p>Burning (I have only DVD-RW to test with, though) doesn't work with SATA <br />burner attaching to ahci(4). Nata still works fine. Verbose cdrecord log for <br />simple blank process is available at <br /><a class="external" href="http://leaf.dragonflybsd.org/~hasso/ahci-cdrecord-verbose-blank.log">http://leaf.dragonflybsd.org/~hasso/ahci-cdrecord-verbose-blank.log</a></p> DragonFlyBSD - Bug #1332 (Feedback): DFBSD 2.2 - Booting usbcdrom/usbsticks on thinkpad hangs on ...https://bugs.dragonflybsd.org/issues/13322009-04-09T19:44:06Ztuxillo
<p>Hi</p>
<p>This is a bug reported by claus on the IRC and initally investigated by Jordan<br />(smtms).</p>
<p>It seems that booting USB cdrom/stick on a Thinkpad (model still to determine)<br />hangs and stops with BTX Halted.</p>
<p>claus reported that FBSD 7.1 booted without problems with that USB Cdrom drive,<br />but with FBSD 7.0 it crashes also.</p>
<p>This is a know issue on FreeBSD that was fixed in revision 177039. Also relevant<br />revisions are 181433, 181436 and 189017.</p>
<p>Cheers,<br />Antonio</p> DragonFlyBSD - Bug #1127 (Feedback): cdrom drive not detectedhttps://bugs.dragonflybsd.org/issues/11272008-08-22T22:48:07Ztgr
<p>Hi, I've got a bit of a problem with the install CD. I've tested this on<br />2.0 and 2.1.0-DEV (i.e. the daily iso downloadable on 2008.08.22). This<br />happens way before I can make any sort of FS, but the same machine's<br />booted up XP, Kubuntu and FBSD5.4.</p>
<p>Anyway, what I can see on the bootup screen of that machine now is as<br />follows:</p>
<p><quote><br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:acd0<br />no disk named 'acd0'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:acd1<br />no disk named 'acd1'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:/dev/acd0a<br />no disk named 'acd0a'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br /></quote></p>
<p>When I then type "panic", the following appears:</p>
<p><quote><br />panic: panic from console<br />Trace beginning at frame 0xc872ca8<br />panic(c05ce64a,c06bc720,c05d0be3,c0872cd8,6) at panic+0x99<br />panic(c05d0be3,c05ce4a6,696e6170,c0560063,8) at panic+0x99<br />vfs_mountroot_ask(c4360b70,c06702dc,d7886c3c,87d000,c0872d98) at<br />vfs_mountroot_ask+0xd7<br />vfs_mountroot(0,87d000,86fc00,87d000,0) at fvs_mountroot+oxcf<br />mi_startup(86f000,d,c06b2a38,c0872c24,c0872c0c) at mi_startup+0x99<br />begin() at begin+0x42<br />Debugger("panic")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0<br /></quote></p>
<p>I've run this twice in a row just to verify all the values, in case they<br />changed. They didn't.</p>
<p>If there is any more information I can provide, please do tell. This<br />system is not in use in any other way, all data on the HDs etc is<br />discardable, so anything goes.</p> DragonFlyBSD - Bug #570 (Feedback): 1.8.x: ACPI problemshttps://bugs.dragonflybsd.org/issues/5702007-03-03T11:46:01Zqhwt+dfly
<p>So if you enable ACPI and boot, it won't respond to keyboard no matter<br />whether you choose to boot into single- or multi-user mode?</p>
<p>So ... your keyboard does not work when you boot straight into the<br />single user mode, whether with or without ACPI driver enabled, right?<br />If not, I have no idea what this part really means:<br /> > But If I boot to non-ACPI-mode, everything works<br /> > just fine, but I can't get to sigle user mode, because prompt freezes<br /> > there too...</p>
<p>If the message buffer(which dmesg command shows you) survives across<br />reboot, I'd like to look at it after you boot with ACPI driver enabled<br />and booted with `boot -v' from the boot loader prompt (did I ask if<br />keyboard works when you go into the boot loader prompt?).</p>
<p>Cheers.</p> DragonFlyBSD - Bug #385 (Feedback): Mail archive address removalhttps://bugs.dragonflybsd.org/issues/3852006-11-22T22:22:03Zjustin
<p>Here's a question for everyone: I had originally the mail archive to<br />completely remove mail addresses, but it seems to mostly be annoying -<br />contacting someone from an archived email would be a dead end unless you<br />happened to already know the person's email address. Meanwhile, the<br />DragonFly lists are archived other places like MARC and Gmane, and<br />addresses are at best mildly obfusticated there.</p>
<p>Opinions? If anyone is significantly bothered by this, I'll keep the<br />addresses completely hidden.</p> DragonFlyBSD - Bug #293 (Feedback): Various updates to the handbookhttps://bugs.dragonflybsd.org/issues/2932006-08-11T04:26:06Zvictor
<p>Hi,</p>
<p>there are 3 patches attached:</p>
<p>book.diff - Updates the copyright info relating to FreeBSD at the header<br /> of the handbook.</p>
<p>dfbsd-updating - Update cvsup port path to the current pkgsrc version in<br /> the chapter "Updating DragonFly".</p>
<p>basics.diff - Update various paths relating to pkgsrc and hier(7). Also<br /> make it use the new entity for pkgsrc <br /> tree/collection/framework.</p> DragonFlyBSD - Bug #285 (Feedback): interrupt latency with re without ip address configuredhttps://bugs.dragonflybsd.org/issues/2852006-08-07T06:00:07Zthomas.nikolajsen
<p>Playing sound using pcm(4)/snd(4) gives bad quality: hiss and hops, like sound isn't playing for very short time periods.</p>
<p>This is experienced:<br /> - not having SMP in kernel config (eg GENERIC)<br /> - from dfly-1.5 26th December '05 (24th is ok using kernels from chlamydia);<br />including HEAD.</p>
<p>dfly-1.4 is ok, including 1.4.4.</p>
<p>Using audio/mpg123 for MP3, 'cp test.raw /dev/dspW' or pcmplay for decoded sound.<br />Buffering audio data with mpg123 -b doesn't sound like making any difference.</p>
<p>CPU load doesn't sound like making any difference.<br />Problem experienced on several systems, using snd_via8233 and snd_ich.</p>
<p>No X11 used.</p>
<pre><code>-thomas</code></pre>