Ubuntu
linux-raspi package

Newer kernel still has no display w/ KMS enabled

Bug #1945842 reported by satmandu on 2021-10-02

This bug report is a duplicate of: Bug #1944397: HDMI does not display anything with Impish RPi desktop image. Edit Remove

14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	linux-raspi (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

This is using KMS, not fKMS...

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-raspi (not installed)
ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
Uname: Linux 5.13.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu69
Architecture: arm64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: satadru 1164 F.... pulseaudio
/dev/snd/pcmC1D0p: satadru 1164 F...m pulseaudio
/dev/snd/controlC0: satadru 1164 F.... pulseaudio
CasperMD5CheckResult: unknown
Date: Fri Oct 1 20:22:10 2021
ImageMediaBuild: 20210421
Lspci-vt: -[0000:00]---00.0-[01]----00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
TERM=vt100
XDG_RUNTIME_DIR=<set>
PATH=(custom, user)
ProcFB: 0 vc4drmfb
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:09:99:D7 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1 fsck.mode=force fsck.repair=yes
RelatedPackageVersions:
linux-restricted-modules-5.13.0-1008-raspi N/A
linux-backports-modules-5.13.0-1008-raspi N/A
linux-firmware 1.201
SourcePackage: linux-raspi
UpgradeStatus: Upgraded to impish on 2021-08-17 (45 days ago)
acpidump:

Tags:

Revision history for this message

satmandu (satadru-umich) wrote on 2021-10-02:

#1

AlsaInfo.txt Edit (14.0 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (643 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (131.5 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (282 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (362 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (495 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (13.5 KiB, text/plain; charset="utf-8")
PaInfo.txt Edit (52.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (775 bytes, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (271 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.9 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (21.7 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (113 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (318.6 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (329.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-10-04:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-raspi (Ubuntu):
status:	New → Confirmed

Revision history for this message

Roger James (rogerjames99) wrote on 2021-10-04:

#3

I am also seeing this after an automatic update from linux-image-5.11.0-1017-raspi to linux-image-5.11.0-1019-raspi. The display output is lost very early on in the boot process.

The only way I could get round it was to roll the kernel back to 5.11.0-2017.

Roger

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-10-05:

#4

Sounds like bug 1944397 so please wait till that is fixed and then log any new bugs you find.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-10-05:

#5

Oh, 5.13.0-1008.9-raspi is meant to contain the fix already. Still, it should be discussed in bug 1944397.

Revision history for this message

Roger James (rogerjames99) wrote on 2021-10-05:

#6

Daniel,

I am not sure this is the same bug. I am getting this in Hirsute after a recent kernel update.

The warnings appear to be in a different area than those in #1944397

3437:Sep 29 15:33:29 brubeck kernel: [ 16.098988] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_disable+0x424/0x49c [vc4] 3488:Sep 29 15:33:29 brubeck kernel: [ 16.100017] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 3550:Sep 29 15:33:29 brubeck kernel: [ 16.100691] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_powerdown+0x178/0x1c0 [vc4] 3602:Sep 29 15:33:29 brubeck kernel: [ 16.101324] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_phy_disable+0x198/0x220 [vc4] 3657:Sep 29 15:33:29 brubeck kernel: [ 16.101969] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_phy_disable+0x190/0x220 [vc4] 4621:Sep 29 15:33:37 brubeck kernel: [ 25.770372] WARNING: CPU: 1 PID: 1021 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 4836:Sep 29 15:33:40 brubeck kernel: [ 28.247538] WARNING: CPU: 3 PID: 1111 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 5122:Sep 29 15:33:44 brubeck kernel: [ 31.914079] WARNING: CPU: 2 PID: 1111 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 5162:Sep 29 15:33:44 brubeck kernel: [ 32.528456] WARNING: CPU: 0 PID: 1111 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] ~

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-10-06:

#7

Roger,

The kernel logs of bug 1945535 and bug 1945805 look like that and they are both currently marked as duplicates of 1944397. In all cases the vc4 HDMI errors are recurring and take multiple forms even on the same machine.

Also, if you want to report new issues in future then please open your own new bugs.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1944397 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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