Bug 1902425

Summary: nouveau 0000:01:00.0: DRM: base-0: timeout
Product: [Fedora] Fedora Reporter: Sam Varshavchik <mrsam>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: acaringi, adscvr, airlied, bskeggs, fernandosj2k4, hdegoede, hedayatv, itamar, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, mjg59, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-14 12:21:21 UTC 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
nouveau driver errors
none
More nouveau errors
none
Still more nouveau errors none

Description Sam Varshavchik 2020-11-28 19:12:22 UTC
Created attachment 1734498 [details]
nouveau driver errors

1. Please describe the problem:

Kernels after kernel-5.8.16-300.fc33.x86_64 randomly result in display freezes, with the nouveau driver spewing errors in syslog.

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

Just reproduced it with kernel-5.9.10-200.fc33.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 :

Probably kernel-5.8.18-300.fc33.x86_64. kernel-5.8.16-300.fc33.x86_64 seems to work for me, the next kernel I installed was kernel-5.8.18-300.fc33.x86_64, and issues started manifesting themselves.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Nothing specific. Freezes occur randomly

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

kernel-5.9.10-200.fc33.x86_64 was just installed

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.

5.9.10 generated an avalanche of:

Nov 28 13:52:28 thinkpad kernel: nouveau 0000:01:00.0: DRM: base-0: timeout
Nov 28 13:52:30 thinkpad kernel: nouveau 0000:01:00.0: DRM: base-0: timeout
Nov 28 13:52:32 thinkpad kernel: nouveau 0000:01:00.0: DRM: base-0: timeout
Nov 28 13:52:34 thinkpad kernel: nouveau 0000:01:00.0: DRM: base-0: timeout

Going to attach additional logs, from various kernels of 5.18.16, with other errors.

The nouveau driver is controlling an old-ish

1:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [Quadro 1000M] (rev a1) (prog-if 00 [VGA controller])

chip, old enough to be fully supported by x.org's nouveau driver.

memtest86 completed a full testing cycle without any errors.

Comment 1 Sam Varshavchik 2020-11-28 19:12:59 UTC
Created attachment 1734499 [details]
More nouveau errors

Comment 2 Sam Varshavchik 2020-11-28 19:14:54 UTC
Created attachment 1734500 [details]
Still more nouveau errors

Comment 3 fernandosj2k4 2020-12-03 14:13:50 UTC
I have the same problem, with kernel 5.9.11-200.fc33.x86_64 and video card: VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430]

Comment 4 Sam Varshavchik 2020-12-03 16:03:21 UTC
Also happens with

06:00.0 VGA compatible controller: NVIDIA Corporation GT200b [GeForce GTX 285] (rev a1) (prog-if 00 [VGA controller])

Kernel 5.8.16-300.fc33.x86_64 is stable for me, on both systems.

Comment 5 Hedayat Vatankhah 2020-12-14 12:21:21 UTC

*** This bug has been marked as a duplicate of bug 1891084 ***