CPU pipe A FIFO underrun

Bug #1971428 reported by Øystein Andresen-Sund
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upgraded from Ubuntu 20.04 to 22.04 at the release date.
I get a blinking screen about 2-3 times a day. Dmesg shows the following:
i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

Lenovo Thinkpad T480s connected to Lenovo Thinkpad Basic Docking Station, type 40AG.
I'm not doing anything special when this happens. I've been using the same monitor, dock and cables for several years.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: oystein 6834 F.... wireplumber
 /dev/snd/controlC1: oystein 6834 F.... wireplumber
 /dev/snd/controlC0: oystein 6834 F.... wireplumber
 /dev/snd/seq: oystein 6832 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 3 14:46:03 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-08-03 (273 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: LENOVO 20L8002VMX
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e9eb1db1-6947-4826-85ca-b36e8bdf8f75 ro quiet splash i915.enable_psr=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-21 (11 days ago)
WifiSyslog:

dmi.bios.date: 11/17/2021
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET72W (1.49 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8002VMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias: dmi:bvnLENOVO:bvrN22ET72W(1.49):bd11/17/2021:br1.49:efr1.22:svnLENOVO:pn20L8002VMX:pvrThinkPadT480s:rvnLENOVO:rn20L8002VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8002VMX
dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

Revision history for this message
Øystein Andresen-Sund (svampebob1) wrote :
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
Revision history for this message
Bas Janssen (watcheroftheskies) wrote :

Same here on my Dell XPS 13 with i915 graphics. Occasionally it gets worse: my screen goes completely black and won't come back on unless I switch to an external monitor and back, or reboot.

Revision history for this message
Damián Bacalov (bdamian) wrote :

Same as Bas Janssen here, Dell XPS 13 with i915. No devices attached. It is a fresh install, not an upgrade.

Revision history for this message
Alexander Lazarević (e11bits) wrote :

Same here on Lenovo Thinkpad T490 with i915 and external monitor attached via Thunderbolt. External monitor goes black several times a day.

Only when I move the mouse cursor into the lower 10% part of the monitor screen. It stays black if I don't move the mouse. Once I move the mouse, the screen comes back. It does not always happen in that lower 10% part. But when it happens, the cursor is in that area.

Around that time I see in dmesg:
i915 0000:00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun

I tried a fix from here:
https://bbs.archlinux.org/viewtopic.php?id=263720

But adding the kernel parameter intel_idle.max_cstate=4 did not help in my case.

Revision history for this message
Bas Janssen (watcheroftheskies) wrote :

Taking a screenshot definitely triggers this for me, although it also happens on other occasions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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