The GPU crashes (AMD RX580 Sapphire Nitro+ 8GB)

L

l080

New Member
Joined
Nov 17, 2021
Messages
3
Reaction score
1
Credits
30
hi everyone,

I think I have a problem with GPU driver. The screen is crashing like on the picture but audio is still present. The only way how I can get my pc back to work is by rebooting it. I noticed that this is happening more often when I run brave browser. I'm using the Firefox as my main browser and Brave browser as my secondary one. With that configuration the GPU was crashing quite rarely. Maybe only when I was running brave browser? I'm not sure about that as I didn't pay much attention to that. Yesterday, I decided that I want to make Brave my main browser and Firefox secondary. Since then I encountered the GPU crash over dozen times.

Under this link https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921004 someone is saying that this can be related to GL applications.

Thanks ahead for any help and advices :)

screen.jpg


glxinfo | grep Mesa
Code: 
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.0-devel (git-8ee7309 2021-11-17 focal-oibaf-ppa)
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.0-devel (git-8ee7309 2021-11-17 focal-oibaf-ppa)
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.0-devel (git-8ee7309 2021-11-17 focal-oibaf-ppa)


inxi -Fxxxrz
Code: 
System:    Kernel: 5.11.0-40-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.38.4
           wm: gnome-shell dm: GDM3 3.38.2.1 Distro: Zorin OS 16 base: Ubuntu 20.04 LTS Focal
Machine:   Type: Desktop Mobo: Micro-Star model: Z490-A PRO (MS-7C75) v: 1.0 serial: <filter>
           UEFI: American Megatrends v: 2.90 date: 04/20/2021
CPU:       Topology: 10-Core model: Intel Core i9-10850K bits: 64 type: MT MCP arch: N/A
           L2 cache: 20.0 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 144000
           Speed: 800 MHz min/max: 800/5200 MHz Core speeds (MHz): 1: 808 2: 4348 3: 3418
           4: 2241 5: 1376 6: 4484 7: 3236 8: 2024 9: 1116 10: 800 11: 800 12: 800 13: 1386
           14: 800 15: 800 16: 800 17: 852 18: 3043 19: 3192 20: 1730
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
           vendor: Sapphire Limited Nitro+ driver: amdgpu v: kernel bus ID: 01:00.0
           chip ID: 1002:67df
           Display: x11 server: X.Org 1.20.11 driver: amdgpu compositor: gnome-shell
           resolution: 3840x2160~60Hz, 3840x2160~30Hz
           OpenGL:
           renderer: AMD Radeon RX 580 Series (polaris10 LLVM 13.0.0 DRM 3.40 5.11.0-40-generic)
           v: 4.6 Mesa 22.0.0-devel (git-8ee7309 2021-11-17 focal-oibaf-ppa) direct render: Yes
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: Micro-Star MSI driver: snd_hda_intel
           v: kernel bus ID: 00:1f.3 chip ID: 8086:06c8
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
           vendor: Sapphire Limited driver: snd_hda_intel v: kernel bus ID: 01:00.1
           chip ID: 1002:aaf0
           Device-3: Corsair type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-1.4:7
           chip ID: 1b1c:0a42 serial: <filter>
           Sound Server: ALSA v: k5.11.0-40-generic
Network:   Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel
           port: 3000 bus ID: 04:00.0 chip ID: 10ec:8125
           IF: enp4s0 state: down mac: <filter>
           Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: 3000 bus ID: 05:00.0
           chip ID: 8086:24f3
           IF: wlp5s0 state: up mac: <filter>
Drives:    Local Storage: total: 4.55 TiB used: 441.58 GiB (9.5%)
           ID-1: /dev/nvme0n1 vendor: Crucial model: CT500P2SSD8 size: 465.76 GiB
           speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: P2CR031 scheme: GPT
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
           speed: 63.2 Gb/s lanes: 4 serial: <filter> rev: 2B2QGXA7 scheme: GPT
           ID-3: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
           speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 0001 scheme: GPT
           ID-4: /dev/sdb vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB speed: 6.0 Gb/s
           serial: <filter> rev: 033 scheme: GPT
Partition: ID-1: / size: 227.98 GiB used: 144.08 GiB (63.2%) fs: ext4 dev: /dev/nvme0n1p2
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A gpu: amdgpu temp: 49 C
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 811
Repos:     Active apt repos in: /etc/apt/sources.list
           1: deb http://gb.archive.ubuntu.com/ubuntu/ focal main restricted
           2: deb http://gb.archive.ubuntu.com/ubuntu/ focal-updates main restricted
           3: deb http://gb.archive.ubuntu.com/ubuntu/ focal universe
           4: deb http://gb.archive.ubuntu.com/ubuntu/ focal-updates universe
           5: deb http://gb.archive.ubuntu.com/ubuntu/ focal multiverse
           6: deb http://gb.archive.ubuntu.com/ubuntu/ focal-updates multiverse
           7: deb http://gb.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
           8: deb http://security.ubuntu.com/ubuntu focal-security main restricted
           9: deb http://security.ubuntu.com/ubuntu focal-security universe
           10: deb http://security.ubuntu.com/ubuntu focal-security multiverse
           11: deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
           Active apt repos in: /etc/apt/sources.list.d/appimagelauncher-team-ubuntu-stable-focal.list
           1: deb http://ppa.launchpad.net/appimagelauncher-team/stable/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/blaze-ubuntu-rtbth-dkms-focal.list
           1: deb http://ppa.launchpad.net/blaze/rtbth-dkms/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/kisak-ubuntu-kisak-mesa-focal.list
           1: deb http://ppa.launchpad.net/kisak/kisak-mesa/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/oibaf-ubuntu-graphics-drivers-focal.list
           1: deb http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/pipewire-debian-ubuntu-pipewire-upstream-focal.list
           1: deb http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list
           1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
           Active apt repos in: /etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-focal.list
           1: deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/zorin.list
           1: deb https://packages.zorinos.com/stable focal main
           2: deb https://packages.zorinos.com/patches focal main
           3: deb https://packages.zorinos.com/apps focal main
           4: deb https://packages.zorinos.com/drivers focal main restricted
           Active apt repos in: /etc/apt/sources.list.d/zorinos-ubuntu-apps-focal.list
           1: deb http://ppa.launchpad.net/zorinos/apps/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/zorinos-ubuntu-drivers-focal.list
           1: deb http://ppa.launchpad.net/zorinos/drivers/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/zorinos-ubuntu-patches-focal.list
           1: deb http://ppa.launchpad.net/zorinos/patches/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/zorinos-ubuntu-stable-focal.list
           1: deb http://ppa.launchpad.net/zorinos/stable/ubuntu focal main
Info:      Processes: 401 Uptime: 16m Memory: 31.28 GiB used: 2.61 GiB (8.4%) Init: systemd
           v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17
           running in: gnome-terminal inxi: 3.0.38

Logs:
Code: 
Nov 18 10:55:25 l080-PC kernel: [ 8866.986778] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=469157, emitted seq=469158
Nov 18 10:55:25 l080-PC kernel: [ 8866.987327] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process brave pid 10704 thread amdgpu_cs:0 pid 10873
Nov 18 10:55:25 l080-PC kernel: [ 8866.987819] amdgpu 0000:01:00.0: amdgpu: GPU reset begin!
Nov 18 10:55:25 l080-PC kernel: [ 8867.220719] amdgpu 0000:01:00.0: amdgpu: BACO reset
Nov 18 10:55:26 l080-PC kernel: [ 8867.526571] amdgpu 0000:01:00.0: amdgpu: GPU reset succeeded, trying to resume
Nov 18 10:55:26 l080-PC kernel: [ 8867.527146] [drm] PCIE GART of 256M enabled (table at 0x000000F401FA4000).
Nov 18 10:55:26 l080-PC kernel: [ 8867.527155] [drm] VRAM is lost due to GPU reset!
Nov 18 10:55:26 l080-PC kernel: [ 8867.792751] [drm] UVD and UVD ENC initialized successfully.
Nov 18 10:55:26 l080-PC kernel: [ 8867.902805] [drm] VCE initialized successfully.
Nov 18 10:55:26 l080-PC kernel: [ 8867.910309] amdgpu 0000:01:00.0: amdgpu: recover vram bo from shadow start
Nov 18 10:55:26 l080-PC gnome-shell[10669]: amdgpu: amdgpu_cs_query_fence_status failed.
Nov 18 10:55:26 l080-PC gnome-shell[10669]: [10704:10704:1118/105526.617325:ERROR:shared_context_state.cc(834)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR
Nov 18 10:55:26 l080-PC gnome-shell[10669]: [10704:10704:1118/105526.617707:ERROR:gpu_service_impl.cc(947)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Nov 18 10:55:26 l080-PC kernel: [ 8867.917710] amdgpu 0000:01:00.0: amdgpu: recover vram bo from shadow done
Nov 18 10:55:26 l080-PC kernel: [ 8867.917716] [drm] Skip scheduling IBs!
Nov 18 10:55:26 l080-PC kernel: [ 8867.917723] amdgpu 0000:01:00.0: amdgpu: GPU reset(1) succeeded!
Nov 18 10:55:26 l080-PC kernel: [ 8867.917825] [drm] Skip scheduling IBs!
Nov 18 10:55:26 l080-PC kernel: [ 8867.917847] [drm] Skip scheduling IBs!
Nov 18 10:55:26 l080-PC kernel: [ 8867.917848] [drm] Skip scheduling IBs!
Nov 18 10:55:26 l080-PC gnome-shell[10669]: [10670:10670:1118/105526.624063:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange.
Nov 18 10:55:26 l080-PC gnome-shell[10669]: [10670:10670:1118/105526.627933:ERROR:gpu_process_host.cc(967)] GPU process exited unexpectedly: exit_code=8704
Nov 18 10:55:26 l080-PC gnome-shell[10669]: /usr/share/libdrm/amdgpu.ids: No such file or directory
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC kernel: [ 8867.979255] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC kernel: [ 8867.980925] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC gnome-shell[10669]: [22570:22570:1118/105526.685421:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
Nov 18 10:55:26 l080-PC com.spotify.Client.desktop[22568]: [spotifywm] spotify window found
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC kernel: [ 8868.000924] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC gnome-shell[6661]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC kernel: [ 8868.005769] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC kernel: [ 8868.007059] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC kernel: [ 8868.007233] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC gnome-shell[6661]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC kernel: [ 8868.020689] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC kernel: [ 8868.062582] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC kernel: [ 8868.062886] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC kernel: [ 8868.065255] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: message repeated 4 times: [ amdgpu: The CS has been cancelled because the context is lost.]
Nov 18 10:55:26 l080-PC gnome-shell[6661]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:26 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
.............................................................................................
...............                                                       .......................
............... A LOT OF REPEATED ERRORS .......................
...............                                                       .......................
.............................................................................................
Nov 18 10:55:29 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:29 l080-PC gnome-shell[6661]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:29 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:29 l080-PC gnome-shell[6661]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:29 l080-PC gnome-shell[6661]: message repeated 4 times: [ amdgpu: The CS has been cancelled because the context is lost.]
Nov 18 10:55:29 l080-PC gnome-shell[8987]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:29 l080-PC gnome-shell[8987]: message repeated 3 times: [ amdgpu: The CS has been cancelled because the context is lost.]
Nov 18 10:55:29 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:29 l080-PC /usr/libexec/gdm-x-session[6407]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:30 l080-PC /usr/libexec/gdm-x-session[6407]: message repeated 2 times: [ amdgpu: The CS has been cancelled because the context is lost.]
Nov 18 10:55:30 l080-PC gnome-shell[6661]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:30 l080-PC gnome-shell[8987]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:30 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:30 l080-PC gnome-shell[22237]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:30 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:30 l080-PC gnome-shell[8987]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:30 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:30 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:30 l080-PC gnome-shell[22237]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:30 l080-PC gnome-shell[11855]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:30 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:30 l080-PC gnome-shell[8987]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:30 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:30 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:30 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:30 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:30 l080-PC gnome-shell[22237]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:30 l080-PC gnome-shell[11855]: [GFX1-]: Failed to connect WebRenderBridgeChild.
.............................................................................................
...............                                                       .......................
............... A LOT OF REPEATED ERRORS .......................
...............                                                       .......................
.............................................................................................
Nov 18 10:55:31 l080-PC gnome-shell[9714]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[11855]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:31 l080-PC gnome-shell[8987]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:31 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:31 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:31 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:31 l080-PC gnome-shell[22237]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:31 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:31 l080-PC gnome-shell[9714]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[11855]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:31 l080-PC gnome-shell[8987]: amdgpu: The CS has been cancelled because the context is lost.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:31 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:31 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:31 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:31 l080-PC gnome-shell[22237]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: IPDL protocol error: Handler returned error code!
Nov 18 10:55:31 l080-PC gnome-shell[8987]: ###!!! [Parent][DispatchSyncMessage] Error: PCompositorBridge::Msg_NotifyChildRecreated Processing error: message was deserialized, but the handler returned false (indicating failure)
Nov 18 10:55:31 l080-PC gnome-shell[9714]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[11855]: [GFX1-]: Failed to connect WebRenderBridgeChild.
Nov 18 10:55:31 l080-PC gnome-shell[8987]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Nov 18 10:55:31 l080-PC gnome-shell[8987]: amNov 18 10:56:44 l080-PC systemd-modules-load[496]: Inserted module 'lp'
Nov 18 10:56:44 l080-PC kernel: [    0.000000] Linux version 5.11.0-40-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #44~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021 (Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22)
Nov 18 10:56:44 l080-PC systemd-modules-load[496]: Inserted module 'ppdev'

lshw -C video
Code: 
  *-display                
       description: VGA compatible controller
       product: Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: /dev/fb0
       version: e7
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=amdgpu latency=0 mode=3840x2160 visual=truecolor xres=3840 yres=2160
       resources: iomemory:420-41f iomemory:410-40f irq:151 memory:4200000000-43ffffffff memory:4100000000-41001fffff ioport:4000(size=256) memory:a0400000-a043ffff memory:c0000-dffff
 

Attachments

  • fullLog.txt
    1.5 MB · Views: 468


Let's try a pretty basic step first.

In Brave's preferences, as it's a Chromium based browser, you should find (in the advanced section) an option for Hardware Acceleration. Turn that off and restart your browser.
 
KGIII said:
Let's try a pretty basic step first.

In Brave's preferences, as it's a Chromium based browser, you should find (in the advanced section) an option for Hardware Acceleration. Turn that off and restart your browser.
Click to expand...
I will test it and let you know. thanks ;)

Also since my post, I updated a bios to the latest one which in theory it shouldn't change anything but for last few hours there was no GPU crash.

Code: 
MSI Z490-A PRO 
Version                                  
7C75v2C
                                                                                                                       
Release Date                               
2021-10-18
                               
Description                                
-  Windows 11 Supported.
-  Improved compatibility for Intel Thunderbolt devices.
 
l080 said:
Also since my post, I updated a bios to the latest one which in theory it shouldn't change anything but for last few hours there was no GPU crash.
Click to expand...

It's probably the hardware acceleration thing. It's a fairly regular problem. Hardware Acceleration doesn't work on Linux and Google has no plans on making it work. Why it's there and why it's enabled by default remain mysteries.

Most of the time, it doesn't cause a problem. When it does, it causes freezes, lockups, screwy graphics, etc...

So, whenever someone's freezing and they're using a Chromium-based browser, have 'em disable hardware acceleration. It's a basic first step for this.

If it continues to freeze, let us know. If it doesn't freeze over the next couple of days, let us know.
 
It looks like the hardware acceleration was a problem. Now everything works fine and no crashes! Thanks @KGIII for your help :)
 
It fixes a surprising number of symptoms.

Again, I have no idea why it's there and enabled by default. It doesn't work. They don't plan on making it work. Yet, there it is and it's enabled by default.
 
KGIII said:
In Brave's preferences, as it's a Chromium based browser, you should find (in the advanced section) an option for Hardware Acceleration. Turn that off and restart your browser.
Click to expand...
I have hardware acceleration turn on on all of my Chromium based browser and had have never run into this issue. I wonder why some people experience it and others don't.
 
f33dm3bits said:
I wonder why some people experience it and others don't.
Click to expand...

I can't find a commonality - and I've used this 'fix' *dozens* of times just this year. Heck, it's one of my more popular answers on AU.

I'm sure it's not random, that there's some commonality between them beyond the superfluous.
 
This same exact situation was happening with me. It makes me slightly angry that it's small and simple things like this that can lead to system crashes, all because of a lack of development. I've since turned off hardware acceleration in Brave and now I'm going to give this a week to see what happens.

Like other people I assume, this issue only happened when I was using Brave when doing graphically intense things like watching 4K YT videos.

I'll update on the future. Still a year later it seems and this issue hasn't been resolved.
 
G'day @boongus and welcome to linux.org :)

If the OP did not report it to Brave and you do not report it to Brave, they may not even know if they have a problem.

Just saying.

Cheers

Chris Turner
wizardfromoz
 
wizardfromoz said:
G'day @boongus and welcome to linux.org :)

If the OP did not report it to Brave and you do not report it to Brave, they may not even know if they have a problem.

Just saying.

Cheers

Chris Turner
wizardfromoz
Click to expand...
Yeah that's true, I should do that. Thanks for bringing that up, a good habit to get into.
 
You must log in or register to reply here.

Staff online

Members online

Total: 546 (members: 8, guests: 538)

Latest posts

Top