Post

Resolving Laptop Crashes: A Journey Through GPU Timeouts and Chrome

Posted
By Sumama Zaeem 14 min read

Navigating Laptop Crashes: Unraveling GPU Timeouts and Chrome

Introduction

Ever found yourself bewildered by sudden laptop crashes, leaving you scratching your head for answers? Recently, I encountered this frustrating scenario as my laptop began hanging and crashing unexpectedly. Determined to uncover the underlying cause, I embarked on a troubleshooting journey that took me deep into the intricate world of log files, command-line tools like grep, awk, and sed, and the settings of my system.

Identifying the Culprit

My investigation began by delving into various log files, including the kernel logs (dmesg), journal logs (journalctl), and system logs (/var/log). Amongst the sea of information, I uncovered recurring error messages pointing to GPU timeouts, ultimately leading to a GPU reset. This recurring issue emerged as the primary suspect behind the frustrating crashes.

Unveiling the Mystery

To shed more light on the matter, I turned to command-line tools like grep, awk, and sed, leveraging their prowess to filter out specific timestamps and relevant details from the plethora of log entries. This meticulous examination unveiled a potential culprit – Google Chrome. Digging deeper, I discovered that Chrome’s heavy reliance on GPU resources could be exacerbating the timeout problem.

Formulating a Plan

With a clearer understanding of the issue at hand, I set out to devise a solution. While Ubuntu, my operating system of choice, natively supports AMD drivers, ruling out driver-related issues, Chrome’s GPU-intensive nature remained a concern. One particular setting in Chrome’s arsenal caught my attention – hardware acceleration. Armed with this insight, I decided to disable hardware acceleration in Chrome’s settings, hoping to alleviate the strain on the GPU and mitigate the crashing problem.

Implementing the Solution

After making the necessary adjustments and restarting Chrome, I eagerly monitored my laptop’s performance, anxiously awaiting the outcome. To my delight, the crashes ceased, and the system operated smoothly, free from the frustrating hang-ups that had plagued it before. It was a small tweak with a profound impact, demonstrating the power of troubleshooting and perseverance.

Key Insights

  1. Mining Log Files for Clues: The wealth of information buried within log files can provide invaluable insights into the root cause of technical issues, guiding us towards effective solutions.

  2. Harnessing Command-Line Tools: Tools like grep, awk, and sed empower us to sift through vast amounts of data, extracting crucial details and facilitating deeper analysis.

  3. Understanding Application Impact: Applications, particularly those heavy on graphics like web browsers, can significantly impact system performance. Analyzing their behavior can uncover crucial insights and inform strategic decisions.

Lessons Learned

Through this experience, I gained a newfound appreciation for the importance of patience, persistence, and resourcefulness in troubleshooting technical issues. It reinforced the notion that technology, while occasionally complex, often harbors straightforward solutions waiting to be discovered.

In conclusion, resolving the laptop crashes wasn’t just about fixing a technical glitch – it was a journey of exploration, learning, and ultimately, triumph. By unraveling the mystery behind the crashes and implementing a simple yet effective solution, I transformed frustration into satisfaction, equipping myself to tackle future challenges with confidence.

System Logs

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

Mar 13 11:07:29 do-lab kernel: [ 2461.010881] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=22819, emitted seq=22821
Mar 13 11:07:29 do-lab kernel: [ 2461.011644] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Mar 13 11:07:29 do-lab kernel: [ 2461.011911] amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
Mar 13 11:07:30 do-lab kernel: [ 2461.106020] amdgpu 0000:04:00.0: amdgpu: MODE2 reset
Mar 13 11:07:30 do-lab kernel: [ 2461.114011] amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded, trying to resume
Mar 13 11:07:30 do-lab kernel: [ 2461.114172] [drm] PCIE GART of 1024M enabled (table at 0x000000F47FC00000).
Mar 13 11:07:30 do-lab kernel: [ 2461.114254] [drm] PSP is resuming...
Mar 13 11:07:30 do-lab kernel: [ 2461.136423] [drm] reserve 0xa00000 from 0xf47e000000 for PSP TMR
Mar 13 11:07:30 do-lab kernel: [ 2461.702984] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
Mar 13 11:07:30 do-lab kernel: [ 2461.713658] amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
Mar 13 11:07:30 do-lab kernel: [ 2461.713670] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Mar 13 11:07:30 do-lab kernel: [ 2461.713680] amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Mar 13 11:07:30 do-lab kernel: [ 2461.714083] amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Mar 13 11:07:30 do-lab kernel: [ 2461.715481] [drm] DMUB hardware initialized: version=0x06000800
Mar 13 11:07:31 do-lab kernel: [ 2462.584497] [drm] kiq ring mec 2 pipe 1 q 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588549] [drm] VCN decode and encode initialized successfully(under DPG Mode).
Mar 13 11:07:31 do-lab kernel: [ 2462.588669] [drm] JPEG decode initialized successfully.
Mar 13 11:07:31 do-lab kernel: [ 2462.588674] amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588677] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588679] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588681] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588683] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588685] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588687] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588689] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588691] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588693] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588695] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Mar 13 11:07:31 do-lab kernel: [ 2462.588697] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Mar 13 11:07:31 do-lab kernel: [ 2462.588699] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Mar 13 11:07:31 do-lab kernel: [ 2462.588701] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Mar 13 11:07:31 do-lab kernel: [ 2462.588702] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Mar 13 11:07:31 do-lab kernel: [ 2462.592557] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow start
Mar 13 11:07:31 do-lab kernel: [ 2462.592561] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow done
Mar 13 11:07:31 do-lab kernel: [ 2462.592586] amdgpu 0000:04:00.0: amdgpu: GPU reset(1) succeeded!
Mar 13 11:07:31 do-lab kernel: [ 2462.592602] [drm] Skip scheduling IBs!
Mar 13 11:07:31 do-lab kernel: [ 2462.594984] [drm] Skip scheduling IBs!
Mar 13 11:07:29 do-lab wpa_supplicant[586]: message repeated 993 times: [ TDLS: Invalid frame - payloadtype=1 category=240 action=26]
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: amdgpu: amdgpu_cs_query_fence_status failed.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [4090:4090:0313/110731.561413:ERROR:shared_context_state.cc(984)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [4090:4090:0313/110731.562424:ERROR:gpu_service_impl.cc(1154)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Mar 13 11:07:31 do-lab kernel: [ 2462.623458] [drm] Skip scheduling IBs!
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595448:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595496:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595571:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595579:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595615:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595622:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595693:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595699:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
Mar 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:3997:0313/110731.601926:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=8704
Mar 13 11:07:31 do-lab wpa_supplicant[586]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Mar 13 11:07:32 do-lab wpa_supplicant[586]: message repeated 4 times: [ TDLS: Invalid frame - payloadtype=1 category=240 action=26]
Mar 13 11:07:33 do-lab google-chrome.desktop[4003]: [7987:7987:0313/110733.139290:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
Mar 13 11:07:33 do-lab wpa_supplicant[586]: TDLS: Invalid frame - payloadtype=1 category=240 action=26

Kernal Logs

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

2024-03-13T11:07:30,010881+05:00 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=22819, emitted seq=22821
2024-03-13T11:07:30,011644+05:00 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
2024-03-13T11:07:30,011911+05:00 amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
2024-03-13T11:07:30,106020+05:00 amdgpu 0000:04:00.0: amdgpu: MODE2 reset
2024-03-13T11:07:30,114011+05:00 amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded, trying to resume
2024-03-13T11:07:30,114172+05:00 [drm] PCIE GART of 1024M enabled (table at 0x000000F47FC00000).
2024-03-13T11:07:30,114254+05:00 [drm] PSP is resuming...
2024-03-13T11:07:30,136423+05:00 [drm] reserve 0xa00000 from 0xf47e000000 for PSP TMR
2024-03-13T11:07:30,702984+05:00 amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
2024-03-13T11:07:30,713658+05:00 amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
2024-03-13T11:07:30,713670+05:00 amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
2024-03-13T11:07:30,713680+05:00 amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
2024-03-13T11:07:30,714083+05:00 amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
2024-03-13T11:07:30,715481+05:00 [drm] DMUB hardware initialized: version=0x06000800
2024-03-13T11:07:31,584497+05:00 [drm] kiq ring mec 2 pipe 1 q 0
2024-03-13T11:07:31,588549+05:00 [drm] VCN decode and encode initialized successfully(under DPG Mode).
2024-03-13T11:07:31,588669+05:00 [drm] JPEG decode initialized successfully.
2024-03-13T11:07:31,588674+05:00 amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
2024-03-13T11:07:31,588677+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
2024-03-13T11:07:31,588679+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
2024-03-13T11:07:31,588681+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
2024-03-13T11:07:31,588683+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
2024-03-13T11:07:31,588685+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
2024-03-13T11:07:31,588687+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
2024-03-13T11:07:31,588689+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
2024-03-13T11:07:31,588691+05:00 amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
2024-03-13T11:07:31,588693+05:00 amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
2024-03-13T11:07:31,588695+05:00 amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
2024-03-13T11:07:31,588697+05:00 amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
2024-03-13T11:07:31,588699+05:00 amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
2024-03-13T11:07:31,588701+05:00 amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
2024-03-13T11:07:31,588702+05:00 amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
2024-03-13T11:07:31,592557+05:00 amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow start
2024-03-13T11:07:31,592561+05:00 amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow done
2024-03-13T11:07:31,592586+05:00 amdgpu 0000:04:00.0: amdgpu: GPU reset(1) succeeded!
2024-03-13T11:07:31,592602+05:00 [drm] Skip scheduling IBs!

Journalctl System Logs

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

مارچ 13 11:07:29 do-lab wpa_supplicant[586]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
مارچ 13 11:07:29 do-lab kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=22819, emitted seq=22821
مارچ 13 11:07:29 do-lab kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
مارچ 13 11:07:29 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: MODE2 reset
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded, trying to resume
مارچ 13 11:07:30 do-lab kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F47FC00000).
مارچ 13 11:07:30 do-lab kernel: [drm] PSP is resuming...
مارچ 13 11:07:30 do-lab kernel: [drm] reserve 0xa00000 from 0xf47e000000 for PSP TMR
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
مارچ 13 11:07:30 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
مارچ 13 11:07:30 do-lab kernel: [drm] DMUB hardware initialized: version=0x06000800
مارچ 13 11:07:31 do-lab kernel: [drm] kiq ring mec 2 pipe 1 q 0
مارچ 13 11:07:31 do-lab kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
مارچ 13 11:07:31 do-lab kernel: [drm] JPEG decode initialized successfully.
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow start
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow done
مارچ 13 11:07:31 do-lab kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset(1) succeeded!
مارچ 13 11:07:31 do-lab kernel: [drm] Skip scheduling IBs!
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: amdgpu: amdgpu_cs_query_fence_status failed.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [4090:4090:0313/110731.561413:ERROR:shared_context_state.cc(984)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [4090:4090:0313/110731.562424:ERROR:gpu_service_impl.cc(1154)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
مارچ 13 11:07:31 do-lab kernel: [drm] Skip scheduling IBs!
مارچ 13 11:07:31 do-lab kernel: [drm] Skip scheduling IBs!
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595448:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595496:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595571:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595579:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595615:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595622:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595693:ERROR:shared_image_interface_proxy.cc(140)] Buffer handle is null. Not creating a mailbox from it.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:4088:0313/110731.595699:ERROR:one_copy_raster_buffer_provider.cc(370)] Creation of MappableSharedImage failed.
مارچ 13 11:07:31 do-lab google-chrome.desktop[4003]: [3997:3997:0313/110731.601926:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=8704
مارچ 13 11:08:20 do-lab wpa_supplicant[586]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
مارچ 13 11:08:20 do-lab google-chrome.desktop[4003]: [7987:7987:0313/110820.150289:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
مارچ 13 11:08:20 do-lab wpa_supplicant[586]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
مارچ 1
Linux, Troubleshooting
Linux Troubleshooting
This post is licensed under CC BY 4.0 by the author.