You are not logged in.

#1 2019-09-25 17:25:48

FREEZE_ball
Member
Registered: 2018-05-06
Posts: 9

[SOLVED] Kernel oops on boot with RX 5700 XT

Edit #3 and the soultion:
Do not use linux-zen untill this is fixed there, use mainline linux 5.3!


So yesterday I finally got the last piece of my build: shiny new Sapphire Pulse Radeon RX 5700 XT, and instead of enjoying it's performance I am struggling to boot. After typical systemd starting output that flashes for a moment, it turns the screen black and powers the card off. Card's fans stop, but all other fans inside the tower continue working. Keyboard stops reacting, I can't switch TTY, I can't login through SSH. Checking # journalctl -b -1 yields this:

Sep 25 18:44:26 FB-PC kernel: [drm] reserve 0x7200000 from 0x8000800000 for PSP TMR
Sep 25 18:44:26 FB-PC kernel: amdgpu: [powerplay] SMU is initialized successfully!
Sep 25 18:44:26 FB-PC kernel: [drm] Display Core initialized with v3.2.35!
Sep 25 18:44:26 FB-PC kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Sep 25 18:44:26 FB-PC kernel: [drm] Driver supports precise vblank timestamp query.
Sep 25 18:44:26 FB-PC kernel: [drm] kiq ring mec 2 pipe 1 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 10 succeeded in 46 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 10 succeeded in 13 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] gfx 0 ring me 0 pipe 0 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 0 succeeded in 12 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] gfx 1 ring me 0 pipe 1 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 1 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 0 mec 1 pipe 0 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 2 succeeded in 3 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 1 mec 1 pipe 1 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 3 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 2 mec 1 pipe 2 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 4 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 3 mec 1 pipe 3 q 0
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 5 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 4 mec 1 pipe 0 q 1
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 6 succeeded in 2 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 5 mec 1 pipe 1 q 1
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 7 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 6 mec 1 pipe 2 q 1
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 8 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] compute ring 7 mec 1 pipe 3 q 1
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 9 succeeded in 1 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 11 succeeded in 17 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] ring test on 12 succeeded in 17 usecs
Sep 25 18:44:26 FB-PC kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Sep 25 18:44:26 FB-PC kernel: kfd kfd: Allocated 3969056 bytes on gart
Sep 25 18:44:26 FB-PC kernel: Virtual CRAT table created for GPU
Sep 25 18:44:26 FB-PC kernel: Parsing CRAT table with 1 nodes
Sep 25 18:44:26 FB-PC kernel: Creating topology SYSFS entries
Sep 25 18:44:26 FB-PC kernel: Topology: Add dGPU node [0x731f:0x1002]
Sep 25 18:44:26 FB-PC kernel: kfd kfd: added device 1002:731f
Sep 25 18:44:26 FB-PC kernel: [drm] fb mappable at 0x4007A00000
Sep 25 18:44:26 FB-PC kernel: [drm] vram apper at 0x4000000000
Sep 25 18:44:26 FB-PC kernel: [drm] size 14745600
Sep 25 18:44:26 FB-PC kernel: [drm] fb depth is 24
Sep 25 18:44:26 FB-PC kernel: [drm]    pitch is 10240
Sep 25 18:44:26 FB-PC kernel: fbcon: amdgpudrmfb (fb0) is primary device
Sep 25 18:44:26 FB-PC kernel: general protection fault: 0000 [#1] PREEMPT SMP NOPTI
Sep 25 18:44:26 FB-PC kernel: CPU: 13 PID: 462 Comm: systemd-udevd Tainted: G           OE     5.3.1-zen1-1-zen #1
Sep 25 18:44:26 FB-PC kernel: Hardware name: System manufacturer System Product Name/ROG MAXIMUS XI HERO (WI-FI), BIOS 1302 09/02/2019
Sep 25 18:44:26 FB-PC kernel: RIP: 0010:dcn20_validate_bandwidth+0x3dc/0x2910 [amdgpu]
Sep 25 18:44:26 FB-PC kernel: Code: 2b 04 00 00 41 39 c4 0f 8c 2b 04 00 00 8b 7c 24 20 0f 28 05 96 8b 23 00 48 c7 44 24 60 ff ff ff ff 48 8b 85 f8 02 00 00 85 ff <0f> 29 44 24 50 0f 95 44 24 10 8b 80 a8 02 00 00 85 c0 0f 84 69 04
Sep 25 18:44:26 FB-PC kernel: RSP: 0018:ffffb05980ab7508 EFLAGS: 00010246
Sep 25 18:44:26 FB-PC kernel: RAX: ffff9915b31a8000 RBX: ffff9915920a0000 RCX: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: RBP: ffff991593dc0000 R08: 0000000000000001 R09: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000003
Sep 25 18:44:26 FB-PC kernel: R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
Sep 25 18:44:26 FB-PC kernel: FS:  00007fd2387a9840(0000) GS:ffff9915bdb40000(0000) knlGS:0000000000000000
Sep 25 18:44:26 FB-PC kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 25 18:44:26 FB-PC kernel: CR2: 00005648c95ea000 CR3: 0000000c33910001 CR4: 00000000003606e0
Sep 25 18:44:26 FB-PC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 25 18:44:26 FB-PC kernel: Call Trace:
Sep 25 18:44:26 FB-PC kernel:  dc_validate_global_state+0x454/0x810 [amdgpu]
Sep 25 18:44:26 FB-PC kernel:  amdgpu_dm_atomic_check+0x479/0x750 [amdgpu]
Sep 25 18:44:26 FB-PC kernel:  drm_atomic_check_only+0x55b/0x780 [drm]
Sep 25 18:44:26 FB-PC kernel:  drm_atomic_commit+0x13/0x50 [drm]
Sep 25 18:44:26 FB-PC kernel:  drm_client_modeset_commit_atomic+0x1da/0x250 [drm]
Sep 25 18:44:26 FB-PC kernel:  drm_client_modeset_commit_force+0x50/0x170 [drm]
Sep 25 18:44:26 FB-PC kernel:  drm_fb_helper_set_par+0x68/0xd0 [drm_kms_helper]
Sep 25 18:44:26 FB-PC kernel:  fbcon_init+0x3cb/0x770
Sep 25 18:44:26 FB-PC kernel:  visual_init+0xce/0x130
Sep 25 18:44:26 FB-PC kernel:  do_bind_con_driver+0x27e/0x540
Sep 25 18:44:26 FB-PC kernel:  do_take_over_console+0x24d/0x460
Sep 25 18:44:26 FB-PC kernel:  fbcon_fb_registered+0xe8/0x160
Sep 25 18:44:26 FB-PC kernel:  register_framebuffer+0x1f6/0x310
Sep 25 18:44:26 FB-PC kernel:  __drm_fb_helper_initial_config_and_unlock+0x314/0x460 [drm_kms_helper]
Sep 25 18:44:26 FB-PC kernel:  amdgpu_fbdev_init+0xbc/0xf0 [amdgpu]
Sep 25 18:44:26 FB-PC kernel:  amdgpu_device_init.cold+0x14e1/0x16f3 [amdgpu]
Sep 25 18:44:26 FB-PC kernel:  amdgpu_driver_load_kms+0x88/0x270 [amdgpu]
Sep 25 18:44:26 FB-PC kernel:  drm_dev_register+0x200/0x240 [drm]
Sep 25 18:44:26 FB-PC kernel:  amdgpu_pci_probe+0xbd/0x120 [amdgpu]
Sep 25 18:44:26 FB-PC kernel:  ? __pm_runtime_resume+0x49/0x60
Sep 25 18:44:26 FB-PC kernel:  pci_device_probe+0x19e/0x210
Sep 25 18:44:26 FB-PC kernel:  really_probe+0xf2/0x640
Sep 25 18:44:26 FB-PC kernel:  driver_probe_device+0xb6/0x100
Sep 25 18:44:26 FB-PC kernel:  __driver_attach+0x118/0x260
Sep 25 18:44:26 FB-PC kernel:  ? __device_attach_driver+0x180/0x180
Sep 25 18:44:26 FB-PC kernel:  ? __device_attach_driver+0x180/0x180
Sep 25 18:44:26 FB-PC kernel:  bus_for_each_dev+0x89/0xd0
Sep 25 18:44:26 FB-PC kernel:  bus_add_driver+0x14a/0x1e0
Sep 25 18:44:26 FB-PC kernel:  driver_register+0x8b/0xd0
Sep 25 18:44:26 FB-PC kernel:  ? 0xffffffffc248b000
Sep 25 18:44:26 FB-PC kernel:  do_one_initcall+0x59/0x234
Sep 25 18:44:26 FB-PC kernel:  do_init_module+0x5c/0x260
Sep 25 18:44:26 FB-PC kernel:  load_module+0x2a7b/0x2d10
Sep 25 18:44:26 FB-PC kernel:  ? __se_sys_init_module+0x171/0x1a0
Sep 25 18:44:26 FB-PC kernel:  __se_sys_init_module+0x171/0x1a0
Sep 25 18:44:26 FB-PC kernel:  do_syscall_64+0x5f/0x1c0
Sep 25 18:44:26 FB-PC kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 25 18:44:26 FB-PC kernel: RIP: 0033:0x7fd239fc3b3e
Sep 25 18:44:26 FB-PC kernel: Code: 48 8b 0d 55 f3 0b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 22 f3 0b 00 f7 d8 64 89 01 48
Sep 25 18:44:26 FB-PC kernel: RSP: 002b:00007ffcfaee9368 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Sep 25 18:44:26 FB-PC kernel: RAX: ffffffffffffffda RBX: 00005648c95bc4e0 RCX: 00007fd239fc3b3e
Sep 25 18:44:26 FB-PC kernel: RDX: 00007fd239c1684d RSI: 00000000008f82e9 RDI: 00005648c9fae900
Sep 25 18:44:26 FB-PC kernel: RBP: 00007fd239c1684d R08: 000000000000005f R09: 00005648c95cbb00
Sep 25 18:44:26 FB-PC kernel: R10: 00005648c93ad010 R11: 0000000000000246 R12: 00005648c9fae900
Sep 25 18:44:26 FB-PC kernel: R13: 00005648c95db010 R14: 0000000000020000 R15: 00005648c95bc4e0
Sep 25 18:44:26 FB-PC kernel: Modules linked in: acpi_cpufreq(-) sof_pci_dev snd_sof_intel_hda_common intel_rapl_msr intel_rapl_common snd_sof_intel_hda ext4 snd_sof_intel_byt snd_sof_intel_ipc snd_sof nls_iso8859_1 nls_cp437 snd_sof_xtensa_dsp vfat mbcache fat snd_soc_skl jbd2 snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc btusb x86_pkg_temp_thermal btrtl intel_powerclamp snd_soc_sst_ipc btbcm coretemp snd_soc_sst_dsp btintel amdgpu(+) snd_soc_acpi_intel_match snd_soc_acpi kvm_intel bluetooth iwlmvm kvm snd_soc_core eeepc_wmi snd_hda_codec_realtek asus_wmi ecdh_generic irqbypass mac80211 crct10dif_pclmul snd_compress iTCO_wdt snd_hda_codec_generic mei_hdcp ecc ghash_clmulni_intel ac97_bus crc16 iTCO_vendor_support btrfs ledtrig_audio sparse_keymap snd_hda_codec_hdmi wmi_bmof mxm_wmi snd_pcm_dmaengine libarc4 snd_hda_intel aesni_intel snd_hda_codec gpu_sched i2c_algo_bit xor aes_x86_64 crypto_simd ttm snd_hda_core iwlwifi cryptd raid6_pq drm_kms_helper snd_hwdep glue_helper libcrc32c snd_pcm intel_cstate
Sep 25 18:44:26 FB-PC kernel:  crc32c_generic input_leds cfg80211 drm crc32c_intel intel_uncore snd_timer e1000e agpgart snd mei_me syscopyarea sysfillrect intel_rapl_perf sysimgblt fb_sys_fops pcspkr i2c_i801 soundcore mei rfkill ie31200_edac wmi evdev acpi_tad mac_hid fuse nfsd vboxnetflt(OE) vboxnetadp(OE) vboxpci(OE) auth_rpcgss nfs_acl lockd vboxdrv(OE) grace sunrpc crypto_user ip_tables x_tables f2fs hid_generic usbhid hid sd_mod ahci libahci libata xhci_pci scsi_mod crc32_pclmul xhci_hcd
Sep 25 18:44:26 FB-PC kernel: ---[ end trace 2dc10d2f8826fcfa ]---
Sep 25 18:44:26 FB-PC kernel: RIP: 0010:dcn20_validate_bandwidth+0x3dc/0x2910 [amdgpu]
Sep 25 18:44:26 FB-PC kernel: Code: 2b 04 00 00 41 39 c4 0f 8c 2b 04 00 00 8b 7c 24 20 0f 28 05 96 8b 23 00 48 c7 44 24 60 ff ff ff ff 48 8b 85 f8 02 00 00 85 ff <0f> 29 44 24 50 0f 95 44 24 10 8b 80 a8 02 00 00 85 c0 0f 84 69 04
Sep 25 18:44:26 FB-PC kernel: RSP: 0018:ffffb05980ab7508 EFLAGS: 00010246
Sep 25 18:44:26 FB-PC kernel: RAX: ffff9915b31a8000 RBX: ffff9915920a0000 RCX: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: RBP: ffff991593dc0000 R08: 0000000000000001 R09: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000003
Sep 25 18:44:26 FB-PC kernel: R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
Sep 25 18:44:26 FB-PC kernel: FS:  00007fd2387a9840(0000) GS:ffff9915bdb40000(0000) knlGS:0000000000000000
Sep 25 18:44:26 FB-PC kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 25 18:44:26 FB-PC kernel: CR2: 00005648c95ea000 CR3: 0000000c33910001 CR4: 00000000003606e0
Sep 25 18:44:26 FB-PC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 25 18:44:26 FB-PC kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Full log. Note that it ends in 4 seconds after it starts, although I left the PC for a couple of minutes to write as much as possible.

My bootloader is systemd-boot and motherboard is Asus RoG Maximus Hero XI (I updated BIOS with the neweset one from the manufacturer's site), the system should boot through SDDM into KDE. Nomodeset parameter obviously works, but does not help. X.org and SDDM spit no logs without nomodeset. Previously the system used EVGA GeForce GTX760, all that left from it is:

fb@FB-PC ~ % pacman -Qs nvidia
local/libvdpau 1.3-1
    Nvidia VDPAU library
fb@FB-PC ~ % 

The whole day was spent on trying to resolve this issue. Threads like this were scanned 5 times, AMDGPU article on arch wiki was used as the handguide of the day, all links from the last week that Google gave me by multiple different combination of keywords "linux" "5700" "arch" were visited and some attempts were done:

  1. Listening to advices from multiple people who were using 5700 before 5.3 kernel, first I used AUR to recompile most of the mesa stuff. After that I returned to normal and then connected to Mesa-git repo. Final results look like this:

    fb@FB-PC ~ % pacman -Qs mesa  
    local/clang-git 10.0.0_r327425.63f6066b53d-1 (mesagit)
        C language family frontend for LLVM (git version)
    local/glu 9.0.1-1
        Mesa OpenGL Utility library
    local/lib32-glu 9.0.1-1
        Mesa OpenGL utility library (32 bits)
    local/lib32-llvm-git 10.0.0_r327426.eee532cd5f9-1 (mesagit)
        Low Level Virtual Machine (32-bit)(git version)
    local/lib32-llvm-libs-git 10.0.0_r327426.eee532cd5f9-1 (mesagit)
        Low Level Virtual Machine library (runtime library)(32-bit)(git version)
    local/lib32-mesa-git 1:19.3.0_devel.115574.40087ffc5b9-1 (mesagit)
        an open-source implementation of the OpenGL specification (32-bit) (git version)
    local/lib32-vulkan-radeon-git 1:19.3.0_devel.115574.40087ffc5b9-1 (mesagit)
        Radeon's Vulkan mesa driver (32-bit) (git version)
    local/libclc-git 587.201909211750-1 (mesagit)
        Library requirements of the OpenCL C programming language (git version)
    local/llvm-git 10.0.0_r327425.63f6066b53d-1 (mesagit)
        Collection of modular and reusable compiler and toolchain technologies (git version)
    local/llvm-libs-git 10.0.0_r327425.63f6066b53d-1 (mesagit)
        LLVM runtime libraries (git version)
    local/mesa-demos 8.4.0-1
        Mesa demos and tools incl. glxinfo + glxgears
    local/mesa-git 1:19.3.0_devel.115574.40087ffc5b9-1 (mesagit)
        an open-source implementation of the OpenGL specification (git version)
    local/opencl-mesa-git 1:19.3.0_devel.115574.40087ffc5b9-1 (mesagit)
        OpenCL support for mesa drivers (git version)
    local/vulkan-radeon-git 1:19.3.0_devel.115574.40087ffc5b9-1 (mesagit)
        Radeon's Vulkan mesa driver (git version)
    fb@FB-PC ~ % 
  2. At first, I used just this firmware but then I switched to:

    fb@FB-PC ~ % pacman -Qs linux-firmware
    local/linux-firmware-git 20190923.417a9c6-1
        Firmware files for Linux
    fb@FB-PC ~ % 
  3. I tried to boot into graphical target from onboard DP. It boots normally into multiuser, but spits out X.org errors such as "no screens found" and "can't detect display from the pipe" and even "X is already running". Spent two hours of quality time with Google looking these errors and most of the solutions were "wrong drivers", "downgrade kernel", "wrong configs" and "upgrade kernel". Tried some of that (even downgraded linux-zen to 5.3.0), got nothing and gave up. Everything from this article was installed already, btw. But that made me thinking I have some wrong configs and lead to the next point.

  4. I scanned typical X.org.conf folders (got from man xorg.conf) and renamed all found configs to *.conf.backup

  5. I updated my BIOS to the latest firmware.

  6. I installed Win10 on an old HDD just to briefly check if the cards works there. It does.

  7. I attempted to install fresh Arch on the same HDD (over Windows) but have done it in haste and screwed up partitioning so I gave up on that one. Oups. Next time I will reinstall, I will do so as the last resort. The HDD was pulled out of the computer.

  8. Tried 2 different monitors, 2 different PCI-E slots, 3 different DP ports on the card and 2 different DP cables out of it.

  9. GDM

  10. Edit #2: I have tried to do mkinitcpio changes with modules, files (explicitly set navi firmware) and blacklists. At the end, I returned to empty MODULES=() and FILES=(), and you can see amdgpu in the kernel oops log.

What I have NOT done but thought about: have not tried GPU passthrough in virtualbox (can't login into graphical interface yet), have not tried HDMi cable, have not tried a thorough test on Windows, have not tried different distributions, have not tried compiling 5.4 kernel (I am new there, scared of compatibility issues and such), have not tried installing old graphics card back, and probably something else on the same level of insignifficance that I forgot about now.

Any help would be appreciated.

Edit #1:
Almost forgot the most asked output:

fb@FB-PC ~ % lspci                                                                                                                                :(
00:00.0 Host bridge: Intel Corporation 8th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 0a)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 0a)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1478 (rev c1)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1479
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5700 / 5700 XT] (rev c1)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
fb@FB-PC ~ % 

Last edited by FREEZE_ball (2019-09-26 12:04:21)

Offline

#2 2019-09-26 10:20:17

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: [SOLVED] Kernel oops on boot with RX 5700 XT


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2019-09-26 12:01:57

FREEZE_ball
Member
Registered: 2018-05-06
Posts: 9

Re: [SOLVED] Kernel oops on boot with RX 5700 XT

Lone_Wolf wrote:

No I haven't seen this one, although it should be emphasized more there that you should use Linux kernel. I've accidentally stumbled uppon this comment and replaced my linux-zen with linux mainline, everything started working again. Thanks anyway!

Last edited by FREEZE_ball (2019-09-26 12:02:11)

Offline

Board footer

Powered by FluxBB