Re: String of emojis and IRC color codes crashes tmux
On 2024/01/23 23:12, Luiz de Milon wrote:
> To: bugs@openbsd.org
> Subject: String of emojis and IRC color codes crashes tmux
> From: hiriga...@riseup.net
> Cc: hiriga...@riseup.net
> Reply-To: hiriga...@riseup.net
>
> >Synopsis: String of emojis and IRC color codes crashes
> tmux (and has issues with ncurses)
> >Category: library
> >Environment:
> System : OpenBSD 7.4
> Details : OpenBSD 7.4 (GENERIC.MP) #1396: Sun Oct 8
> 09:20:40 MDT 2023
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> Architecture: OpenBSD.amd64
> Machine : amd64
> >Description:
> When the following file is `cat`ed in tmux, the server
> crashes. This also messes up the rendering in weechat, so I
> believe the bug may be in ncurses rather than tmux.
That seems likely - I can reproduce it in 7.4 but not -current (which
has newer curses).
> ~ $ hexdump -C this-crashes
> f0 9f 87 a8 f0 9f 87 b2 f0 9f 87 b6 f0 9f 87
> af ||
> 0010 f0 9f 87 b2 f0 9f 87 a7 0a |.|
> 0019
> ~ $ hexdump -C this-does-not
> f0 9f 87 b2 f0 9f 87 b6 f0 9f 87 af f0 9f 87
> b2 ||
> 0010 f0 9f 87 a7 0a |.|
> 0015
Here's a uuencoded version to make it easier if someone else wants to
replicate.
begin 644 this-crashes
9\)^'J/"?A[+PGX>V\)^'K_"?A[+PGX>G"@``
`
end
> Here's a ktrace output of the server, up to the crash. I
> input `cat this-crashes` and pressed enter, and then
> tmux exited with "server exited unexpectedly" and after
> that, i have to `reset` because my terminal stops behaving
> correctly. (it seems like it gets fixed to a certain length,
> i get long lines ending with % after it crashes, after any
> command, such as ls. ls -l also does not align properly,
> etc. etc.)
>
>
> 23866 tmux STRU struct kevent { ident=5,
> filter=EVFILT_READ, flags=0x1, fflags=0<>, data=1,
> udata=0xd88d19387b8 }
> 23866 tmux RET kevent 1
> 23866 tmux CALL clock_gettime(CLOCK_MONOTONIC,0x7c8f3fea64e0)
> 23866 tmux STRU struct timespec { 2158618.909373185 }
> 23866 tmux RET clock_gettime 0
> 23866 tmux CALL ioctl(5,FIONREAD,0x7c8f3fea641c)
> 23866 tmux RET ioctl 0
> 23866 tmux CALL read(5,0xd88c139aa00,0x1)
> 23866 tmux GIO fd 5 read 1 bytes
> "c"
> 23866 tmux RET read 1
> 23866 tmux CALL gettimeofday(0x7c8f3fea64d0,0)
> 23866 tmux STRU struct timeval { 1706063732<"Jan 24
> 02:35:32 2024">.173102 }
> 23866 tmux RET gettimeofday 0
> 23866 tmux CALL gettimeofday(0x7c8f3fea6410,0)
> 23866 tmux STRU struct timeval { 1706063732<"Jan 24
> 02:35:32 2024">.173107 }
> 23866 tmux RET gettimeofday 0
> 23866 tmux CALL gettimeofday(0xd88d19385f0,0)
> 23866 tmux STRU struct timeval { 1706063732<"Jan 24
> 02:35:32 2024">.173112 }
> 23866 tmux RET gettimeofday 0
> 23866 tmux CALL kbind(0x7c8f3fea61b8,24,0xdcc9ee19dd2aa3fc)
> 23866 tmux RET kbind 0
> 23866 tmux CALL kbind(0x7c8f3fea6178,24,0xdcc9ee19dd2aa3fc)
> 23866 tmux RET kbind 0
> 23866 tmux CALL clock_gettime(CLOCK_MONOTONIC,0x7c8f3fea64e0)
> 23866 tmux STRU struct timespec { 2158618.909505995 }
> 23866 tmux RET clock_gettime 0
> 23866 tmux CALL clock_gettime(CLOCK_MONOTONIC,0x7c8f3fea64e0)
> 23866 tmux STRU struct timespec { 2158618.909509964 }
> 23866 tmux RET clock_gettime 0
> 23866 tmux CALL
> kevent(4,0xd88c1389000,1,0xd88c1376800,64,0x7c8f3fea6438)
> 23866 tmux STRU struct timespec { 10.790533000 }
> 23866 tmux STRU struct kevent { ident=8,
> filter=EVFILT_WRITE, flags=0x11,
> fflags=0<>, data=0, udata=0xd88a5e6b508 }
> 23866 tmux STRU struct kevent { ident=8,
> filter=EVFILT_WRITE, flags=0x11,
> fflags=0<>, data=8192, udata=0xd88a5e6b508 }
> 23866 tmux RET kevent 1
> 23866 tmux CALL clock_gettime(CLOCK_MONOTONIC,0x7c8f3fea64e0)
> 23866 tmux STRU struct timespec { 2158618.909524839 }
> 23866 tmux RET clock_gettime 0
> 23866 tmux CALL kbind(0x7c8f3fea6398,24,0xdcc9ee19dd2aa3fc)
> 23866 tmux RET kbind 0
> 23866 tmux CALL write(8,0xd88c139a300,0x1)
> 23866 tmux GIO fd 8 wrote 1 bytes
> "c"
> 23866 tmux RET write 1
> 23866 tmux CALL gettimeofday(0x7c8f3fea64d0,0)
> 23866 tmux STRU struct timeval { 1706063732<"Jan 24
> 02:35:32 2024">.173576 }
> 23866 tmux RET gettimeofday 0
> 23866 tmux CALL clock_gettime(CLOCK_MONOTONIC,0x7c8f3fea64e0)
> 23866 tmux STRU struct timespec { 2158618.909899176 }
> 23866 tmux RET clock_gettime 0
> 23866 tmux CALL clock_gettime(CLOCK_MONOTONIC,0x7c8f3fea64e0)
> 23866 tmux STRU struct timespec { 2158618.909904195 }
> 23866 tmux RET clock_gettime 0
> 23866 tmux CALL kevent(4,0,0,0xd88c1376800,64,0x7c8f3fea6438)
> 23866 tmux STRU struct timespec { 10.790139000 }
> 23866 tmux STRU
Re: Unable to boot -current without disabling amdgpu
On Wed, Jan 24, 2024 at 09:46:41PM +1100, Jonathan Gray wrote:
> On Tue, Jan 23, 2024 at 10:55:26AM -0500, Josh Rickmar wrote:
> > Latest -current is unhappy with my amd64 desktop. I'm assuming this
> > is due to the recent drm sync to newer Linux. My GPU is a RX Vega 64.
>
> An earlier snapshot worked?
Yes, however the monitor would briefly go into power saving mode from
not having a display signal for a short while, and when it displayed
again, the console had color stripes. These would disappear once
xenodm was loaded, and switching back to the console would not show
the color striping again.
>
> >
> > It seems to kernel panic but I can't confirm this, the screen is black
> > and it doesn't bring up networking/respond to pings.
> >
> > I see the following errors in the dmesg buffer before the most recent
> > boot:
> >
> > amdgpu0: VEGA10 GC 9.0.1 64 CU rev 0x01
> > [drm] *ERROR* IB test failed on gfx_low (-60).
> > [drm] *ERROR* IB test failed on gfx_high (-60).
> > [drm] *ERROR* IB test failed on comp_1.0.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.1.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.2.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.3.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.0.1 (-60).
> > [drm] *ERROR* IB test failed on comp_1.1.1 (-60).
> > [drm] *ERROR* IB test failed on comp_1.2.1 (-60).
>
> Does the following change this?
>
> The framebuffer offset/size can cause tests to fail.
>
Unfortunately not, I see the same behavior and errors in dmesg as
before.
> Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c
> ===
> RCS file: /cvs/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c,v
> diff -u -p -r1.11 amdgpu_gmc.c
> --- sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 16 Jan 2024 23:37:52 -
> 1.11
> +++ sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 24 Jan 2024 10:07:49 -
> @@ -738,15 +738,6 @@ void amdgpu_gmc_get_vbios_allocations(st
> } else {
> size = amdgpu_gmc_get_vbios_fb_size(adev);
>
> -#ifdef __amd64__
> - /*
> - * XXX Workaround for machines where the framebuffer
> - * size reported by the hardware is incorrect.
> - */
> - extern psize_t efifb_stolen();
> - size = max(size, efifb_stolen());
> -#endif
> -
> if (adev->mman.keep_stolen_vga_memory)
> size = max(size, (unsigned)AMDGPU_VBIOS_VGA_ALLOCATION);
> }
Re: Unable to boot -current without disabling amdgpu
On Wed, Jan 24, 2024 at 12:54:03PM -0400, Jos?? Maldonado wrote:
> El mar, 23 ene 2024 a la(s) 1:08???p.m., Josh Rickmar (jr...@zettaport.com)
> escribi??:
> >
> > On Tue, Jan 23, 2024 at 10:55:26AM -0500, Josh Rickmar wrote:
> > > Latest -current is unhappy with my amd64 desktop. I'm assuming this
> > > is due to the recent drm sync to newer Linux. My GPU is a RX Vega 64.
> > >
> > > It seems to kernel panic but I can't confirm this, the screen is black
> > > and it doesn't bring up networking/respond to pings.
> > >
> > > I see the following errors in the dmesg buffer before the most recent
> > > boot:
> > >
> > > amdgpu0: VEGA10 GC 9.0.1 64 CU rev 0x01
> > > [drm] *ERROR* IB test failed on gfx_low (-60).
> > > [drm] *ERROR* IB test failed on gfx_high (-60).
> > > [drm] *ERROR* IB test failed on comp_1.0.0 (-60).
> > > [drm] *ERROR* IB test failed on comp_1.1.0 (-60).
> > > [drm] *ERROR* IB test failed on comp_1.2.0 (-60).
> > > [drm] *ERROR* IB test failed on comp_1.3.0 (-60).
> > > [drm] *ERROR* IB test failed on comp_1.0.1 (-60).
> > > [drm] *ERROR* IB test failed on comp_1.1.1 (-60).
> > > [drm] *ERROR* IB test failed on comp_1.2.1 (-60).
> >
> > I also see a bit more from the panicking dmesg boot above this:
> >
> > amdgpu0 at pci9 dev 0 function 0 "ATI Radeon Rx Vega" rev 0xc1
> > drm0 at amdgpu0
> > amdgpu_acpi_enumerate_xcc: stub
> > amdgpu0: msi
> >
> > Which comes from:
> >
> > static int amdgpu_acpi_enumerate_xcc(void)
> > {
> > STUB();
> > return -ENOSYS;
> > #ifdef notyet
> > <...>
> > #endif
> > }
> >
> > Not familiar enough to understand if this is part of the problem, but
> > thought it was worth adding to the bug report.
> >
>
> Hi, right now I'm using -current OpenBSD 7.4 GENERIC.MP#1622 amd64 with
> amdgpu and not problems with new drm code.
>
> ??Firmware update, maybe?
I've got the latest firmware.
Re: Unable to boot -current without disabling amdgpu
I may have stumbled upon a fix by accident. Enabling resizable BAR in
my UEFI settings seems to stop the crash.
On Wed, Jan 24, 2024 at 09:46:41PM +1100, Jonathan Gray wrote:
> On Tue, Jan 23, 2024 at 10:55:26AM -0500, Josh Rickmar wrote:
> > Latest -current is unhappy with my amd64 desktop. I'm assuming this
> > is due to the recent drm sync to newer Linux. My GPU is a RX Vega 64.
>
> An earlier snapshot worked?
>
> >
> > It seems to kernel panic but I can't confirm this, the screen is black
> > and it doesn't bring up networking/respond to pings.
> >
> > I see the following errors in the dmesg buffer before the most recent
> > boot:
> >
> > amdgpu0: VEGA10 GC 9.0.1 64 CU rev 0x01
> > [drm] *ERROR* IB test failed on gfx_low (-60).
> > [drm] *ERROR* IB test failed on gfx_high (-60).
> > [drm] *ERROR* IB test failed on comp_1.0.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.1.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.2.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.3.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.0.1 (-60).
> > [drm] *ERROR* IB test failed on comp_1.1.1 (-60).
> > [drm] *ERROR* IB test failed on comp_1.2.1 (-60).
>
> Does the following change this?
>
> The framebuffer offset/size can cause tests to fail.
>
> Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c
> ===
> RCS file: /cvs/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c,v
> diff -u -p -r1.11 amdgpu_gmc.c
> --- sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 16 Jan 2024 23:37:52 -
> 1.11
> +++ sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 24 Jan 2024 10:07:49 -
> @@ -738,15 +738,6 @@ void amdgpu_gmc_get_vbios_allocations(st
> } else {
> size = amdgpu_gmc_get_vbios_fb_size(adev);
>
> -#ifdef __amd64__
> - /*
> - * XXX Workaround for machines where the framebuffer
> - * size reported by the hardware is incorrect.
> - */
> - extern psize_t efifb_stolen();
> - size = max(size, efifb_stolen());
> -#endif
> -
> if (adev->mman.keep_stolen_vga_memory)
> size = max(size, (unsigned)AMDGPU_VBIOS_VGA_ALLOCATION);
> }
>
Re: Unable to boot -current without disabling amdgpu
El mar, 23 ene 2024 a la(s) 1:08 p.m., Josh Rickmar (jr...@zettaport.com)
escribió:
>
> On Tue, Jan 23, 2024 at 10:55:26AM -0500, Josh Rickmar wrote:
> > Latest -current is unhappy with my amd64 desktop. I'm assuming this
> > is due to the recent drm sync to newer Linux. My GPU is a RX Vega 64.
> >
> > It seems to kernel panic but I can't confirm this, the screen is black
> > and it doesn't bring up networking/respond to pings.
> >
> > I see the following errors in the dmesg buffer before the most recent
> > boot:
> >
> > amdgpu0: VEGA10 GC 9.0.1 64 CU rev 0x01
> > [drm] *ERROR* IB test failed on gfx_low (-60).
> > [drm] *ERROR* IB test failed on gfx_high (-60).
> > [drm] *ERROR* IB test failed on comp_1.0.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.1.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.2.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.3.0 (-60).
> > [drm] *ERROR* IB test failed on comp_1.0.1 (-60).
> > [drm] *ERROR* IB test failed on comp_1.1.1 (-60).
> > [drm] *ERROR* IB test failed on comp_1.2.1 (-60).
>
> I also see a bit more from the panicking dmesg boot above this:
>
> amdgpu0 at pci9 dev 0 function 0 "ATI Radeon Rx Vega" rev 0xc1
> drm0 at amdgpu0
> amdgpu_acpi_enumerate_xcc: stub
> amdgpu0: msi
>
> Which comes from:
>
> static int amdgpu_acpi_enumerate_xcc(void)
> {
> STUB();
> return -ENOSYS;
> #ifdef notyet
> <...>
> #endif
> }
>
> Not familiar enough to understand if this is part of the problem, but
> thought it was worth adding to the bug report.
>
Hi, right now I'm using -current OpenBSD 7.4 GENERIC.MP#1622 amd64 with
amdgpu and not problems with new drm code.
¿Firmware update, maybe?
Re: Unable to boot -current without disabling amdgpu
On Tue, Jan 23, 2024 at 10:55:26AM -0500, Josh Rickmar wrote:
> Latest -current is unhappy with my amd64 desktop. I'm assuming this
> is due to the recent drm sync to newer Linux. My GPU is a RX Vega 64.
An earlier snapshot worked?
>
> It seems to kernel panic but I can't confirm this, the screen is black
> and it doesn't bring up networking/respond to pings.
>
> I see the following errors in the dmesg buffer before the most recent
> boot:
>
> amdgpu0: VEGA10 GC 9.0.1 64 CU rev 0x01
> [drm] *ERROR* IB test failed on gfx_low (-60).
> [drm] *ERROR* IB test failed on gfx_high (-60).
> [drm] *ERROR* IB test failed on comp_1.0.0 (-60).
> [drm] *ERROR* IB test failed on comp_1.1.0 (-60).
> [drm] *ERROR* IB test failed on comp_1.2.0 (-60).
> [drm] *ERROR* IB test failed on comp_1.3.0 (-60).
> [drm] *ERROR* IB test failed on comp_1.0.1 (-60).
> [drm] *ERROR* IB test failed on comp_1.1.1 (-60).
> [drm] *ERROR* IB test failed on comp_1.2.1 (-60).
Does the following change this?
The framebuffer offset/size can cause tests to fail.
Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c
===
RCS file: /cvs/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c,v
diff -u -p -r1.11 amdgpu_gmc.c
--- sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 16 Jan 2024 23:37:52 -
1.11
+++ sys/dev/pci/drm/amd/amdgpu/amdgpu_gmc.c 24 Jan 2024 10:07:49 -
@@ -738,15 +738,6 @@ void amdgpu_gmc_get_vbios_allocations(st
} else {
size = amdgpu_gmc_get_vbios_fb_size(adev);
-#ifdef __amd64__
- /*
-* XXX Workaround for machines where the framebuffer
-* size reported by the hardware is incorrect.
-*/
- extern psize_t efifb_stolen();
- size = max(size, efifb_stolen());
-#endif
-
if (adev->mman.keep_stolen_vga_memory)
size = max(size, (unsigned)AMDGPU_VBIOS_VGA_ALLOCATION);
}
Re: String of emojis and IRC color codes crashes tmux
On Wed, 24 Jan 2024 09:20:41 + Stuart Henderson wrote: > On 2024/01/23 23:12, Luiz de Milon wrote: > > When the following file is `cat`ed in tmux, the server > > crashes. This also messes up the rendering in weechat, so I > > believe the bug may be in ncurses rather than tmux. > > That seems likely - I can reproduce it in 7.4 but not -current (which > has newer curses). This is a tmux bug; nicm fixed it in tmux/screen-write.c r1.224 2023/10/30 "Do not allow UTF-8 characters that are too long, GitHub issue 3729." This fix is in -current but not 7.4. A simple reproducer is $ perl -CS -e 'print chr(0x1f1e6) x 6' or any utf-8 string of 6 characters from U+1F1E6 to U+1F1FF (regional indicator symbol letters A to Z). https://github.com/tmux/tmux/issues/3729
Re: Unable to boot -current without disabling amdgpu
On Wed, Jan 24, 2024 at 12:54:10PM -0500, Josh Rickmar wrote: > I may have stumbled upon a fix by accident. Enabling resizable BAR in > my UEFI settings seems to stop the crash. I unsuccessfully tried to reproduce the problem by disabling CSM and doing a new UEFI/GPT install on: bios0: vendor American Megatrends Inc. version "P3.20" date 04/09/2019 bios0: ASRock X470 Gaming K4 .. cpu0: AMD Ryzen 5 2600X Six-Core Processor, 3600.00 MHz, 17-08-02, patch 0800820b .. amdgpu0: VEGA10 GC 9.0.1 56 CU rev 0x01 The card has the resizable BAR capability, but there are no system bios options for it. Resizable BAR seems to require >= Ryzen 3000 (Zen 2). 33:0:0: ATI Radeon Rx Vega 0x: Vendor ID: 1002, Product ID: 687f 0x0004: Command: 0006, Status: 0010 0x0008: Class: 03 Display, Subclass: 00 VGA, Interface: 00, Revision: c3 0x000c: BIST: 00, Header Type: 80, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem prefetchable 64bit addr: 0xe000/0x1000 0x0018: BAR mem prefetchable 64bit addr: 0xf000/0x0020 0x0020: BAR io addr: 0xe000/0x0100 0x0024: BAR mem 32bit addr: 0xfcb0/0x0008 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1458 Product ID: 230c 0x0030: Expansion ROM Base Address: fcb8 0x0038: 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00 0x0048: Capability 0x09: Vendor Specific 0x0050: Capability 0x01: Power Management State: D0 0x0064: Capability 0x10: PCI Express Max Payload Size: 256 / 256 bytes Max Read Request Size: 512 bytes Link Speed: 8.0 / 8.0 GT/s Link Width: x16 / x16 0x0100: Enhanced Capability 0x0b: Vendor-Specific 0x0150: Enhanced Capability 0x01: Advanced Error Reporting 0x0200: Enhanced Capability 0x15: Resizable BAR 0x0270: Enhanced Capability 0x19: Secondary PCIe Capability 0x02a0: Enhanced Capability 0x0d: Access Control Services 0x02b0: Enhanced Capability 0x0f: Address Translation Services 0x02c0: Enhanced Capability 0x13: Page Request Interface 0x02d0: Enhanced Capability 0x1b: Process Address Space ID 0x0320: Enhanced Capability 0x18: Latency Tolerance Reporting 0x00a0: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes
Re: Unable to boot -current without disabling amdgpu
On Thu, Jan 25, 2024 at 02:14:58PM +1100, Jonathan Gray wrote: > On Wed, Jan 24, 2024 at 12:54:10PM -0500, Josh Rickmar wrote: > > I may have stumbled upon a fix by accident. Enabling resizable BAR in > > my UEFI settings seems to stop the crash. > > I unsuccessfully tried to reproduce the problem by disabling CSM and > doing a new UEFI/GPT install on: > > bios0: vendor American Megatrends Inc. version "P3.20" date 04/09/2019 > bios0: ASRock X470 Gaming K4 > .. > cpu0: AMD Ryzen 5 2600X Six-Core Processor, 3600.00 MHz, 17-08-02, patch > 0800820b > .. > amdgpu0: VEGA10 GC 9.0.1 56 CU rev 0x01 > > The card has the resizable BAR capability, but there are no system bios > options for it. Resizable BAR seems to require >= Ryzen 3000 (Zen 2). > > 33:0:0: ATI Radeon Rx Vega > 0x: Vendor ID: 1002, Product ID: 687f > 0x0004: Command: 0006, Status: 0010 > 0x0008: Class: 03 Display, Subclass: 00 VGA, > Interface: 00, Revision: c3 > 0x000c: BIST: 00, Header Type: 80, Latency Timer: 00, > Cache Line Size: 10 > 0x0010: BAR mem prefetchable 64bit addr: 0xe000/0x1000 > 0x0018: BAR mem prefetchable 64bit addr: 0xf000/0x0020 > 0x0020: BAR io addr: 0xe000/0x0100 > 0x0024: BAR mem 32bit addr: 0xfcb0/0x0008 > 0x0028: Cardbus CIS: > 0x002c: Subsystem Vendor ID: 1458 Product ID: 230c > 0x0030: Expansion ROM Base Address: fcb8 > 0x0038: > 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00 > 0x0048: Capability 0x09: Vendor Specific > 0x0050: Capability 0x01: Power Management > State: D0 > 0x0064: Capability 0x10: PCI Express > Max Payload Size: 256 / 256 bytes > Max Read Request Size: 512 bytes > Link Speed: 8.0 / 8.0 GT/s > Link Width: x16 / x16 > 0x0100: Enhanced Capability 0x0b: Vendor-Specific > 0x0150: Enhanced Capability 0x01: Advanced Error Reporting > 0x0200: Enhanced Capability 0x15: Resizable BAR > 0x0270: Enhanced Capability 0x19: Secondary PCIe Capability > 0x02a0: Enhanced Capability 0x0d: Access Control Services > 0x02b0: Enhanced Capability 0x0f: Address Translation Services > 0x02c0: Enhanced Capability 0x13: Page Request Interface > 0x02d0: Enhanced Capability 0x1b: Process Address Space ID > 0x0320: Enhanced Capability 0x18: Latency Tolerance Reporting > 0x00a0: Capability 0x05: Message Signalled Interrupts (MSI) > Enabled: yes > It might be due to some other percularities about my bios menu. This motherboard is a MSI B550 Tomahawk. When resizable BAR is enabled, two other bios settings flip on as well, one named "Above 4G memory/Crypto Currency mining" and the other "Restore PCIe registers". The latter does not have its own menu option as far as I can see: it is turned on and off with resizable BAR and is only shown in the summary page of changes when saving settings. The >4G memory option can be toggled separately from resizable BAR/restore PCIe registers, however I tried all combinations of these settings and only enabling all of them avoids the crash. 45:0:0: ATI Radeon Rx Vega 0x: Vendor ID: 1002, Product ID: 687f 0x0004: Command: 0006, Status: 0010 0x0008: Class: 03 Display, Subclass: 00 VGA, Interface: 00, Revision: c1 0x000c: BIST: 00, Header Type: 80, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem prefetchable 64bit addr: 0x007c/0x2 0x0018: BAR mem prefetchable 64bit addr: 0x007e/0x1000 0x0020: BAR io addr: 0xf000/0x0100 0x0024: BAR mem 32bit addr: 0xfcd0/0x0008 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1da2 Product ID: e37f 0x0030: Expansion ROM Base Address: fcd8 0x0038: 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00 0x0048: Capability 0x09: Vendor Specific 0x0050: Capability 0x01: Power Management State: D0 0x0064: Capability 0x10: PCI Express Max Payload Size: 256 / 256 bytes Max Read Request Size: 512 bytes Link Speed: 8.0 / 8.0 GT/s Link Width: x16 / x16 0x0100: Enhanced Capability 0x0b: Vendor-Specific 0x0150: Enhanced Capability 0x01: Advanced Error Reporting 0x0200: Enhanced Capability 0x15: Resizable BAR 0x0270: Enhanced Capability 0x19: Secondary PCIe Capability 0x02a0: Enhanced Capability 0x0d: Access Control Services 0x02b0: Enhanced Capability 0x0f: Address Translation Services 0x02c0: Enhanced Capability 0x13: Page Request Interface 0x02d0: Enhanced Capability 0x1b: Process Address Space ID 0x0320: Enhanced Capability 0x18:
