DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082023-12-23T19:11:01ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3365 (New): NFSv4 ACLs for HAMMER2https://bugs.dragonflybsd.org/issues/33652023-12-23T19:11:01ZvinipsmakerDragonFlyBSD - Bug #3364 (New): aio_read2() and aio_write2()https://bugs.dragonflybsd.org/issues/33642023-12-23T19:09:19Zvinipsmaker
<p>I'd like to use AIO to read files w/o specifying an offset in the member aio_offset. Instead, I'd like for the current file offset to be used. For Linux, io_uring supports using -1 for the offset to indicate that the current file position should be used instead of passing in an explicit offset. I'd like to do the same on DragonFly BSD.</p>
<p>I propose the following interface:</p>
<p>int aio_read2(struct aiocb *iocb, unsigned flags);<br />int aio_write2(struct aiocb *iocb, unsigned flags);</p>
<p>aio_read(iocb) would be equivalent to aio_read2(iocb, 0) and aio_write(iocb) would be equivalent to aio_write2(iocb, 0).</p>
<p>Then we would define the following flags:</p>
<p>AIO_IGNOREOFFSET</p>
<p>The flag AIO_IGNOREOFFSET would instruct the call to ignore aio_offset in aiocb and use the file position (lseek) if applicable. The flag AIO_IGNOREOFFSET should not conflict with LIO opcodes so one could OR it into aio_lio_opcode for usage with lio_listio() as well. I think that should be enough to close all ties.</p> DragonFlyBSD - Bug #3363 (New): sysctl CTL_NET.PF_ROUTE.0.0.NET_RT_IFLIST.0 blocks in an uninterr...https://bugs.dragonflybsd.org/issues/33632023-12-22T07:11:53Zguy
<p>The attached program blocks, reliably, in an uninterruptible wait on my DragonFly BSD 6.4 VM if I run it and then:</p>
<p>plug in a USB Wi-FI interface and tell VMware Fusion to attach it to the running VM;</p>
<p>wait for the interface to be attached and to be recognized by the program;</p>
<p>unplug the interface.</p>
<p>It hands in my_getifaddrs() (which is a copy of the DFly BSD getifaddrs()) when it's called after the program receives an RTM_IFINFO message. The hang is in the first sysctl() it does in the loop.</p>
<p>The RTM_IFINFO message is indicating that the carrier state of the removed interface is unknown; after that, an RTM_IFANNOUNCE message is received, indicating that the interface in question was removed, and then <strong>another</strong> RTM_IFINFO message, for the same interface, is received, again indicating that the carrier state is unknown.</p>
<p>I suspect this will happen on real hardware as well. It may also occur for, for example, Ethernet interfaces, and interfaces on pluggable-at-run-time buses other than USB.</p> DragonFlyBSD - Submit #3362 (New): Reduce package dependencies of sysutils/cdrtools in branch wit...https://bugs.dragonflybsd.org/issues/33622023-12-05T04:09:21Zmneumann
<p>Git branch withpkg.</p>
<p>Build `sysutils/cdrtools` without options DOCS, LAME and VORBIS. This should get rid of various dependent packages in `dports.base`.<br />We only need cdrtools for mkisofs, not for burning audio cds...</p> DragonFlyBSD - Bug #3361 (New): newlocale()/freelocale() leak https://bugs.dragonflybsd.org/issues/33612023-11-16T01:24:12Ztonyc
<p>The attached code shows the combination of newlocale() to create a new locale object and freelocale() to free that object leaks memory.<br /><code>$ ./newlocale_loop<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 4 178 0 4124 680 wait S0+ 0 0:00.00 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 7.63G 416616 wait S1+ 0 0:05.37 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 15.26G 832272 wait S1+ 0 0:09.62 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 22.89G 1.19G wait S1+ 0 0:12.80 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 30.52G 1.58G wait S1+ 0 0:17.34 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 38.15G 1.98G wait S1+ 0 0:18.68 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 45.78G 2.37G wait S1+ 0 0:23.65 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 53.41G 2.77G wait S1+ 0 0:26.65 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 61.04G 3.17G wait S1+ 0 0:30.35 ./n<br /> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND<br /> 1001 825 822 80 254 0 68.67G 3.56G wait S1+ 0 0:35.02 ./n<br /></code></p>
<p>Note RSS going from 680 to 3.56G</p>
<p>Building and running the same code on Linux (Debian bookworm) and Freebsd 15-CURRENT does not leak in the same way.</p> DragonFlyBSD - Bug #3359 (New): Too many zlibhttps://bugs.dragonflybsd.org/issues/33592023-10-18T04:21:25Ztkusumikusumi.tomohiro@gmail.com
<p>Recently added hammer2(8) recover directive has added yet another zlib to HAMMER2, this time in userspace.<br />This is a third copy of zlib in HAMMER2 related source.<br />Why not just use contrib/zlib-1.2, or if not possible why ?</p>
<p>hammer2(8) recover directive has also added a userspace copy of LZ4.<br />This one can easily reuse sys/vfs/hammer2/*lz4*.<br />All we need is a few KERNEL ifdefs around malloc/free related and header includes.</p> DragonFlyBSD - Submit #3355 (New): [PATCH] Port ext4 extents support from FreeBSDhttps://bugs.dragonflybsd.org/issues/33552023-08-23T03:03:33ZphcoderDragonFlyBSD - Bug #3353 (New): [panic] 'hammer2 pfs-create -t master' causes kernel panichttps://bugs.dragonflybsd.org/issues/33532023-06-25T01:52:18Zliweitianuxliweitianux@live.com
<p>liuyb1 on IRC reported on 2023-06-20 the following HAMMER2 PFS panic.</p>
<p>Reproduce steps:</p>
<pre><code class="shell syntaxhl" data-language="shell"><span class="nv">$ </span>hammer2 snapshot / snap-1
<span class="nv">$ </span>hammer2 <span class="nt">-u</span> <span class="sb">`</span>hammer2 pfs-clid snap-1<span class="sb">`</span> pfs-create snap-slave
<span class="nv">$ </span>hammer2 <span class="nt">-t</span> master <span class="nt">-u</span> <span class="sb">`</span>hammer2 pfs-clid snap-1<span class="sb">`</span> pfs-create snap-master
</code></pre>
<p>Kernel panic trace:</p>
<pre>
panic with 1 spinlocks held
panic: hammer2_chain_insert: collision 0xfffff8011e688a40 0xfffff8011e694580 (key=0000000000000400)
cpuid = 1
Trace beginning at frame 0xfffff80097df6a90
hammer2_chain_insert() at hammer2_chain_insert+0x15b 0xffffffff8096ca7b
hammer2_chain_insert() at hammer2_chain_insert+0x15b 0xffffffff8096ca7b
hammer2_chain_create() at hammer2_chain_create+0xded 0xffffffff809734ed
hammer2_chain_rename() at hammer2_chain_rename+0xd1 0xffffffff809740c1
hammer2_chain_rename_obref() at hammer2_chain_rename_obref+0x20 0xffffffff809741d0
hammer2_chain_indirect_maintenance() at hammer2_chain_indirect_maintenance+0x421 0xffffffff809746b1
</pre>
<p>Although the above PFS clustering commands are documented in the hammer2(8) man page, the clustering feature is actually still in early development phase, as per the <a href="https://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys/vfs/hammer2/DESIGN#l27" class="external">DESIGN</a> doc. So issues are expected and panic is quite possible.</p>
<p>Well, it should report the functionality is not implemented rather than panic the system.</p> DragonFlyBSD - Bug #3352 (New): HAMMER2 ioctl(HAMMER2IOC_DESTROY) is brokenhttps://bugs.dragonflybsd.org/issues/33522023-06-21T08:29:16Ztkusumikusumi.tomohiro@gmail.com
<p>1. hammer2(8) destroy directive - This succeeds with "ok" message, but after unmount + mount, the same file is still there.</p>
<p>The reason is because it currently just unlinks dirent chain from parent directory (ip) chain,<br />and returns without modifying parent directory which can cause flusher to flush.<br />Both VOP_NREMOVE and VOP_NRMDIR modify dip, but this one does not.</p>
<pre><code class="shell syntaxhl" data-language="shell"><span class="c"># mount_hammer2 /dev/vn0 /mnt</span>
<span class="c"># hammer2 destroy /mnt/src/Makefile</span>
/mnt/src/Makefile ok
<span class="c"># hammer2 destroy /mnt/src/Makefile</span>
/mnt/src/Makefile No such file or directory
<span class="c"># umount /mnt</span>
<span class="c"># mount_hammer2 /dev/vn0 /mnt</span>
<span class="c"># hammer2 destroy /mnt/src/Makefile</span>
/mnt/src/Makefile ok
<span class="c"># hammer2 destroy /mnt/src/Makefile</span>
/mnt/src/Makefile No such file or directory
</code></pre>
<p>2. hammer2(8) destroy-inum directive - This simply fails. It seems hammer2_chain_lookup() can't find the chain via inode number.</p>
<pre><code class="shell syntaxhl" data-language="shell"><span class="c"># mount_hammer2 /dev/vn0 /mnt</span>
<span class="c"># ls -li /mnt/src/README</span>
1104 <span class="nt">-rw-r--r--</span> 1 root wheel 10989 Jun 21 00:58 /mnt/src/README
<span class="c"># hammer2 -s /mnt destroy-inum 1104</span>
deleting inodes on /mnt
1104 No such file or directory
<span class="c"># hammer2 -s /mnt destroy-inum 0x450</span>
deleting inodes on /mnt
1104 No such file or directory
</code></pre> DragonFlyBSD - Bug #3351 (New): XDM and GDM3 display manager under DragonFlyBSD 6.4: After starti...https://bugs.dragonflybsd.org/issues/33512023-06-17T15:22:07Zadrian
<p>Dear Maintainer,</p>
<p>currently under DragonFlyBSD 6.4 and with up-to-date packages from pkg package manager, XDM and GDM3 fail to load correctly.</p>
<p>I am able to start a local Xorg session running CTWM with the 'startx' commando. This works!</p>
<p>So the Xorg configuration works. With the same settings, XDM worked under DragonFlyBSD 6.2.</p>
<p>I am running DragonFlyBSD 6.4 as VM under a Debian Linux/testing KVM/qemu host.</p>
<p>Thank you very much in advance.</p>
<p>Sincerely,</p>
<p>Adrian Kieß</p> DragonFlyBSD - Bug #3350 (New): tmux: Terminfo file usr/share/terminfo/t/tmux-256color does not w...https://bugs.dragonflybsd.org/issues/33502023-06-17T07:43:41Zadrian
<p>Dear Maintainer,</p>
<p>the terminfo file /usr/share/terminfo/t/tmux-256color does not work correctly, when logging into DragonFlyBSD from a remote tmux session.</p>
<p>Running:</p>
<p>export TERM=xterm-256color</p>
<p>after logging in, fixes the broken terminal.</p>
<p>I am using:</p>
<p>root@dragonflybsd /home/adrian
# uname -a <br />DragonFly dragonflybsd.v-zone.lan.dac 6.4-RELEASE DragonFly v6.4.0.26.g43e53c-RELEASE <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>: Mon Mar 13 12:12:53 CET 2023 <a class="email" href="mailto:adrian@dragonflybsd.v-zone.lan.dac">adrian@dragonflybsd.v-zone.lan.dac</a>:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64</p>
<p>Thanks a lot in advance.</p>
<p>Sincerely,</p>
<p>Adrian Kieß</p> DragonFlyBSD - Bug #3345 (In Progress): amdgpu crashes when loaded on Ryzen 5 PRO 3500Uhttps://bugs.dragonflybsd.org/issues/33452023-02-12T13:39:26Zdaftaupepierre-alain@toret.fr
<p>Hi,</p>
<p>I tried to load amdgpu on a HP laptop with a Ryzen 5 PRO 3500U.<br />Linux reports it as PCI_ID=1002:15D8 which seems to be supported according to <a class="external" href="https://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys/dev/drm/amd/amdgpu/amdgpu_drv.c#l788">https://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys/dev/drm/amd/amdgpu/amdgpu_drv.c#l788</a></p>
<p>Though, after installing devfw-amdgpu and trying to load amdgpu I get the following trace and the system ends up on a black screen.<br /><pre><code class="shell syntaxhl" data-language="shell"><span class="o">[</span>drm] amdgpu kernel modesetting enabled.
drm0 on vgapci0
<span class="o">[</span>drm] pdev: <span class="nv">vendor</span><span class="o">=</span>0x1002 <span class="nv">device</span><span class="o">=</span>0x15d8 <span class="nv">rev</span><span class="o">=</span>0xd2
<span class="o">[</span>drm] <span class="nv">svendor</span><span class="o">=</span>0x103c <span class="nv">sdevice</span><span class="o">=</span>0x8589 <span class="nv">irq</span><span class="o">=</span>17
vgapci0: child drm0 requested pci_enable_io
vgapci0: child drm0 requested pci_enable_io
amdgpu_driver_load_kms<span class="o">()</span>: <span class="nv">flags</span><span class="o">=</span>131094 <span class="nv">drm_device</span><span class="o">=</span>0xfffff801564f4500 <span class="nv">adev</span><span class="o">=</span>0xfffff80364ac8000
amdgpu_device_init: start
<span class="o">[</span>drm] initializing kernel modesetting <span class="o">(</span>RAVEN 0x1002:0x15D8 0x103C:0x8589 0xD2<span class="o">)</span><span class="nb">.</span>
amdgpu_device_init: 1
<span class="o">[</span>drm] register mmio base: 0xF0600000
<span class="o">[</span>drm] register mmio size: 524288
pci_resource_flags: <span class="nv">pdev</span><span class="o">=</span>0xfffff8015646e800 <span class="nv">bar</span><span class="o">=</span>2 <span class="nb">type</span><span class="o">=</span>MEM
amdgpu_device_init: 2
amdgpu_device_init: <span class="k">for </span>loop 0
amdgpu_device_init: <span class="k">for </span>loop 1
amdgpu_device_init: <span class="k">for </span>loop 2
amdgpu_device_init: <span class="k">for </span>loop 3
amdgpu_device_init: <span class="k">for </span>loop 4
amdgpu_device_init: <span class="nv">rio_rid</span><span class="o">=</span>32
amdgpu_device_init: <span class="nv">mem_size</span><span class="o">=</span>256
amdgpu_device_init: 3
<span class="o">[</span>drm] add ip block number 0 <soc15_common>
<span class="o">[</span>drm] add ip block number 1 <gmc_v9_0>
<span class="o">[</span>drm] add ip block number 2 <vega10_ih>
<span class="o">[</span>drm] add ip block number 3 <psp>
<span class="o">[</span>drm] add ip block number 4 <powerplay>
<span class="o">[</span>drm] add ip block number 5 <dm>
<span class="o">[</span>drm] add ip block number 6 <gfx_v9_0>
<span class="o">[</span>drm] add ip block number 7 <sdma_v4_0>
<span class="o">[</span>drm] add ip block number 8 <vcn_v1_0>
<span class="o">[</span>drm] VCN decode is enabled <span class="k">in </span>VM mode
<span class="o">[</span>drm] VCN encode is enabled <span class="k">in </span>VM mode
<span class="o">[</span>drm] VCN jpeg decode is enabled <span class="k">in </span>VM mode
amdgpu_device_init: 4
amdgpu_device_init: 5
ATOM BIOS: SWBRT48929.001
amdgpu_device_init: 6
amdgpu_device_init: 6.1
amdgpu_device_init: 7
amdgpu_device_init: 8
<span class="o">[</span>drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
amdgpu: No suitable DMA available.
amdgpu: No coherent DMA available.
drm0: info: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF <span class="o">(</span>512M used<span class="o">)</span>
drm0: info: GART: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF
<span class="o">[</span>drm] Detected VRAM <span class="nv">RAM</span><span class="o">=</span>512M, <span class="nv">BAR</span><span class="o">=</span>256M
<span class="o">[</span>drm] RAM width 128bits DDR4
<span class="o">[</span>TTM] Zone kernel: Available graphics memory: 65536 kiB
<span class="o">[</span>TTM] Zone dma32: Available graphics memory: 65536 kiB
<span class="o">[</span>TTM] Initializing pool allocator
<span class="o">[</span>drm] amdgpu: 512M of VRAM memory ready
<span class="o">[</span>drm] amdgpu: 3072M of GTT memory ready.
<span class="o">[</span>drm] GART: num cpu pages 262144, num gpu pages 262144
<span class="o">[</span>drm] PCIE GART of 1024M enabled <span class="o">(</span>table at 0x000000F404000000<span class="o">)</span><span class="nb">.</span>
ttm_check_under_lowerlimit: stub
amdgpu: <span class="o">[</span>powerplay] powerplay sw init successfully
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 0 use gpu addr 0x000000f500400040, cpu addr 0x0xffffb80000101040
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 1 use gpu addr 0x000000f5004000c0, cpu addr 0x0xffffb800001010c0
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 2 use gpu addr 0x000000f500400140, cpu addr 0x0xffffb80000101140
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 3 use gpu addr 0x000000f5004001c0, cpu addr 0x0xffffb800001011c0
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 4 use gpu addr 0x000000f500400240, cpu addr 0x0xffffb80000101240
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 5 use gpu addr 0x000000f5004002c0, cpu addr 0x0xffffb800001012c0
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 6 use gpu addr 0x000000f500400340, cpu addr 0x0xffffb80000101340
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 7 use gpu addr 0x000000f5004003c0, cpu addr 0x0xffffb800001013c0
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 8 use gpu addr 0x000000f500400440, cpu addr 0x0xffffb80000101440
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 9 use gpu addr 0x000000f5004004e0, cpu addr 0x0xffffb800001014e0
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
<span class="o">[</span>drm] use_doorbell being <span class="nb">set </span>to: <span class="o">[</span><span class="nb">true</span><span class="o">]</span>
drm0: debug: fence driver on ring 10 use gpu addr 0x000000f500400560, cpu addr 0x0xffffb80000101560
ttm_check_under_lowerlimit: stub
<span class="o">[</span>drm] Found VCN firmware Version: 1.73 Family ID: 18
<span class="o">[</span>drm] PSP loading VCN firmware
drm0: debug: fence driver on ring 11 use gpu addr 0x000000f5004005e0, cpu addr 0x0xffffb800001015e0
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 12 use gpu addr 0x000000f500400660, cpu addr 0x0xffffb80000101660
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 13 use gpu addr 0x000000f5004006e0, cpu addr 0x0xffffb800001016e0
ttm_check_under_lowerlimit: stub
drm0: debug: fence driver on ring 14 use gpu addr 0x000000f500400760, cpu addr 0x0xffffb80000101760
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
ttm_check_under_lowerlimit: stub
amdgpu: <span class="o">[</span>powerplay] dpm has been enabled
<span class="o">[</span>drm] DM_PPLIB: values <span class="k">for </span>Invalid clock
<span class="o">[</span>drm] DM_PPLIB: 400000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: 933000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: 1067000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: 1200000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: values <span class="k">for </span>Invalid clock
<span class="o">[</span>drm] DM_PPLIB: 300000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: 600000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: 626000 <span class="k">in </span>kHz
<span class="o">[</span>drm] DM_PPLIB: 654000 <span class="k">in </span>kHz
<span class="o">[</span>drm] Display Core initialized with v3.1.59!
tunable drm.video.eDP-1 is not <span class="nb">set</span>
<span class="o">[</span>drm] SADs count is: <span class="nt">-2</span>, don<span class="s1">'t need to read it
tunable drm.video.DP-1 is not set
tunable drm.video.DP-2 is not set
tunable drm.video.DP-3 is not set
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
drm0: error: [gfxhub] VMC page fault (src_id:0 ring:217 vmid:0 pasid:0, for process pid 0 thread pid 0
)
drm0: error: at address 0x0000000000000000 from 27
drm0: error: VM_L2_PROTECTION_FAULT_STATUS:0x00000BB2
drm0: error: [gfxhub] VMC page fault (src_id:0 ring:217 vmid:0 pasid:0, for process pid 0 thread pid 0
)
drm0: error: at address 0x0000000000001000 from 27
drm0: error: VM_L2_PROTECTION_FAULT_STATUS:0x00000BB2
error: [drm:pid759:gfx_v9_0_kiq_kcq_enable] *ERROR* KCQ enable failed (scratch(0xC040)=0xCAFEDEAD)
error: [drm:pid759:amdgpu_device_ip_init] *ERROR* hw_init of IP block <gfx_v9_0> failed -22
drm0: error: amdgpu_device_ip_init failed
drm0: error: Fatal error during GPU init
[drm] amdgpu: finishing device.
amdgpu_device_ip_fini: 1
</span></code></pre></p>
<p>The crash is consistently reproduced and I discovered it's in fact a db prompt, so I got a dump which I have uploaded in my leaf account : /build/home/daftaupe/crash/amdgpu_crash together with that trace, dmesg output and pciconf output.<br />If anything more is needed, just ask.</p> DragonFlyBSD - Bug #3311 (New): TrueCrypt support may cause kernel crashhttps://bugs.dragonflybsd.org/issues/33112022-01-30T10:33:08Zarcade@b1t.namearcade@b1t.name
<p>When working on tcplay:hammer2 device kernel can crash. Screenshots attached...</p> DragonFlyBSD - Bug #3302 (New): Will not boot on System76 Lemur Pro (lemp10)https://bugs.dragonflybsd.org/issues/33022021-11-03T17:21:41Zpiecuch
<p>I booted a nightly img from 2020-10-18 off an USB2.0 stick, the port is USB3.1.</p>
<p>Please let me know if there are more details I can give or test something.</p> DragonFlyBSD - Submit #3206 (In Progress): update psm/kbd to FreeBSD 12.0 codehttps://bugs.dragonflybsd.org/issues/32062019-09-19T19:21:35Zhtseharald.brinkhof@gmail.com
<p>updates code to this FreeBSD commit</p>
<p>commit 11b574d82f92a010ea507fe962cec39e38954c3a<br />Author: philip <<a class="email" href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>><br />Date: Sun Jun 16 03:06:05 2019 +0000</p>
<pre><code>Add macOS-like three finger drag trackpad gesture to psm(4)</code></pre>
<p>Adds three-fingered drag, natural scrolling, a bunch of bugfixes, 4-5 finger support, ...</p>