screen goes white at plymouth w/ amdgpu sienna cichlid

Bug #1930902 reported by Liz Fong-Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-oem-5.10 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
New
Undecided
Unassigned

Bug Description

regression since 5.10.0-1026

Jun 4 07:56:37 lily kernel: [ 3.980436] amdgpu 0000:09:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Jun 4 07:56:37 lily kernel: [ 4.007921] amdgpu 0000:09:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007922] amdgpu 0000:09:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007923] amdgpu 0000:09:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007924] amdgpu 0000:09:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007925] amdgpu 0000:09:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007925] amdgpu 0000:09:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007926] amdgpu 0000:09:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007927] amdgpu 0000:09:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007928] amdgpu 0000:09:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007929] amdgpu 0000:09:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007930] amdgpu 0000:09:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007931] amdgpu 0000:09:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007932] amdgpu 0000:09:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007932] amdgpu 0000:09:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0
Jun 4 07:56:37 lily kernel: [ 4.007933] amdgpu 0000:09:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.007934] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.007935] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.007936] amdgpu 0000:09:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.007937] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.007938] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.007939] amdgpu 0000:09:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1
Jun 4 07:56:37 lily kernel: [ 4.008299] amdgpu 0000:09:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0)
Jun 4 07:56:37 lily kernel: [ 4.008308] amdgpu 0000:09:00.0: amdgpu: in page starting at address 0x0000000007000000 from client 18
Jun 4 07:56:37 lily kernel: [ 4.008311] amdgpu 0000:09:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A
Jun 4 07:56:37 lily kernel: [ 4.008314] amdgpu 0000:09:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3)
Jun 4 07:56:37 lily kernel: [ 4.008316] amdgpu 0000:09:00.0: amdgpu: MORE_FAULTS: 0x0
Jun 4 07:56:37 lily kernel: [ 4.008318] amdgpu 0000:09:00.0: amdgpu: WALKER_ERROR: 0x5
Jun 4 07:56:37 lily kernel: [ 4.008319] amdgpu 0000:09:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Jun 4 07:56:37 lily kernel: [ 4.008321] amdgpu 0000:09:00.0: amdgpu: MAPPING_ERROR: 0x1
Jun 4 07:56:37 lily kernel: [ 4.008322] amdgpu 0000:09:00.0: amdgpu: RW: 0x0
Jun 4 07:56:37 lily kernel: [ 4.008326] fbcon: Taking over console
Jun 4 07:56:37 lily kernel: [ 4.017984] [drm] Initialized amdgpu 3.40.0 20150101 for 0000:09:00.0 on minor 0

Timo Aaltonen (tjaalton)
Changed in linux-oem-5.10 (Ubuntu):
status: New → Invalid
Revision history for this message
Liz Fong-Jones (lizthegrey) wrote :

Doesn't repro with 5.11 HWE builds, so I assume it's safe to not debug this and let it go invalid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.