Bug 2058535 - AMDGPU page fault after Login using Mesa 21.3.7
Summary: AMDGPU page fault after Login using Mesa 21.3.7
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 35
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-25 09:30 UTC by Marcel
Modified: 2022-03-03 21:17 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-03 21:17:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Mesa 21.3.7 dmesg log (98.16 KB, text/plain)
2022-02-25 09:30 UTC, Marcel
no flags Details

Description Marcel 2022-02-25 09:30:02 UTC
Created attachment 1863287 [details]
Mesa 21.3.7 dmesg log

Description of problem:
Computer crashes right after Login because of a page fault using Mesa 21.3.7 with a AMD Radeon RX 6500 XT


Version-Release number of selected component (if applicable): 
Mesa 21.3.7
Kernel 5.16.2


How reproducible:
Always

Steps to Reproduce:
1. Login on a computer with a AMD Radeon RX 6500 XT

Actual results:
Computer crashes


Expected results:
Computer should not crash


Additional info:
- The GPU is a new one, maybe it isn't supported yet?
- Kernel is 5.16.2, can't upgrade it because of a similar crash for Kernel > 5.16.2

Comment 1 Kamil Páral 2022-03-03 10:04:45 UTC
Marcel, what happens if you install latest mesa and kernel together, does it help?
Also, you can try the latest development snapshot for kernel 5.17 here:
https://koji.fedoraproject.org/koji/packageinfo?packageID=8

Comment 2 Marcel 2022-03-03 21:17:41 UTC
Just tried Kernel 5.16.11 + Mesa 21.3.7 and it crashes, but because of the Kernel bug.
After booting with Kernel 5.16.2 + Mesa 21.3.7 it worked fine ?. Maybe I mixed something up while testing and got confused about the versions. Sorry. 
Closing this one.


Note You need to log in before you can comment on or make changes to this bug.