[Bug]: https://rank.top/ causes amdgpu page fault and driver reset

Open
#457 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux
Domain
backend

Research direction

Start by reproducing the failure at https://rank.top/bot/sofi/vote with an AMD GPU, then compare behavior with Chrome and an empty Helium profile; those checks are not marked as completed. The issue includes dmesg logs showing an amdgpu page fault during the vote action, but names no project files or tests. Done means identifying a reproducible cause and fixing the GPU reset.

Written by the indexing model from the issue text.

Description

bug
Version

Version 0.20.1.1 (Official Build, Chromium 156.0.8078.47) rpm (x86_64)

Have you tested that this is not an upstream issue or an issue with your configuration?
  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description

site causes amdgpu page fault and driver reset

How to Reproduce?
  1. open https://rank.top/bot/sofi/vote
  2. press "power vote"
Actual behavior

pc hangs and my igpu performs a reset

Expected behavior

page to be ok

Additional context

dmesg log:

[ 9049.069147] amdgpu 0000:06:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:140)
[ 9049.069154] amdgpu 0000:06:00.0:  Process helium pid 27536 thread helium:cs0 pid 27551
[ 9049.069157] amdgpu 0000:06:00.0:   in page starting at address 0x0000000039ea0000 from client 10
[ 9049.069160] amdgpu 0000:06:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601430
[ 9049.069162] amdgpu 0000:06:00.0: 	Faulty UTCL2 client ID: SQC (data) (0xa)
[ 9049.069164] amdgpu 0000:06:00.0: 	MORE_FAULTS: 0x0
[ 9049.069166] amdgpu 0000:06:00.0: 	WALKER_ERROR: 0x0
[ 9049.069167] amdgpu 0000:06:00.0: 	PERMISSION_FAULTS: 0x3
[ 9049.069168] amdgpu 0000:06:00.0: 	MAPPING_ERROR: 0x0
[ 9049.069170] amdgpu 0000:06:00.0: 	RW: 0x0
[ 9051.088602] amdgpu 0000:06:00.0: Dumping IP State
[ 9051.090379] amdgpu 0000:06:00.0: Dumping IP State Completed
[ 9051.090395] amdgpu 0000:06:00.0: [drm] AMDGPU device coredump file has been created
[ 9051.090397] amdgpu 0000:06:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[ 9051.090398] amdgpu 0000:06:00.0: ring gfx_0.0.0 timeout, signaled seq=1287998, emitted seq=1288000
[ 9051.090400] amdgpu 0000:06:00.0:  Process helium pid 27536 thread helium:cs0 pid 27551
[ 9051.090402] amdgpu 0000:06:00.0: Starting gfx_0.0.0 ring reset
[ 9051.091136] amdgpu 0000:06:00.0: Ring gfx_0.0.0 reset succeeded
[ 9051.091138] amdgpu 0000:06:00.0: [drm] device wedged, but no recovery needed
[10318.945169] amdgpu 0000:06:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:366)
[10318.945174] amdgpu 0000:06:00.0:  Process helium pid 89417 thread helium:cs0 pid 89420
[10318.945176] amdgpu 0000:06:00.0:   in page starting at address 0x00009fff44c42000 from client 10
[10318.945179] amdgpu 0000:06:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
[10318.945180] amdgpu 0000:06:00.0: 	Faulty UTCL2 client ID: SQC (data) (0xa)
[10318.945181] amdgpu 0000:06:00.0: 	MORE_FAULTS: 0x0
[10318.945183] amdgpu 0000:06:00.0: 	WALKER_ERROR: 0x0
[10318.945184] amdgpu 0000:06:00.0: 	PERMISSION_FAULTS: 0x3
[10318.945185] amdgpu 0000:06:00.0: 	MAPPING_ERROR: 0x0
[10318.945186] amdgpu 0000:06:00.0: 	RW: 0x0
[10320.968823] amdgpu 0000:06:00.0: Dumping IP State
[10320.971697] amdgpu 0000:06:00.0: Dumping IP State Completed
[10320.971713] amdgpu 0000:06:00.0: [drm] AMDGPU device coredump file has been created
[10320.971714] amdgpu 0000:06:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[10320.971716] amdgpu 0000:06:00.0: ring gfx_0.1.0 timeout, signaled seq=2277377, emitted seq=2277379
[10320.971718] amdgpu 0000:06:00.0:  Process kwin_wayland pid 4001 thread kwin_wayla:cs0 pid 4082
[10320.971720] amdgpu 0000:06:00.0: Starting gfx_0.1.0 ring reset
[10322.975523] amdgpu 0000:06:00.0: MES failed to respond to msg=RESET
[10322.975527] amdgpu 0000:06:00.0: failed to reset legacy queue
[10322.975529] amdgpu 0000:06:00.0: Ring gfx_0.1.0 reset failed
[10322.975532] amdgpu 0000:06:00.0: GPU reset begin!. Source:  1
[10325.048276] amdgpu 0000:06:00.0: MES failed to respond to msg=REMOVE_QUEUE
[10325.048280] amdgpu 0000:06:00.0: failed to unmap legacy queue
[10327.052110] amdgpu 0000:06:00.0: MES failed to respond to msg=REMOVE_QUEUE
[10327.052114] amdgpu 0000:06:00.0: failed to unmap legacy queue
[10327.259167] [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
[10327.260784] amdgpu 0000:06:00.0: MODE2 reset
[10327.296798] amdgpu 0000:06:00.0: GPU reset succeeded, trying to resume
[10327.297541] amdgpu 0000:06:00.0: [drm] PCIE GART of 512M enabled (table at 0x000000807FD00000).
[10327.297619] amdgpu 0000:06:00.0: SMU is resuming...
[10327.299600] amdgpu 0000:06:00.0: SMU is resumed successfully!
[10327.307006] amdgpu 0000:06:00.0: [drm] DMUB hardware initialized: version=0x08006200
[10327.532297] amdgpu 0000:06:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[10327.532304] amdgpu 0000:06:00.0: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
[10327.532306] amdgpu 0000:06:00.0: ring comp_1.0.0 uses VM inv eng 4 on hub 0
[10327.532307] amdgpu 0000:06:00.0: ring comp_1.1.0 uses VM inv eng 6 on hub 0
[10327.532309] amdgpu 0000:06:00.0: ring comp_1.2.0 uses VM inv eng 7 on hub 0
[10327.532310] amdgpu 0000:06:00.0: ring comp_1.3.0 uses VM inv eng 8 on hub 0
[10327.532312] amdgpu 0000:06:00.0: ring comp_1.0.1 uses VM inv eng 9 on hub 0
[10327.532313] amdgpu 0000:06:00.0: ring comp_1.1.1 uses VM inv eng 10 on hub 0
[10327.532314] amdgpu 0000:06:00.0: ring comp_1.2.1 uses VM inv eng 11 on hub 0
[10327.532316] amdgpu 0000:06:00.0: ring comp_1.3.1 uses VM inv eng 12 on hub 0
[10327.532317] amdgpu 0000:06:00.0: ring sdma0 uses VM inv eng 13 on hub 0
[10327.532319] amdgpu 0000:06:00.0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[10327.532320] amdgpu 0000:06:00.0: ring jpeg_dec uses VM inv eng 1 on hub 8
[10327.532321] amdgpu 0000:06:00.0: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
[10327.535207] amdgpu 0000:06:00.0: GPU reset(3) succeeded!
[10327.535215] amdgpu 0000:06:00.0: [drm] device wedged, but no recovery needed
Dominant language
Shell
Stars
1.1k
Forks
63
Avg merge
28m
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.