Bug 2192908

Summary: Quadro FX 380 don't work after kernel update 6.1 -> 6.2
Product: [Fedora] Fedora Reporter: Amin <amin>
Component: xorg-x11-drv-nouveauAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 37CC: airlied, ajax, bskeggs, lyude, redhat
Target Milestone: ---Keywords: Desktop, Regression, Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-15 12:12:59 UTC 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
Logs from problem host - Quadro FX 380 + nouveau + Kernel 6.2.13 none

Description Amin 2023-05-03 13:22:13 UTC
On new kernels 6.2.* GPU Quadro FX 380 don't work correctly with nouveau driver.
On old kernels 6.1.* this GPU correct uner nouveau driver absolutely correct.



Reproducible: Always

Steps to Reproduce:
1. Fedora 37 with NVIDIA G96GL [Quadro FX 380] (rev a1) and 50" big TV as HDMI-display - work correct under kernel 6.1.11
2. Update kernel to 6.2* - 6.2.10 ... 6.2.13 and reboot
3. see graphical artefacts on display at attempt start sddm / lxdm
4. Reboot back to kernel 6.1.11 - GPU work correctly.
Actual Results:  
GPU Quadro FX 380 can't work in graphical mode with kernels 6.2.*

Expected Results:  
GPU Quadro FX 380 must work in graphical mode with kernels 6.2.* same as with kernels 6.1.*

I can try collect all related logs and attach this later.

Comment 1 Amin 2023-05-03 13:27:45 UTC
Created attachment 1961963 [details]
Logs from problem host - Quadro FX 380 + nouveau + Kernel 6.2.13

Logs

# cat bootlog-kernel-6.2.13-nouveau-QuadroFX380.txt | wc -l
4082

# cat bootlog-kernel-6.2.13-nouveau-QuadroFX380.txt | grep nouveau | wc -l
1666

Too many nouveau-related messages

Comment 2 Amin 2023-05-03 13:32:08 UTC
Comment on attachment 1961963 [details]
Logs from problem host - Quadro FX 380 + nouveau + Kernel 6.2.13

$ cat bootlog-kernel-6.2.13-nouveau-QuadroFX380.txt | grep nouveau | grep ERROR
мая 03 16:23:05 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 3 [RESERVED_METHOD] 00 [] chid 0 mthd 05c0 data 00001201
мая 03 16:23:05 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000002
мая 03 16:23:39 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:23:43 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:23:54 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:04 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:17 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:19 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:21 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:24 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:25 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 3 [RESERVED_METHOD] 00 [] chid 0 mthd 05c0 data 00000000
мая 03 16:24:25 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 3 [RESERVED_METHOD] 00 [] chid 0 mthd 05c0 data 00003201
мая 03 16:24:25 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000002
мая 03 16:24:30 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:32 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:34 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000
мая 03 16:24:36 WebaCCTVMon kernel: nouveau 0000:01:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000000

Comment 3 redhat 2023-08-22 17:12:04 UTC
I can confirm that switching from kernel 5.19.0-32-generic to kernel 6.2.0-26-generic breaks my video on Quadro FX 1800 using nouveau driver.


Caveat: I just hit this on ubuntu and using a Quadro FX 1800. Not redhat, but I still think it's an interesting datapoint.

Comment 4 Aoife Moloney 2023-11-23 01:42:53 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-01-15 12:12:59 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.