[nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)

Bug #1965882 reported by Daniel van Vugt
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Unassigned
Jammy
Fix Released
High
Unassigned
Kinetic
Won't Fix
High
Unassigned

Bug Description

External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. The primary GPU (i915) still works fine.

This seems to be a kernel regression...

FAIL: 5.17.0-051700drmtip20220322-generic
FAIL: 5.17.0-051700-generic
FAIL: 5.15.0-23-generic
FAIL: 5.14.21-051421-generic
PASS: 5.14.20-051420-generic
PASS: 5.14.18-051418-generic
PASS: 5.14.15-051415-generic
PASS: 5.14.10-051410-generic
PASS: 5.14.0-051400-generic
PASS: 5.13.19-051319-generic
PASS: 5.10.107-0510107-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-23-generic 5.15.0-23.23
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Tue Mar 22 16:35:58 2022
InstallationDate: Installed on 2021-11-05 (136 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
MachineType: Intel(R) Client Systems NUC9i7QNX
ProcFB:
 0 i915drmfb
 1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-23-generic N/A
 linux-backports-modules-5.15.0-23-generic N/A
 linux-firmware 20220314.gitcd01f857-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: Intel Corp.
dmi.bios.version: QXCFL579.0034.2019.1125.1436
dmi.board.name: NUC9i7QNB
dmi.board.vendor: Intel Corporation
dmi.board.version: K49245-402
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 24.33
dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX:
dmi.product.family: QN
dmi.product.name: NUC9i7QNX
dmi.product.sku: BXNUC9i7QNX
dmi.product.version: K49244-403
dmi.sys.vendor: Intel(R) Client Systems

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
tags: added: multimonitor
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
summary: - [nouveau] External monitor plugged into Nvidia GPU is all white (plus a
- little flicker)
+ [nouveau] External monitor plugged into (secondary) Nvidia GPU is all
+ white (plus a little flicker)
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Maybe this was caused by an Ubuntu config change? Building 5.14.20 and 5.14.1 from git results in failure now. Only the mainline debs of those versions succeed.

Revision history for this message
Chris Monahan (cobra-v) wrote :

Just wanted to chime in and say I am having the same issue on my Lenovo P1 which has both Intel and Nvidia cards. Ubuntu 21.10 worked flawlessly, 22.04 displays a pure white screen on my external display.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

For a variety of reasons, we don't recommend anyone use the default nouveau driver. I only opened this bug for the sake of tracking. Please open the 'Additional Drivers' app and install the proprietary Nvidia driver instead.

Revision history for this message
Chris Monahan (cobra-v) wrote :

I think what you are saying is that nouveau is not maintained by Ubuntu. I am just curious if Ubuntu made a config changed that caused this issue, or if it was an update to nouveau itself. I personally like nouveau because it allows automatic graphics switching, and the last time I tried the native Nvidia drivers, it ate a lot of battery.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The change that caused this bug is the newer kernel in Ubuntu 22.04. Not anything we did directly to affect nouveau, we just seem to have inherited a new nouveau bug. Older kernels do not have the bug.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Another DRM regression in v5.14.21: bug 1971146

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

should be easy to test with 'intel_iommu=off' on the kernel cmdline

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes! Fixed by intel_iommu=off

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
tags: added: rls-jj-incoming
no longer affects: linux
Revision history for this message
koba (kobako) wrote :

There's dmar error, i thought Device[01:00.0] may access a out-of-bound address.
[ 843.730480] DMAR: DRHD: handling fault status reg 3
[ 843.730488] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e000000 [fault reason 0x0c] non-zero reserved fields in PTE
[ 843.730494] DMAR: DRHD: handling fault status reg 3
[ 843.730496] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e016000 [fault reason 0x0c] non-zero reserved fields in PTE
[ 843.730499] DMAR: DRHD: handling fault status reg 3
[ 843.730501] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e01e000 [fault reason 0x0c] non-zero reserved fields in PTE
[ 843.730505] DMAR: DRHD: handling fault status reg 3

Could someone dump
sudo cat /sys/bus/pci/devices/0000\:01\:00.0/iommu/intel-iommu/*
sudo cat /sys/bus/pci/devices/0000\:01\:00.0/iommu_group/reserved_regions
sudo cat /sys/bus/pci/devices/0000\:01\:00.0/iommu_group/type

Revision history for this message
koba (kobako) wrote (last edit ):

could someone help to verify this kernel on target w/o intel_iommu=off?thanks
https://drive.google.com/drive/folders/1c1p8y265T9urgOwKoJLXaiGUrlKpJlKO?usp=sharing

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you upload it to a more familiar/trustworthy URL?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Confirmed that test kernel 5.14.0-1033lpv1967153-oem does not have the bug. Even without intel_iommu=off.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in linux (Ubuntu Jammy):
importance: Undecided → High
status: New → Fix Released
Changed in linux (Ubuntu Kinetic):
status: Triaged → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Verified fixed in 5.15.0-40-generic

Although my nouveau setup is seemingly less reliable than it used to be, there is no white screen and I eventually got a working signal from the Nvidia card.

tags: added: iommu
Revision history for this message
Heinrich Schuchardt (xypron) wrote :

intel_iommu=off may result in a security risk as PCIe devices can access all of the RAM. intel_iommu=igfx_off should be enough to resolve issues with GPUs.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Verified:

FAIL: intel_iommu=on
PASS: intel_iommu=off
PASS: intel_iommu=igfx_off
PASS: No parameter required in 5.15.0-40-generic

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test the kernel, which adds the affected GFX to IOMMU quirk list:
https://people.canonical.com/~khfeng/gfx-no-dmar/

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

See also bug 2006370

Revision history for this message
Alex (alyieks) wrote (last edit ):

Comment number three [driver update to tested] provides error (see the screenshot)
This window with the error cannot be closed (bug); I tried everything, including pressing close the window button.

Revision history for this message
Alex (alyieks) wrote :

intel_iommu=igfx_off - not helped (input goes OK, but the bug is still here)

Revision history for this message
Alex (alyieks) wrote :

Suggested solution:
https://people.canonical.com/~khfeng/gfx-no-dmar/
=>
linux-modules-extra-5.15.0-1050-generic_5.15.0-1050.56_amd64.deb
Error with no description (screenshot attached)

Revision history for this message
Alex (alyieks) wrote :

PS: The second attempt to follow to the comment number three: Error with no description (see the screenshot)
It then automatically selects the last option (no other option end with success).

Revision history for this message
Alex (alyieks) wrote :

My kernel is: 5.19.0-35-generic

Revision history for this message
Alex (alyieks) wrote :

Hi everyone,
It seems my bug is unsolvable. I will hope for a better Linux (Ubuntu) version since no other choices exist.
This bug makes me a very rare Linux user (I can't work on just one monitor).
So, Happy Easter Everyone!
Best Wishes,
Alex.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is solved. The above comments probably belong in bug 2006370, not here.

Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.

Changed in linux (Ubuntu Kinetic):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.