Bug 2222774

Summary: Freeze after update - radeon: ring 0 stalled for more than xxxmsec
Product: [Fedora] Fedora Reporter: Afox <remasch>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 38CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, remasch, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg.txt none

Description Afox 2023-07-13 16:50:35 UTC
Created attachment 1975631 [details]
dmesg.txt

1. Please describe the problem:
System freezes after login. 

2. What is the Version-Release number of the kernel:
6.3.12-200.fc38

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
The system works fine after installing from ISO "Fedora-Workstation-Live-x86_64-38-1.6.iso".

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
After installation of the named ISO you simply update and restart.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
-

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No additional software is installed.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.