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 - Bug #2958 (Feedback): Hammer FS dies during pruning after massive write loadhttps://bugs.dragonflybsd.org/issues/29582016-10-09T11:11:20Zneilbkyuupichan@gmail.com
<p>I have one or two apps that use leveldb badly, and read and write a lot of data to disk.</p>
<p>I have a 256GB SSD, and to avoid running out of space within an hour or two of starting these apps, I have them use the DB on a no history PFS and clean the FS intraday. This kernel freezes around 40% of the time during pruning. The other operations are never a problem.</p>
<p>I don't really know what I can give as useful information. Normal usage without these apps is fine; hammer never gives a problem. Just after 100s of GBs of writes pruning sometimes kills the kernel. The FS is always fine and not corrupt after rebooting, and redoing the clean usually then succeeds (though once it died again, after making progress freeing space).</p>
<p>Incidentally, during these pruning phases that do succeed, X completely freezes for 20-30s several times; the mouse doesn't move and the desktop clock I have stops ticking. Not losing userspace interactivity would be nice.</p>
<p>$ uname -a<br />DragonFly zotac.akihabara.co.uk 4.5-DEVELOPMENT DragonFly v4.5.0.681.g2e03c8-DEVELOPMENT <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>: Sun Mar 20 21:54:05 JST 2016 <a class="email" href="mailto:root@zotac.akihabara.co.uk">root@zotac.akihabara.co.uk</a>:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64</p> DragonFlyBSD - 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 #2638 (Feedback): Fix machdep.pmap_mmu_optimizehttps://bugs.dragonflybsd.org/issues/26382014-02-13T21:51:39Ztuxillo
<p>Fix machdep.pmap_mmu_optimize (currently off by default in commit 1ac5304a10366be7ed3129ceee7ca94beb0f3183 ). Affects apache and rtorrent for sure.</p>
<p>"might be fixed here: a44410dd8663abb121417692995d3b365f32fd6e<br />update: it's not fixed"</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 #2347 (Feedback): Hammer PFSes destroy does not give back full space allocated...https://bugs.dragonflybsd.org/issues/23472012-04-11T07:17:48Zsgeorgesgeorge.ml2@gmail.com
<p>I was mirroring PFSes from 3.1 dev to slaves in 3.02 and I found that<br />the PFSes took more space on the 3.02 slave.<br />Investigating I found this strange thing</p>
<p>94 GB is allocated for this slave PFS. But when it is removed only 52<br />GB is freed :-(</p>
<p>dfly-bkpsrv2# hammer dedup /pfs/software<br />Dedup running<br />Dedup /pfs/software succeeded<br />Dedup ratio = 1.06<br /> 100 GB referenced<br /> 94 GB allocated<br /> 4339 KB skipped<br /> 429 CRC collisions<br /> 0 SHA collisions<br /> 1 bigblock underflows<br /> 0 new dedup records<br /> 0 new dedup bytes</p>
<p>dfly-bkpsrv2# df -h<br />Filesystem Size Used Avail Capacity Mounted on<br />ROOT 459G 354G 106G 77% /<br />devfs 1.0K 1.0K 0B 100% /dev<br />/dev/serno/QM00001.s1a 756M 168M 527M 24% /boot<br />/pfs/<code>@-1:00001 459G 354G 106G 77% /var<br />/pfs/</code>@-1:00002 459G 354G 106G 77% /tmp<br />/pfs/<code>@-1:00003 459G 354G 106G 77% /usr<br />/pfs/</code>@-1:00004 459G 354G 106G 77% /home<br />/pfs/<code>@-1:00005 459G 354G 106G 77% /usr/obj<br />/pfs/</code>@-1:00006 459G 354G 106G 77% /var/crash<br />/pfs/<code>@-1:00007 459G 354G 106G 77% /var/tmp<br />procfs 4.0K 4.0K 0B 100% /proc<br />dfly-bkpsrv2# ls<br />home software usr var<br />var.tmp vms2-lxc<br />mysql-baks tmp usr.obj var.crash vms1-lxc<br />dfly-bkpsrv2# hammer pfs-destroy /pfs/software<br />You have requested that PFS#11 () be destroyed<br />This will irrevocably destroy all data on this PFS!!!!!<br />Do you really want to do this? y<br />Destroying PFS #11 () in 5 4 3 2 1.. starting destruction pass<br />pfs-destroy of PFS#11 succeeded!<br />dfly-bkpsrv2# df -h<br />Filesystem Size Used Avail Capacity Mounted on<br />ROOT 459G 302G 158G 66% /<br />devfs 1.0K 1.0K 0B 100% /dev<br />/dev/serno/QM00001.s1a 756M 168M 527M 24% /boot<br />/pfs/</code>@-1:00001 459G 302G 158G 66% /var<br />/pfs/<code>@-1:00002 459G 302G 158G 66% /tmp<br />/pfs/</code>@-1:00003 459G 302G 158G 66% /usr<br />/pfs/<code>@-1:00004 459G 302G 158G 66% /home<br />/pfs/</code>@-1:00005 459G 302G 158G 66% /usr/obj<br />/pfs/<code>@-1:00006 459G 302G 158G 66% /var/crash<br />/pfs/</code>@-1:00007 459G 302G 158G 66% /var/tmp<br />procfs 4.0K 4.0K 0B 100% /proc</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 #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 #1717 (Feedback): HAMMER panic in hammer_cursor_down()https://bugs.dragonflybsd.org/issues/17172010-04-08T09:25:15Zjosepht1
<p>I got the following panic (sorry it's just a backtrace):</p>
<p>panic: BTYPE MISMATCH L <br />Trace beginning at frame 0xdf17171c<br />panic(df171740,cee83300,df1717f4,e3903248,df171764) at panic+0x8c<br />panic(c06029f3,4c,0,e3903248,cefdf000) at panic+0x8c<br />hammer_cursor_down(df1717f4) at hammer_cursor_down+0x113<br />hammer_btree_iterate_reverse(df1717f4,df171a58,0,0,cefdf040) at<br />hammer_btree_iterate_reverse+0x1c0<br />hammer_ioc_prune(df171a58,d91c5610,dc874f00,df17195c,1) at<br />hammer_ioc_prune+0x682<br />hammer_ioctl(d91c5610,c0fc6801,dc874f00,1,d50b1050) at<br />hammer_ioctl+0x1c8<br />hammer_vop_ioctl(df171ac8,df171abc,d8797ab4,d8797ab4,d8cf32f0) at<br />hammer_vop_ioctl+0x2f<br />vop_ioctl(d8cead10,c47f3d28,c0fc6801,dc874f00,1) at vop_ioctl+0x58<br />vn_ioctl(d50f0338,c0fc6801,dc874f00,d50b1050,df171cf0) at<br />vn_ioctl+0xe0<br />mapped_ioctl(5,c0fc6801,280f0188,0,df171cf0) at mapped_ioctl+0x3e4<br />sys_ioctl(df171cf0,6,0,0,d86fa9d0) at sys_ioctl+0x17<br />syscall2(df171d40) at syscall2+0x20e<br />Xint0x80_syscall() at Xint0x80_syscall+0x36</p>
<p>I've uploaded the kern.25.gz and vmcore.25.gz to my leaf account.</p>
<p>Thanks,<br />Joe</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 #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 #1330 (Feedback): Hammer, usb disk, SYNCHRONIZE CACHE failurehttps://bugs.dragonflybsd.org/issues/13302009-04-07T20:35:05Zjosepht
<p>This is for 2.2-RELEASE. I have a 2.5" drive in an external USB<br />enclosure with one big Hammer filesystem on it. The disk is ~75GB.<br />When the daily cronjob to cleanup hammer runs it fails with these<br />errors:</p>
<p>Thanks,<br />Joe</p>
<p>Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE <abbr title="10">CACHE</abbr>. CDB: 35 0 0 0 0 0 0 0 0 0 <br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:20,0<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): Invalid command operation code<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): <br />SYNCHRONIZE <abbr title="10">CACHE</abbr>. CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:20,0<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): Invalid command operatio n code<br />Apr 6 03:02:10 jupiter kernel: Unretryable error<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): error 22<br />Apr 6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): Unretryable Error<br />Apr 6 03:02:10 jupiter kernel: <abbr title="DATA">HAMMER</abbr>: Critical error inode=-1 while flushing meta-data<br />Apr 6 03:02:10 jupiter kernel: <abbr title="DATA">HAMMER</abbr>: Forcing read-only mode<br />Apr 6 03:02:10 jupiter kernel: <abbr title="DATA">HAMMER</abbr>: Critical write error during flush, refusing to sync UNDO FIFO</p> DragonFlyBSD - Bug #979 (Feedback): Failure-prone USB mass storage (SB600? msdosfs? CAM?)https://bugs.dragonflybsd.org/issues/9792008-03-23T00:52:39Zfloid
<p>I'm still very behind when it comes to keeping track of development, so pardon<br />if this is known. I always need to do more testing, but some feedback will help<br />me narrow down the test cases.</p>
<p>Symptoms:</p>
<p>Using 1.12.0-RELEASE, copying from a FAT-formatted 2GB CF card in a reader with<br />a "Genesys" chipset hangs after the first ~82MB have been copied. A "hang" is<br />determined as iostat showing 0 throughput and cp not responding to ^C.</p>
<p>ehci.ko is <strong>not</strong> loaded, so ohci alone was involved here.</p>
<p>Hardware considerations:</p>
<p>SMP kernel (Athlon 64 x2)<br />SB600<br />The reader is part of a Mitsumi floppy combo device<br /> (A slim conventional floppy and USB card reader crammed into one 3.5" box.)</p>
<p>Relevant portion of usbdevs -v:<br />Controller /dev/usb4:<br />addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), <abbr title="0x0000">ATI</abbr>,<br />rev 1.00<br /> port 1 addr 2: full speed, power 500 mA, config 1, USB Reader(0x070e),<br />Genesys(0x05e3), rev 93.25<br /> port 2 powered</p>
<p>...</p>
<p>The following from CAM was found in dmesg. I <strong>believe</strong> this was printed before<br />I rudely pulled the card, however I cannot be sure. (Have we considered<br />timestamping dmesg yet?) There was nothing else new in dmesg.</p>
<p>(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 <br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0<br />(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed<br />(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)</p>
<p>Similarly, cp has produced some odd output, but since the card was pulled and<br />the hung cp was left sitting for 24 hours before I got around to reporting this,<br />I'm not sure what happened here. :}</p>
<p>%cd /home/floid/Photos/<br />%cp /mnt/dcim/101olymp/* .<br />cp: ./pa091308.jpg: Bad address<br />cp: ./pa091307.jpg: Bad address<br />cp: /mnt/dcim/101olymp/pa091306.jpg: Input/output error<br />cp: /mnt/dcim/101olymp/pa091303.jpg: Input/output error<br />cp: /mnt/dcim/101olymp/pa091302.jpg: Cross-device link<br />^C</p>
<p>Adding to my confusion, the Linux (Ubuntu 7.10) machine I would attempt to read<br />the card with has a similar hardware configuration (another SB600, another card<br />reader that's also Genesys Logic-based) and its own intractable problems with<br />USB in general! On review, I see that Linux ("2.6.22-14-generic <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> SMP" i686)<br />made it exactly 32MB into the card before a majority of its USB support locked<br />up. Unfortunately that's been happening whenever anyone breathes near that<br />machine, and proprietary VMWare and fglrx modules are involved, so it'll be a<br />while before I can fsck or chkdsk the filesystem structure on the CF card itself!</p>
<p>(The media should be fine, since the camera has had no complaints.)</p>
<p>===</p>
<p>Should I be suspecting the filesystem, CAM (I've noticed Peter Avalos's work on<br />CAM locking but haven't tried it yet), or the basic hardware support?</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>