Bug 2230615

Summary: 6.4.8-200.fc38.x86_64 breaks hardware acceleration (and apps that use it)
Product: [Fedora] Fedora Reporter: oli <olze>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 38CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarod, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
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
none
dmesg with errors ... again none

Description oli 2023-08-09 18:07:42 UTC 
1. Please describe the problem:
i upgraded a few days ago the kernel and turned on hw acceleration after the new linux firmware arrived. now a new kernel arrived and hw acceleration is broken - again...

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

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 :
6.4.8-200.fc38.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
yes, always
open chromium and visit e.g. youtube, most parts of the website are simply missing
disabling hw acceleration "fixes" it 

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``:
dont know

6. Are you running any modules that not shipped with directly Fedora's kernel?:
no

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.


Reproducible: Always
Comment 1 oli 2023-08-09 18:08:06 UTC 
Created attachment 1982612 [details]
dmesg
Comment 2 oli 2023-08-09 18:09:23 UTC 
i dont want to flame the amd guys but... i really never had such hardcore problems with nvidia cards, never... at least both screens are now finally working
Comment 3 oli 2023-08-09 20:01:21 UTC 
Created attachment 1982636 [details]
dmesg with errors ... again

attached a funny dmesg with some errors :(