Bug #1946368 “HDMI output freezes under current/proposed impish ...” : Bugs : linux-raspi package : Ubuntu

Revision history for this message

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

#1

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

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

Revision history for this message

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

#2

If the issue is specific to atomic KMS then you can turn that off in /etc/environment:

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

which might provide a workaround.

Revision history for this message

fprietog (fprietog) wrote on 2021-10-09:

#3

I can confirm this -nasty- bug. It happens in X11 and wayland sessions.

The workaround of changing in /boot/firmware/config.txt:
dtoverlay=vc4-kms-v3d

To:
dtoverlay=vc4-fkms-v3d

Solves the problem for me.

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-10 (last edit on 2021-10-10):

#4

Setting fkms instead of kms bypasses the problem and is a solution at the moment.
However, the error with kms is not fixed.
Ubuntu Budgie 21.10 offers this change from kms to fkms with the tool "Budgie ARM and Pi" and you don’t have to edit the entry via config.txt.

Revision history for this message

William Wilson (jawn-smith) wrote on 2021-10-10:

#5

I have found some more detail about this bug. When I am on a high resolution/frame rate monitor (2560x1440@144Hz) I see this bug on just about every single boot. I can't get past the plymouth screen before HDMI crashes with the flip_done error message. This is the case on both hirsute and impish. I have tried kernels from 5.11.0-1007 to the mainline 5.15 and get the same error. Switching to fake kms resolves the issue regardless of kernel.

When I switch to using my TV (1920x1080@60) I have a hard time recreating this issue. It takes playing multiple videos simultaneously and dragging them around all over the screen to trigger the flip_done crash.

Interestingly, I tried a third monitor that is 2560x1440 but with a lower max refresh rate (60Hz). It displayed behavior similar to the 1080p TV I used. That is, this issue was difficult to recreate.

So the only thing I can think of that is different with the monitor where I am able to recreate this easily is the max refresh rate. I find that odd as I think the Pi doesn't go over 60 Hz anyway, but that's about the only difference I can see.

Revision history for this message

fprietog (fprietog) wrote on 2021-10-10:

#6

In my case I use a 1920x1080@60 monitor:
- Using wayland session if I just try to move an app in the apps drawer it hangs inmediately.
- Using X11 session it takes more time to hang, but it's just a matter of time.

Revision history for this message

Dave Jones (waveform) wrote on 2021-10-11:

#7

To summarize the current findings after several days of testing:

* In all monitors the freeze manifests the same, with the same dmesg output
* Some monitors, in particular it seems higher-frame-rate (100+Hz) monitors (but by no means exclusive to these) trigger the freeze quite easily, often before the login screen even appears
* Other monitors, in particular lower-frame-rate (60Hz) monitors do trigger the freeze, but only after some activity
* A few monitor(s) (so far only a 60Hz one) don't trigger the freeze at all (thanks to brian-murray for additional testing on this)

Over the weekend I tested the 5.11.0-1019 and 5.11.0-1021 linux-raspi kernels from hirsute, installing them onto the impish image. With my (60Hz) monitor, I was unable to reproduce the crash with either of these, but jawn-smith *did* reproduce the issue with the hirsute kernel on his high-frame-rate monitor.

In other words, even rolling all the way back to the hirsute kernel won't eliminate the freeze for everyone. The good news is that fkms does appear to reliably work around the issue (thanks for knoedelfan and fprietog for the reports in #3 and #4), although that in itself comes with its own issues (though none as severe as the display freezing).

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-11: Re: [Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels

#8

Download full text (10.8 KiB)

Question - should the default be changed from KMS to FKMS for the
impish release? It seems that freezing is severe enough either not to
ship / or ship with a less than perfect default until more time can be
devoted to investigate and resolve.

On Mon, 11 Oct 2021 at 15:50, Dave Jones <email address hidden> wrote:
>
> To summarize the current findings after several days of testing:
>
> * In all monitors the freeze manifests the same, with the same dmesg output
> * Some monitors, in particular it seems higher-frame-rate (100+Hz) monitors (but by no means exclusive to these) trigger the freeze quite easily, often before the login screen even appears
> * Other monitors, in particular lower-frame-rate (60Hz) monitors do trigger the freeze, but only after some activity
> * A few monitor(s) (so far only a 60Hz one) don't trigger the freeze at all (thanks to brian-murray for additional testing on this)
>
> Over the weekend I tested the 5.11.0-1019 and 5.11.0-1021 linux-raspi
> kernels from hirsute, installing them onto the impish image. With my
> (60Hz) monitor, I was unable to reproduce the crash with either of
> these, but jawn-smith *did* reproduce the issue with the hirsute kernel
> on his high-frame-rate monitor.
>
> In other words, even rolling all the way back to the hirsute kernel
> won't eliminate the freeze for everyone. The good news is that fkms does
> appear to reliably work around the issue (thanks for knoedelfan and
> fprietog for the reports in #3 and #4), although that in itself comes
> with its own issues (though none as severe as the display freezing).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
> HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
> Confirmed
> Status in linux-raspi source package in Impish:
> Confirmed
>
> Bug description:
> Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
> for the Ubuntu Pi pre-installed desktop impish release, the HDMI
> output occasionally freezes. A known workaround at this time is to
> change the following line in /boot/firmware/config.txt:
>
> dtoverlay=vc4-kms-v3d
>
> To the following:
>
> dtoverlay=vc4-fkms-v3d
>
> In other words, to use the "fake" KMS overlay (fkms) instead of the
> "full" KMS overlay (kms).
>
> I've been unable to determine a reliable method of guaranteeing a
> freeze, but it appears to occur much more readily when video playback
> is occurring, and when other interactions (especially moving windows
> around, minimizing, restoring) occurs simultaneously. Display suspend
> also periodically causes the same hang, which made me suspect this
> might be related to #1944397 but it appears that had a separate cause
> (now resolved).
>
> The following dmesg outputs have been observed immediately after the
> display hang; this one from 1007.8:
>
> [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
> mmit wait timed out
> ...

Question - should the default be changed from KMS to FKMS for the
impish release?  It seems that freezing is severe enough either not to
ship / or ship with a less than perfect default until more time can be
devoted to investigate and resolve.

On Mon, 11 Oct 2021 at 15:50, Dave Jones <1946368@bugs.launchpad.net> wrote:
>
> To summarize the current findings after several days of testing:
>
> * In all monitors the freeze manifests the same, with the same dmesg output
> * Some monitors, in particular it seems higher-frame-rate (100+Hz) monitors (but by no means exclusive to these) trigger the freeze quite easily, often before the login screen even appears
> * Other monitors, in particular lower-frame-rate (60Hz) monitors do trigger the freeze, but only after some activity
> * A few monitor(s) (so far only a 60Hz one) don't trigger the freeze at all (thanks to brian-murray for additional testing on this)
>
> Over the weekend I tested the 5.11.0-1019 and 5.11.0-1021 linux-raspi
> kernels from hirsute, installing them onto the impish image. With my
> (60Hz) monitor, I was unable to reproduce the crash with either of
> these, but jawn-smith *did* reproduce the issue with the hirsute kernel
> on his high-frame-rate monitor.
>
> In other words, even rolling all the way back to the hirsute kernel
> won't eliminate the freeze for everyone. The good news is that fkms does
> appear to reliably work around the issue (thanks for knoedelfan and
> fprietog for the reports in #3 and #4), although that in itself comes
> with its own issues (though none as severe as the display freezing).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
>   HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
>   Confirmed
> Status in linux-raspi source package in Impish:
>   Confirmed
>
> Bug description:
>   Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
>   for the Ubuntu Pi pre-installed desktop impish release, the HDMI
>   output occasionally freezes. A known workaround at this time is to
>   change the following line in /boot/firmware/config.txt:
>
>   dtoverlay=vc4-kms-v3d
>
>   To the following:
>
>   dtoverlay=vc4-fkms-v3d
>
>   In other words, to use the "fake" KMS overlay (fkms) instead of the
>   "full" KMS overlay (kms).
>
>   I've been unable to determine a reliable method of guaranteeing a
>   freeze, but it appears to occur much more readily when video playback
>   is occurring, and when other interactions (especially moving windows
>   around, minimizing, restoring) occurs simultaneously.  Display suspend
>   also periodically causes the same hang, which made me suspect this
>   might be related to #1944397 but it appears that had a separate cause
>   (now resolved).
>
>   The following dmesg outputs have been observed immediately after the
>   display hang; this one from 1007.8:
>
>   [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
>   mmit wait timed out
>   [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
>   done timed out
>   [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
>   ] commit wait timed out
>   [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [  534.250685] ------------[ cut here ]------------
>   [  534.250701] refcount_t: underflow; use-after-free.
>   [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
>   [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm
>    btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C)
>    snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi snd_seq_midi_event bcm2835_codec(C) bcm
>   2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig
>   videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_common videodev snd_seq_devi
>   ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem uio_pdrv_genirq uio sch_fq_
>   codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress hid_generic usbhid raid
>   6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core gpu_sched crct10dif_ce i2c_
>   brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci xhci_pci_renesas sysfillrect sysimgbl
>   t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
>   [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: G        WC        5.13.0-1007-raspi #8-Ubuntu
>   [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
>   [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
>   [  534.251239] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
>   [  534.251248] pc : refcount_dec_not_one+0xa0/0xbc
>   [  534.251257] lr : refcount_dec_not_one+0xa0/0xbc
>   [  534.251265] sp : ffff8000118cbb50
>   [  534.251269] x29: ffff8000118cbb50 x28: ffff6cf7ee894400 x27: ffff6cf80502e000
>   [  534.251285] x26: ffff6cf80502e000 x25: 0000000000000006 x24: ffff6cf7ee94c500
>   [  534.251300] x23: ffffa94dff246018 x22: ffff6cf833068880 x21: ffff6cf805027c80
>   [  534.251314] x20: ffff6cf88ead75ac x19: ffff6cf88ead7400 x18: 0000000000000000
>   [  534.251328] x17: 0000000000000000 x16: ffffa94e0a243314 x15: 0000000000000000
>   [  534.251342] x14: 0000000000000000 x13: 0000000000000030 x12: ffff800010035000
>   [  534.251356] x11: ffffa94e0b30dfd0 x10: 00000000fffff000 x9 : ffffa94e09d09f54
>   [  534.251370] x8 : 00000000ffffefff x7 : ffffa94e0b30dfd0 x6 : 0000000000000000
>   [  534.251384] x5 : ffff6cf8b799f948 x4 : 0000000000000000 x3 : 0000000000000027
>   [  534.251397] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff6cf800abec80
>   [  534.251411] Call trace:
>   [  534.251416]  refcount_dec_not_one+0xa0/0xbc
>   [  534.251424]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
>   [  534.251473]  vc4_cleanup_fb+0x3c/0x4c [vc4]
>   [  534.251518]  drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper]
>   [  534.251604]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
>   [  534.251648]  commit_tail+0xac/0x190 [drm_kms_helper]
>   [  534.251723]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
>   [  534.251796]  drm_atomic_commit+0x58/0x70 [drm]
>   [  534.251936]  atomic_remove_fb+0x2a8/0x2f4 [drm]
>   [  534.252073]  drm_framebuffer_remove+0x164/0x18c [drm]
>   [  534.252209]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
>   [  534.252346]  process_one_work+0x200/0x4d0
>   [  534.252359]  worker_thread+0x2c8/0x470
>   [  534.252367]  kthread+0x12c/0x140
>   [  534.252374]  ret_from_fork+0x10/0x3c
>   [  534.252386] ---[ end trace a97341262fc57e44 ]---
>
>   And a similar one from 1008.9 (note that most of the time, the stack
>   trace *doesn't* appear hence I'm not sure if it's related to the
>   display freeze itself, or something auxiliary):
>
>   [  221.914617] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [  221.914617] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  221.914795] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [  232.154711] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  232.154898] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   I can produce this same stack trace, but *without* a corresponding
>   freeze by manually locking the  desktop (Super+L) and waiting for the
>   display fade. However, after the stack trace appears, one can press a
>   key to bring the display back and login again happily. Here are
>   several repeated traces from such activity under the 1008.9 proposed
>   kernel:
>
>   [ 1043.431061] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1043.431136] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1043.431384] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1053.671415] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1053.671705] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1063.911800] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1063.912147] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1181.162739] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1181.418774] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1181.419072] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1191.658996] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1191.659289] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1201.899168] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1201.899438] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1332.461450] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1332.461460] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1332.461717] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1342.701602] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1342.701890] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1352.941798] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1352.942067] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   Note that even when the display is frozen (and cannot be resurrected),
>   only the display driver appears to crash; the system remains
>   operational (at least for some time) happily responding to SSH login
>   requests or, if video is playing, continuing audio output.
>
>   The same occurs with the current linux-firmware-raspi2 release (which
>   the above stack traces were taken from), or with the latest firmware
>   (installed from an experimental package in my
>   https://launchpad.net/~waveform/+archive/ubuntu/firmware PPA).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions
>

Revision history for this message

fprietog (fprietog) wrote on 2021-10-11:

#9

@fossfreedom

Well, in fact the ubuntu-release-upgrader is doing just the the opposite that you want...

In hirsute I was using "vc4-fkms-v3d" so I didn't suffer this problem. But during the upgrade to impish my config.txt file was automatically changed from this:

dtoverlay=vc4-fkms-v3d

To

# changed by do-release-upgrade (LP: #1923673)
dtoverlay=vc4-kms-v3d

This is the related bug:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923673

Revision history for this message

Xinle Yao (sean-was-taken) wrote on 2021-10-11:

#10

Dragging icons around on the dock makes the HDMI outputs freeze reliably on my monitor.

Dave Jones (waveform) on 2021-10-11

Changed in linux-raspi (Ubuntu Impish):
importance:	Undecided → Critical

Revision history for this message

Xinle Yao (sean-was-taken) wrote on 2021-10-12:

#11

After some testing, I found that restarting the monitor unfreezes the HDMI output. The monitor is an LG smart tv.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-13:

#12

Download full text (3.7 KiB)

Not sure if this is yet another different issue. Setting GNOME to 1920x1080@120Hz and rebooting consistently yields the below crash when X starts:

[ 35.852282] Unable to handle kernel paging request at virtual address dead000000000108
[ 35.860416] Mem abort info:
[ 35.863282] ESR = 0x96000044
[ 35.866382] EC = 0x25: DABT (current EL), IL = 32 bits
[ 35.871847] SET = 0, FnV = 0
[ 35.875059] EA = 0, S1PTW = 0
[ 35.878266] Data abort info:
[ 35.881231] ISV = 0, ISS = 0x00000044
[ 35.885156] CM = 0, WnR = 1
[ 35.888185] [dead000000000108] address between user and kernel address ranges
[ 35.895469] Internal error: Oops: 96000044 [#1] PREEMPT SMP
[ 35.901128] Modules linked in: rfcomm cmac algif_hash aes_arm64 algif_skcipher af_alg hci_uart btqca btrtl btbcm btintel bnep snd_soc_hdmi_codec btsdio bluetooth vc4 snd_soc_core ecdh_generic ecc snd_bcm2835(C) snd_pcm_dmaengine snd_pcm_oss bcm2835_codec(C) bcm2835_isp(C) brcmfmac snd_pcm v4l2_mem2mem videobuf2_dma_contig bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) cfg80211 snd_seq videobuf2_vmalloc v3d gpu_sched snd_seq_device crct10dif_ce videobuf2_memops rfkill videobuf2_v4l2 brcmutil raspberrypi_hwmon videobuf2_common snd_timer vc_sm_cma(C) videodev snd drm_kms_helper mc syscopyarea sysfillrect sysimgblt bcm2835_gpiomem fb_sys_fops cec rpivid_mem nvmem_rmem uio_pdrv_genirq uio squashfs sch_fq_codel fuse drm ip_tables x_tables ipv6 autofs4 btrfs blake2b_generic libcrc32c xor xor_neon zstd_compress raid6_pq dm_mod uas usb_storage spidev i2c_brcmstb dwc2 udc_core i2c_bcm2835 xhci_pci roles xhci_pci_renesas spi_bcm2835 phy_generic
[ 35.984579] CPU: 1 PID: 1068 Comm: gnome-shell Tainted: G C 5.13.14-9001-raspi #1+git1294b741
[ 35.994553] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
[ 36.000466] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[ 36.006561] pc : clk_request_done+0x34/0xe0
[ 36.010810] lr : clk_request_done+0x30/0xe0
[ 36.015050] sp : ffff8000122bba10
[ 36.018406] x29: ffff8000122bba10 x28: ffff8000122bbd48 x27: 0000000000000000
[ 36.025655] x26: ffff6b77cae94000 x25: 0000000000000038 x24: ffff6b77d4f82c00
[ 36.032902] x23: ffff6b77d08afc80 x22: 000000001dcd6500 x21: ffff6b77e0eb8200
[ 36.040148] x20: ffff6b77c3575200 x19: ffff6b77d0a8a780 x18: 0000000000000000
[ 36.047393] x17: 0000000000000000 x16: ffffaaafc2cfcdc0 x15: 0000ffffc55ddcb0
[ 36.054638] x14: 0000000000000000 x13: 0000000000000000 x12: 00000000ffffffff
[ 36.061882] x11: ffffaaafc352e4d0 x10: 0000000000000b20 x9 : ffffaaafc2cf409c
[ 36.069127] x8 : ffff6b77e6ce4980 x7 : 0000000000000000 x6 : dead000000000100
[ 36.076372] x5 : 0000000000000000 x4 : ffff6b77e6ce3e00 x3 : ffffaaafc3c49238
[ 36.083617] x2 : dead000000000100 x1 : dead000000000122 x0 : 0000000000000001
[ 36.090862] Call trace:
[ 36.093338] clk_request_done+0x34/0xe0
[ 36.097227] vc4_atomic_commit_tail+0x550/0x6b4 [vc4]
[ 36.102403] commit_tail+0xac/0x190 [drm_kms_helper]
[ 36.107524] drm_atomic_helper_commit+0x16c/0x380 [drm_kms_helper]
[ 36.113867] drm_atomic_commit+0x58/0x70 [drm]
[ 36.118529] drm_atomic_helper_set_config+0xe0/0x120 [drm_kms_helper]
[ 36.1251...

Not sure if this is yet another different issue. Setting GNOME to 1920x1080@120Hz and rebooting consistently yields the below crash when X starts:

[   35.852282] Unable to handle kernel paging request at virtual address dead000000000108
[   35.860416] Mem abort info:
[   35.863282]   ESR = 0x96000044
[   35.866382]   EC = 0x25: DABT (current EL), IL = 32 bits
[   35.871847]   SET = 0, FnV = 0
[   35.875059]   EA = 0, S1PTW = 0
[   35.878266] Data abort info:
[   35.881231]   ISV = 0, ISS = 0x00000044
[   35.885156]   CM = 0, WnR = 1
[   35.888185] [dead000000000108] address between user and kernel address ranges
[   35.895469] Internal error: Oops: 96000044 [#1] PREEMPT SMP
[   35.901128] Modules linked in: rfcomm cmac algif_hash aes_arm64 algif_skcipher af_alg hci_uart btqca btrtl btbcm btintel bnep snd_soc_hdmi_codec btsdio bluetooth vc4 snd_soc_core ecdh_generic ecc snd_bcm2835(C) snd_pcm_dmaengine snd_pcm_oss bcm2835_codec(C) bcm2835_isp(C) brcmfmac snd_pcm v4l2_mem2mem videobuf2_dma_contig bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) cfg80211 snd_seq videobuf2_vmalloc v3d gpu_sched snd_seq_device crct10dif_ce videobuf2_memops rfkill videobuf2_v4l2 brcmutil raspberrypi_hwmon videobuf2_common snd_timer vc_sm_cma(C) videodev snd drm_kms_helper mc syscopyarea sysfillrect sysimgblt bcm2835_gpiomem fb_sys_fops cec rpivid_mem nvmem_rmem uio_pdrv_genirq uio squashfs sch_fq_codel fuse drm ip_tables x_tables ipv6 autofs4 btrfs blake2b_generic libcrc32c xor xor_neon zstd_compress raid6_pq dm_mod uas usb_storage spidev i2c_brcmstb dwc2 udc_core i2c_bcm2835 xhci_pci roles xhci_pci_renesas spi_bcm2835 phy_generic
[   35.984579] CPU: 1 PID: 1068 Comm: gnome-shell Tainted: G         C        5.13.14-9001-raspi #1+git1294b741
[   35.994553] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
[   36.000466] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[   36.006561] pc : clk_request_done+0x34/0xe0
[   36.010810] lr : clk_request_done+0x30/0xe0
[   36.015050] sp : ffff8000122bba10
[   36.018406] x29: ffff8000122bba10 x28: ffff8000122bbd48 x27: 0000000000000000
[   36.025655] x26: ffff6b77cae94000 x25: 0000000000000038 x24: ffff6b77d4f82c00
[   36.032902] x23: ffff6b77d08afc80 x22: 000000001dcd6500 x21: ffff6b77e0eb8200
[   36.040148] x20: ffff6b77c3575200 x19: ffff6b77d0a8a780 x18: 0000000000000000
[   36.047393] x17: 0000000000000000 x16: ffffaaafc2cfcdc0 x15: 0000ffffc55ddcb0
[   36.054638] x14: 0000000000000000 x13: 0000000000000000 x12: 00000000ffffffff
[   36.061882] x11: ffffaaafc352e4d0 x10: 0000000000000b20 x9 : ffffaaafc2cf409c
[   36.069127] x8 : ffff6b77e6ce4980 x7 : 0000000000000000 x6 : dead000000000100
[   36.076372] x5 : 0000000000000000 x4 : ffff6b77e6ce3e00 x3 : ffffaaafc3c49238
[   36.083617] x2 : dead000000000100 x1 : dead000000000122 x0 : 0000000000000001
[   36.090862] Call trace:
[   36.093338]  clk_request_done+0x34/0xe0
[   36.097227]  vc4_atomic_commit_tail+0x550/0x6b4 [vc4]
[   36.102403]  commit_tail+0xac/0x190 [drm_kms_helper]
[   36.107524]  drm_atomic_helper_commit+0x16c/0x380 [drm_kms_helper]
[   36.113867]  drm_atomic_commit+0x58/0x70 [drm]
[   36.118529]  drm_atomic_helper_set_config+0xe0/0x120 [drm_kms_helper]
[   36.125136]  drm_mode_setcrtc+0x1b4/0x7f0 [drm]
[   36.129870]  drm_ioctl_kernel+0xd0/0x120 [drm]
[   36.134514]  drm_ioctl+0x2a4/0x560 [drm]
[   36.138630]  __arm64_sys_ioctl+0xb4/0x100
[   36.142700]  invoke_syscall+0x50/0x120
[   36.146505]  el0_svc_common.constprop.0+0x6c/0x1a0
[   36.151367]  do_el0_svc+0x30/0x94
[   36.154729]  el0_svc+0x2c/0x54
[   36.157828]  el0_sync_handler+0x1a4/0x1b0
[   36.161893]  el0_sync+0x19c/0x1c0
[   36.165259] Code: f9400800 f9400014 97ffdca1 a9400662 (f9000441) 
[   36.171440] ---[ end trace e46e53e469b2ff21 ]---

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-14:

#13

A test kernel is available here: https://kernel.ubuntu.com/~juergh/lp1946368/

I'd appreciate it if people who suffer from this problem could take it for a spin and report back.

Make sure to use full kms, i.e., dtoverlay=vc4-kms-v3d and also verify that you're actually running the test kernel:

$ uname -a
Linux rpi-4b-rev1d4-d9f5 5.13.0-1008-raspi #9+20211014.git9545d93d SMP PREEMPT Thu Oct 14 09:46:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Revision history for this message

fprietog (fprietog) wrote on 2021-10-14:

#14

Quick test done:

root@fpgrpi:~# uname -a
Linux fpgrpi 5.13.0-1008-raspi #9+20211014.git9545d93d SMP PREEMPT Thu Oct 14 09:46:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Tested dtoverlay=vc4-kms-v3d on both wayland and X11 with no HDMI freezes at all. I'll have it keep running (on wayland) to make sure, but this fix seems to be really promising. Thanks.

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-14:

#15

Download full text (9.9 KiB)

'fraid its not working here.

Confirmed uname -a - rebooted, ok. Switched to kms and on reboot it hangs.

Here using budgie-desktop installed on the current 21.10 release image
with gnome-shell removed. Thus using X11.

On Thu, 14 Oct 2021 at 13:01, fprietog <email address hidden> wrote:
>
> Quick test done:
>
> root@fpgrpi:~# uname -a
> Linux fpgrpi 5.13.0-1008-raspi #9+20211014.git9545d93d SMP PREEMPT Thu Oct 14 09:46:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
>
> Tested dtoverlay=vc4-kms-v3d on both wayland and X11 with no HDMI
> freezes at all. I'll have it keep running (on wayland) to make sure, but
> this fix seems to be really promising. Thanks.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
> HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
> Confirmed
> Status in linux-raspi source package in Impish:
> Confirmed
>
> Bug description:
> Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
> for the Ubuntu Pi pre-installed desktop impish release, the HDMI
> output occasionally freezes. A known workaround at this time is to
> change the following line in /boot/firmware/config.txt:
>
> dtoverlay=vc4-kms-v3d
>
> To the following:
>
> dtoverlay=vc4-fkms-v3d
>
> In other words, to use the "fake" KMS overlay (fkms) instead of the
> "full" KMS overlay (kms).
>
> I've been unable to determine a reliable method of guaranteeing a
> freeze, but it appears to occur much more readily when video playback
> is occurring, and when other interactions (especially moving windows
> around, minimizing, restoring) occurs simultaneously. Display suspend
> also periodically causes the same hang, which made me suspect this
> might be related to #1944397 but it appears that had a separate cause
> (now resolved).
>
> The following dmesg outputs have been observed immediately after the
> display hang; this one from 1007.8:
>
> [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
> mmit wait timed out
> [ 513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
> done timed out
> [ 524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
> ] commit wait timed out
> [ 534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
> [ 534.250685] ------------[ cut here ]------------
> [ 534.250701] refcount_t: underflow; use-after-free.
> [ 534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
> [ 534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm
> btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm283...

'fraid its not working here.

Confirmed uname -a - rebooted, ok.  Switched to kms and on reboot it hangs.

Here using budgie-desktop installed on the current 21.10 release image
with gnome-shell removed.  Thus using X11.

On Thu, 14 Oct 2021 at 13:01, fprietog <1946368@bugs.launchpad.net> wrote:
>
> Quick test done:
>
> root@fpgrpi:~# uname -a
> Linux fpgrpi 5.13.0-1008-raspi #9+20211014.git9545d93d SMP PREEMPT Thu Oct 14 09:46:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
>
> Tested dtoverlay=vc4-kms-v3d on both wayland and X11 with no HDMI
> freezes at all. I'll have it keep running (on wayland) to make sure, but
> this fix seems to be really promising. Thanks.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
>   HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
>   Confirmed
> Status in linux-raspi source package in Impish:
>   Confirmed
>
> Bug description:
>   Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
>   for the Ubuntu Pi pre-installed desktop impish release, the HDMI
>   output occasionally freezes. A known workaround at this time is to
>   change the following line in /boot/firmware/config.txt:
>
>   dtoverlay=vc4-kms-v3d
>
>   To the following:
>
>   dtoverlay=vc4-fkms-v3d
>
>   In other words, to use the "fake" KMS overlay (fkms) instead of the
>   "full" KMS overlay (kms).
>
>   I've been unable to determine a reliable method of guaranteeing a
>   freeze, but it appears to occur much more readily when video playback
>   is occurring, and when other interactions (especially moving windows
>   around, minimizing, restoring) occurs simultaneously.  Display suspend
>   also periodically causes the same hang, which made me suspect this
>   might be related to #1944397 but it appears that had a separate cause
>   (now resolved).
>
>   The following dmesg outputs have been observed immediately after the
>   display hang; this one from 1007.8:
>
>   [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
>   mmit wait timed out
>   [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
>   done timed out
>   [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
>   ] commit wait timed out
>   [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [  534.250685] ------------[ cut here ]------------
>   [  534.250701] refcount_t: underflow; use-after-free.
>   [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
>   [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm
>    btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C)
>    snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi snd_seq_midi_event bcm2835_codec(C) bcm
>   2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig
>   videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_common videodev snd_seq_devi
>   ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem uio_pdrv_genirq uio sch_fq_
>   codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress hid_generic usbhid raid
>   6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core gpu_sched crct10dif_ce i2c_
>   brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci xhci_pci_renesas sysfillrect sysimgbl
>   t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
>   [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: G        WC        5.13.0-1007-raspi #8-Ubuntu
>   [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
>   [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
>   [  534.251239] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
>   [  534.251248] pc : refcount_dec_not_one+0xa0/0xbc
>   [  534.251257] lr : refcount_dec_not_one+0xa0/0xbc
>   [  534.251265] sp : ffff8000118cbb50
>   [  534.251269] x29: ffff8000118cbb50 x28: ffff6cf7ee894400 x27: ffff6cf80502e000
>   [  534.251285] x26: ffff6cf80502e000 x25: 0000000000000006 x24: ffff6cf7ee94c500
>   [  534.251300] x23: ffffa94dff246018 x22: ffff6cf833068880 x21: ffff6cf805027c80
>   [  534.251314] x20: ffff6cf88ead75ac x19: ffff6cf88ead7400 x18: 0000000000000000
>   [  534.251328] x17: 0000000000000000 x16: ffffa94e0a243314 x15: 0000000000000000
>   [  534.251342] x14: 0000000000000000 x13: 0000000000000030 x12: ffff800010035000
>   [  534.251356] x11: ffffa94e0b30dfd0 x10: 00000000fffff000 x9 : ffffa94e09d09f54
>   [  534.251370] x8 : 00000000ffffefff x7 : ffffa94e0b30dfd0 x6 : 0000000000000000
>   [  534.251384] x5 : ffff6cf8b799f948 x4 : 0000000000000000 x3 : 0000000000000027
>   [  534.251397] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff6cf800abec80
>   [  534.251411] Call trace:
>   [  534.251416]  refcount_dec_not_one+0xa0/0xbc
>   [  534.251424]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
>   [  534.251473]  vc4_cleanup_fb+0x3c/0x4c [vc4]
>   [  534.251518]  drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper]
>   [  534.251604]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
>   [  534.251648]  commit_tail+0xac/0x190 [drm_kms_helper]
>   [  534.251723]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
>   [  534.251796]  drm_atomic_commit+0x58/0x70 [drm]
>   [  534.251936]  atomic_remove_fb+0x2a8/0x2f4 [drm]
>   [  534.252073]  drm_framebuffer_remove+0x164/0x18c [drm]
>   [  534.252209]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
>   [  534.252346]  process_one_work+0x200/0x4d0
>   [  534.252359]  worker_thread+0x2c8/0x470
>   [  534.252367]  kthread+0x12c/0x140
>   [  534.252374]  ret_from_fork+0x10/0x3c
>   [  534.252386] ---[ end trace a97341262fc57e44 ]---
>
>   And a similar one from 1008.9 (note that most of the time, the stack
>   trace *doesn't* appear hence I'm not sure if it's related to the
>   display freeze itself, or something auxiliary):
>
>   [  221.914617] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [  221.914617] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  221.914795] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [  232.154711] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  232.154898] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   I can produce this same stack trace, but *without* a corresponding
>   freeze by manually locking the  desktop (Super+L) and waiting for the
>   display fade. However, after the stack trace appears, one can press a
>   key to bring the display back and login again happily. Here are
>   several repeated traces from such activity under the 1008.9 proposed
>   kernel:
>
>   [ 1043.431061] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1043.431136] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1043.431384] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1053.671415] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1053.671705] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1063.911800] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1063.912147] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1181.162739] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1181.418774] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1181.419072] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1191.658996] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1191.659289] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1201.899168] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1201.899438] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1332.461450] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1332.461460] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1332.461717] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1342.701602] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1342.701890] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1352.941798] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1352.942067] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   Note that even when the display is frozen (and cannot be resurrected),
>   only the display driver appears to crash; the system remains
>   operational (at least for some time) happily responding to SSH login
>   requests or, if video is playing, continuing audio output.
>
>   The same occurs with the current linux-firmware-raspi2 release (which
>   the above stack traces were taken from), or with the latest firmware
>   (installed from an experimental package in my
>   https://launchpad.net/~waveform/+archive/ubuntu/firmware PPA).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions
>

Revision history for this message

fprietog (fprietog) wrote on 2021-10-14:

#16

@fossfreedom sorry to read this. It's still working for me even triyng to force it dragging icons, playing video and doing gpu benchmarks...

Please, publish here the result of inxi -Faz command in order to see if there is a difference between your and my graphics system:

Wayland, inxi graphics section:
-------------------------------
Graphics: Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef00700 class-ID: hdmi
           Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef05700 class-ID: hdmi
           Device-3: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu class-ID: gpu
           Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev
           display-ID: :0 screens: 1
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
           Monitor-1: XWAYLAND0 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") diag: 551mm (21.7")
           OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.2.2 direct render: Yes

X11, inxi graphics section:
---------------------------
Graphics: Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef00700 class-ID: hdmi
           Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A chip-ID: brcm:fef05700 class-ID: hdmi
           Device-3: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu class-ID: gpu
           Display: x11 server: X.Org 1.20.13 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev
           display-ID: :0 screens: 1
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
           Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 102 size: 476x268mm (18.7x10.6") diag: 546mm (21.5")
           OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.2.2 direct render: Yes

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2021-10-14:

#17

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1946368

tags:

added: iso-testing

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-14 (last edit on 2021-10-14):

#18

I have installed this 2 *.deb from here:
https://kernel.ubuntu.com/~juergh/impish-raspi/

Setting is now kms instead fkms

uname -a
Linux RW-RPI2 5.13.14-9004-raspi #1+git9545d93d SMP PREEMPT Thu Oct 14 11:12:19 CEST 2021 aarch64 aarch64 aarch64 GNU/Linux

config.txt:

# Config settings specific to arm64
arm_64bit=1
dtoverlay=dwc2
gpu_mem=512
dtoverlay=vc4-kms-v3d

Ubuntu Budgie 21.10

Starting Video with "Kylin" (setting is Mplayer) and it works fine without freeze.
Testing with DELL 19" 1600x900. Video playing in Fullscreen or Windows without issue.
Video playing in Firefox-Browser without issue.
Video and audio are beautifully synchronous.

I had installed all 6 *.deb from https://kernel.ubuntu.com/~juergh/lp1946368/
but that don´t helps out. So, i remove all of them again.
The strange thing was that with uname -a only one kernel with status September had reported.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-14:

#19

@knoedelfan, what doesn't help? `uname -a` will just show you the version of the running kernel.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-14:

#20

@fossfredom can you ssh to the system and pull the kernel log?

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-14:

#21

@knoedelfan, Oh, you might need to force flash-kernel if you have test kernels installed because their versions might be higher.

Install linux-image and linux-modules from https://kernel.ubuntu.com/~juergh/lp1946368/ and then 'flash-kernel --force 5.13.0-1008-raspi'.

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-14:

#22

Download full text (11.1 KiB)

Graphics:
  Device-1: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu
  class-ID: gpu
  Device-2: bcm2711-hdmi0 driver: N/A bus-ID: N/A chip-ID: brcm:soc
  class-ID: hdmi
  Device-3: bcm2711-hdmi1 driver: N/A bus-ID: N/A chip-ID: brcm:soc
  class-ID: hdmi
  Display: x11 server: X.Org 1.20.13 compositor: budgie-wm driver:
  loaded: modesetting unloaded: fbdev display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.0x9.4")
  s-diag: 449mm (17.7")
  Monitor-1: HDMI-1 res: 1440x900 hz: 60 dpi: 90
  size: 408x255mm (16.1x10.0") diag: 481mm (18.9")
  OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.2.2 direct render: Yes

The hang is at boot stage - so it hasnt got to lightDM/desktop - so
its not possible to SSH - I scanned via nmap and it isnt seen on the
network. I just see the initial date text after the splash screen,
followed by writable blocks and seeing briefly the load of the
broadcom driver - at that stage the monitor turns off. Switching back
to fkms via a separate computer, reinserting into the pi allows the
boot to be ok to the lightdm & desktop.

If my issues are different from others then maybe I should raise a
separate bug report.
On Thu, 14 Oct 2021 at 14:35, knoedel fan <email address hidden> wrote:
>
> I have installed this 2 *.deb from here:
> https://kernel.ubuntu.com/~juergh/impish-raspi/
>
> Setting is now kms instead fkms
>
> uname -a
> Linux RW-RPI2 5.13.14-9004-raspi #1+git9545d93d SMP PREEMPT Thu Oct 14 11:12:19 CEST 2021 aarch64 aarch64 aarch64 GNU/Linux
>
> Ubuntu Budgie 21.10
>
> Starting Video with "Kylin" (setting is Mplayer) and it works fine without freeze.
> Testing with DELL 19" 1600x900. Video playing in Fullscreen or Windows without issue.
> Video playing in Firefox-Browser without issue.
>
> I had installed all 6 *.deb from https://kernel.ubuntu.com/~juergh/lp1946368/
> but that don´t helps out. So, i remove all of them again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
> HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
> Confirmed
> Status in linux-raspi source package in Impish:
> Confirmed
>
> Bug description:
> Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
> for the Ubuntu Pi pre-installed desktop impish release, the HDMI
> output occasionally freezes. A known workaround at this time is to
> change the following line in /boot/firmware/config.txt:
>
> dtoverlay=vc4-kms-v3d
>
> To the following:
>
> dtoverlay=vc4-fkms-v3d
>
> In other words, to use the "fake" KMS overlay (fkms) instead of the
> "full" KMS overlay (kms).
>
> I've been unable to determine a reliable method of guaranteeing a
> freeze, but it appears to occur much more readily when video playback
> is occurring, and when other interactions (especially moving windows
> around, minimizing, restoring) occurs simultaneously. Display suspend
> also periodically causes the same hang, which made me suspect this
> might be related to #1944397 but it appears that had a separate cause
> (now ...

Graphics:
  Device-1: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:gpu
  class-ID: gpu
  Device-2: bcm2711-hdmi0 driver: N/A bus-ID: N/A chip-ID: brcm:soc
  class-ID: hdmi
  Device-3: bcm2711-hdmi1 driver: N/A bus-ID: N/A chip-ID: brcm:soc
  class-ID: hdmi
  Display: x11 server: X.Org 1.20.13 compositor: budgie-wm driver:
  loaded: modesetting unloaded: fbdev display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.0x9.4")
  s-diag: 449mm (17.7")
  Monitor-1: HDMI-1 res: 1440x900 hz: 60 dpi: 90
  size: 408x255mm (16.1x10.0") diag: 481mm (18.9")
  OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.2.2 direct render: Yes

The hang is at boot stage - so it hasnt got to lightDM/desktop - so
its not possible to SSH - I scanned via nmap and it isnt seen on the
network.  I just see the initial date text after the splash screen,
followed by writable blocks and seeing briefly the load of the
broadcom driver - at that stage the monitor turns off.  Switching back
to fkms via a separate computer, reinserting into the pi allows the
boot to be ok to the lightdm & desktop.

If my issues are different from others then maybe I should raise a
separate bug report.
On Thu, 14 Oct 2021 at 14:35, knoedel fan <1946368@bugs.launchpad.net> wrote:
>
> I have installed this 2 *.deb from here:
> https://kernel.ubuntu.com/~juergh/impish-raspi/
>
> Setting is now kms instead fkms
>
> uname -a
> Linux RW-RPI2 5.13.14-9004-raspi #1+git9545d93d SMP PREEMPT Thu Oct 14 11:12:19 CEST 2021 aarch64 aarch64 aarch64 GNU/Linux
>
> Ubuntu Budgie 21.10
>
> Starting Video with "Kylin" (setting is Mplayer) and it works fine without freeze.
> Testing with DELL 19" 1600x900. Video playing in Fullscreen or Windows without issue.
> Video playing in Firefox-Browser without issue.
>
> I had installed all 6 *.deb from  https://kernel.ubuntu.com/~juergh/lp1946368/
> but that don´t helps out. So, i remove all of them again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
>   HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
>   Confirmed
> Status in linux-raspi source package in Impish:
>   Confirmed
>
> Bug description:
>   Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
>   for the Ubuntu Pi pre-installed desktop impish release, the HDMI
>   output occasionally freezes. A known workaround at this time is to
>   change the following line in /boot/firmware/config.txt:
>
>   dtoverlay=vc4-kms-v3d
>
>   To the following:
>
>   dtoverlay=vc4-fkms-v3d
>
>   In other words, to use the "fake" KMS overlay (fkms) instead of the
>   "full" KMS overlay (kms).
>
>   I've been unable to determine a reliable method of guaranteeing a
>   freeze, but it appears to occur much more readily when video playback
>   is occurring, and when other interactions (especially moving windows
>   around, minimizing, restoring) occurs simultaneously.  Display suspend
>   also periodically causes the same hang, which made me suspect this
>   might be related to #1944397 but it appears that had a separate cause
>   (now resolved).
>
>   The following dmesg outputs have been observed immediately after the
>   display hang; this one from 1007.8:
>
>   [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
>   mmit wait timed out
>   [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
>   done timed out
>   [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
>   ] commit wait timed out
>   [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [  534.250685] ------------[ cut here ]------------
>   [  534.250701] refcount_t: underflow; use-after-free.
>   [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
>   [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm
>    btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C)
>    snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi snd_seq_midi_event bcm2835_codec(C) bcm
>   2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig
>   videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_common videodev snd_seq_devi
>   ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem uio_pdrv_genirq uio sch_fq_
>   codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress hid_generic usbhid raid
>   6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core gpu_sched crct10dif_ce i2c_
>   brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci xhci_pci_renesas sysfillrect sysimgbl
>   t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
>   [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: G        WC        5.13.0-1007-raspi #8-Ubuntu
>   [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
>   [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
>   [  534.251239] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
>   [  534.251248] pc : refcount_dec_not_one+0xa0/0xbc
>   [  534.251257] lr : refcount_dec_not_one+0xa0/0xbc
>   [  534.251265] sp : ffff8000118cbb50
>   [  534.251269] x29: ffff8000118cbb50 x28: ffff6cf7ee894400 x27: ffff6cf80502e000
>   [  534.251285] x26: ffff6cf80502e000 x25: 0000000000000006 x24: ffff6cf7ee94c500
>   [  534.251300] x23: ffffa94dff246018 x22: ffff6cf833068880 x21: ffff6cf805027c80
>   [  534.251314] x20: ffff6cf88ead75ac x19: ffff6cf88ead7400 x18: 0000000000000000
>   [  534.251328] x17: 0000000000000000 x16: ffffa94e0a243314 x15: 0000000000000000
>   [  534.251342] x14: 0000000000000000 x13: 0000000000000030 x12: ffff800010035000
>   [  534.251356] x11: ffffa94e0b30dfd0 x10: 00000000fffff000 x9 : ffffa94e09d09f54
>   [  534.251370] x8 : 00000000ffffefff x7 : ffffa94e0b30dfd0 x6 : 0000000000000000
>   [  534.251384] x5 : ffff6cf8b799f948 x4 : 0000000000000000 x3 : 0000000000000027
>   [  534.251397] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff6cf800abec80
>   [  534.251411] Call trace:
>   [  534.251416]  refcount_dec_not_one+0xa0/0xbc
>   [  534.251424]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
>   [  534.251473]  vc4_cleanup_fb+0x3c/0x4c [vc4]
>   [  534.251518]  drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper]
>   [  534.251604]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
>   [  534.251648]  commit_tail+0xac/0x190 [drm_kms_helper]
>   [  534.251723]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
>   [  534.251796]  drm_atomic_commit+0x58/0x70 [drm]
>   [  534.251936]  atomic_remove_fb+0x2a8/0x2f4 [drm]
>   [  534.252073]  drm_framebuffer_remove+0x164/0x18c [drm]
>   [  534.252209]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
>   [  534.252346]  process_one_work+0x200/0x4d0
>   [  534.252359]  worker_thread+0x2c8/0x470
>   [  534.252367]  kthread+0x12c/0x140
>   [  534.252374]  ret_from_fork+0x10/0x3c
>   [  534.252386] ---[ end trace a97341262fc57e44 ]---
>
>   And a similar one from 1008.9 (note that most of the time, the stack
>   trace *doesn't* appear hence I'm not sure if it's related to the
>   display freeze itself, or something auxiliary):
>
>   [  221.914617] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [  221.914617] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  221.914795] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [  232.154711] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  232.154898] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   I can produce this same stack trace, but *without* a corresponding
>   freeze by manually locking the  desktop (Super+L) and waiting for the
>   display fade. However, after the stack trace appears, one can press a
>   key to bring the display back and login again happily. Here are
>   several repeated traces from such activity under the 1008.9 proposed
>   kernel:
>
>   [ 1043.431061] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1043.431136] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1043.431384] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1053.671415] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1053.671705] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1063.911800] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1063.912147] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1181.162739] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1181.418774] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1181.419072] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1191.658996] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1191.659289] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1201.899168] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1201.899438] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1332.461450] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1332.461460] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1332.461717] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1342.701602] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1342.701890] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1352.941798] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1352.942067] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   Note that even when the display is frozen (and cannot be resurrected),
>   only the display driver appears to crash; the system remains
>   operational (at least for some time) happily responding to SSH login
>   requests or, if video is playing, continuing audio output.
>
>   The same occurs with the current linux-firmware-raspi2 release (which
>   the above stack traces were taken from), or with the latest firmware
>   (installed from an experimental package in my
>   https://launchpad.net/~waveform/+archive/ubuntu/firmware PPA).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions
>

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-14:

#23

#21

Because the two *. deb from https://kernel. ubuntu. com/~juergh/impish-raspi/ work, I don’t see any reason to make any further changes at the moment.

Had installed both with "Software" Application installation.

Revision history for this message

fprietog (fprietog) wrote on 2021-10-14 (last edit on 2021-10-14):

#24

@fossfreedom, apart from the wm used (you budgie-wm and me gnome-shell) I see that your HDMI devices are identified as brcm:soc while mines are identified as fef00700 and fef05700.

Maybe we are using different eeprom version. I'm using latest stable from here:
https://github.com/raspberrypi/rpi-eeprom

root@fpgrpi:~# rpi-eeprom-update

BOOTLOADER: up to date
   CURRENT: mar 06 jul 2021 10:44:53 UTC (1625568293)
    LATEST: jue 29 abr 2021 16:11:25 UTC (1619712685)
   RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
            Use raspi-config to change the release.

  VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 000138a1
    LATEST: 000138a1

Which one are you using? Maybe you can update it to the newest version just to try.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-14:

#25

@knoedelfan, then you'll never get kernel updates again since the test kernel's version will always be higher. Your call.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-14:

#26

@fossfreedom, can you SSH to the system if you boot without a monitor attached? Then you could (untested):
- systemctl set-default multi-user
- reattach monitor
- reboot
- SSH to system
- systemctl isolate graphical (to fire up X)
- pull logs (assuming the system stays up)

Revision history for this message

William Wilson (jawn-smith) wrote on 2021-10-14:

#27

@juergh with this new kernel I no longer see the flip_done timed out message, but HDMI still dies and the boot process hangs right after plymouth starts up.

```
ext4
Thu Jan 1 00:00:09 UTC 1970
writable: recovering journal
writable: clean, 159978/929200 files, 1595477/3751163 blocks
-.mount
blk-availability.service
dev-hugepages.mount
dev-mqueue.mount
sys-kernel-debug.mount
sys-kernel-tracing.mount
kmod-static-nodes.service
systemd-modules-load.service
systemd-remount-fs.service
ufw.service
swapfile.swap
systemd-journald.service
sys-fs-fuse-connections.mount
sys-kernel-config.mount
systemd-growfs@-.service
systemd-random-seed.service
systemd-sysusers.service
systemd-sysctl.service
systemd-tmpfiles-setup-dev.service
keyboard-setup.service
systemd-journal-flush.service
lvm2-monitor.service
snap-bare-5.mount
snap-core-11803.mount
snap-core20-1171.mount
snap-firefox-633.mount
snap-gnome\x2d3\x2d38\x2d2004-78.mount
snap-gtk\x2dcommon\x2dthemes-1519.mount
snap-snap\x2dstore-555.mount
systemd-udevd.service
systemd-udev-trigger.service
plymouth-start.service
[ 15.442712] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 15.725950] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 15.738824] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 15.760840] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: May 14 2020 17:26:08 version 7.84.17.1 (r871554) FWID 01-3d9e1d87
```

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-14 (last edit on 2021-10-14):

#28

#25
No problem for me.
Ubuntu Budgie 21.10 is only release candidate. So, if there is the final out coming, I install this fresh.
It's only my Test-System, and normally I use Ubuntu budgie 21.04.

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-14:

#29

Download full text (9.8 KiB)

Similar here to William Wilson's observation - I've now done a clean
install - installed openssh-server - autologin. With KMS and no
monitor attached the raspi hangs before any network is established -
confirmed via nmap scan. With fkms & no monitor attached, boot occurs
ok and I can find the raspi IP via nmap and connect via ssh.

On Thu, 14 Oct 2021 at 17:10, knoedel fan <email address hidden> wrote:
>
> #25
> No problem for me.
> Ubuntu Budgie 21.10 is only release candidate. So, if there is the final out coming, I install this fresh.
> It's only my Test-System, and normally I use Ubuntu budgie 21.04.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
> HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
> Confirmed
> Status in linux-raspi source package in Impish:
> Confirmed
>
> Bug description:
> Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
> for the Ubuntu Pi pre-installed desktop impish release, the HDMI
> output occasionally freezes. A known workaround at this time is to
> change the following line in /boot/firmware/config.txt:
>
> dtoverlay=vc4-kms-v3d
>
> To the following:
>
> dtoverlay=vc4-fkms-v3d
>
> In other words, to use the "fake" KMS overlay (fkms) instead of the
> "full" KMS overlay (kms).
>
> I've been unable to determine a reliable method of guaranteeing a
> freeze, but it appears to occur much more readily when video playback
> is occurring, and when other interactions (especially moving windows
> around, minimizing, restoring) occurs simultaneously. Display suspend
> also periodically causes the same hang, which made me suspect this
> might be related to #1944397 but it appears that had a separate cause
> (now resolved).
>
> The following dmesg outputs have been observed immediately after the
> display hang; this one from 1007.8:
>
> [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
> mmit wait timed out
> [ 513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
> done timed out
> [ 524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
> ] commit wait timed out
> [ 534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
> [ 534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
> [ 534.250685] ------------[ cut here ]------------
> [ 534.250701] refcount_t: underflow; use-after-free.
> [ 534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
> [ 534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm
> btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C)
> snd_pcm_dmaengine ecdh_generic ecc snd_pcm ...

Similar here to William Wilson's observation - I've now done a clean
install - installed openssh-server - autologin.  With KMS and no
monitor attached the raspi hangs before any network is established -
confirmed via nmap scan.  With fkms & no monitor attached, boot occurs
ok and I can find the raspi IP via nmap and connect via ssh.

On Thu, 14 Oct 2021 at 17:10, knoedel fan <1946368@bugs.launchpad.net> wrote:
>
> #25
> No problem for me.
> Ubuntu Budgie 21.10 is only release candidate. So, if there is the final out coming, I install this fresh.
> It's only my Test-System, and normally I use Ubuntu budgie 21.04.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
>   HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
>   Confirmed
> Status in linux-raspi source package in Impish:
>   Confirmed
>
> Bug description:
>   Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
>   for the Ubuntu Pi pre-installed desktop impish release, the HDMI
>   output occasionally freezes. A known workaround at this time is to
>   change the following line in /boot/firmware/config.txt:
>
>   dtoverlay=vc4-kms-v3d
>
>   To the following:
>
>   dtoverlay=vc4-fkms-v3d
>
>   In other words, to use the "fake" KMS overlay (fkms) instead of the
>   "full" KMS overlay (kms).
>
>   I've been unable to determine a reliable method of guaranteeing a
>   freeze, but it appears to occur much more readily when video playback
>   is occurring, and when other interactions (especially moving windows
>   around, minimizing, restoring) occurs simultaneously.  Display suspend
>   also periodically causes the same hang, which made me suspect this
>   might be related to #1944397 but it appears that had a separate cause
>   (now resolved).
>
>   The following dmesg outputs have been observed immediately after the
>   display hang; this one from 1007.8:
>
>   [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
>   mmit wait timed out
>   [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
>   done timed out
>   [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
>   ] commit wait timed out
>   [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [  534.250685] ------------[ cut here ]------------
>   [  534.250701] refcount_t: underflow; use-after-free.
>   [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
>   [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm
>    btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C)
>    snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi snd_seq_midi_event bcm2835_codec(C) bcm
>   2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig
>   videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_common videodev snd_seq_devi
>   ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem uio_pdrv_genirq uio sch_fq_
>   codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress hid_generic usbhid raid
>   6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core gpu_sched crct10dif_ce i2c_
>   brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci xhci_pci_renesas sysfillrect sysimgbl
>   t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
>   [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: G        WC        5.13.0-1007-raspi #8-Ubuntu
>   [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
>   [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
>   [  534.251239] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
>   [  534.251248] pc : refcount_dec_not_one+0xa0/0xbc
>   [  534.251257] lr : refcount_dec_not_one+0xa0/0xbc
>   [  534.251265] sp : ffff8000118cbb50
>   [  534.251269] x29: ffff8000118cbb50 x28: ffff6cf7ee894400 x27: ffff6cf80502e000
>   [  534.251285] x26: ffff6cf80502e000 x25: 0000000000000006 x24: ffff6cf7ee94c500
>   [  534.251300] x23: ffffa94dff246018 x22: ffff6cf833068880 x21: ffff6cf805027c80
>   [  534.251314] x20: ffff6cf88ead75ac x19: ffff6cf88ead7400 x18: 0000000000000000
>   [  534.251328] x17: 0000000000000000 x16: ffffa94e0a243314 x15: 0000000000000000
>   [  534.251342] x14: 0000000000000000 x13: 0000000000000030 x12: ffff800010035000
>   [  534.251356] x11: ffffa94e0b30dfd0 x10: 00000000fffff000 x9 : ffffa94e09d09f54
>   [  534.251370] x8 : 00000000ffffefff x7 : ffffa94e0b30dfd0 x6 : 0000000000000000
>   [  534.251384] x5 : ffff6cf8b799f948 x4 : 0000000000000000 x3 : 0000000000000027
>   [  534.251397] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff6cf800abec80
>   [  534.251411] Call trace:
>   [  534.251416]  refcount_dec_not_one+0xa0/0xbc
>   [  534.251424]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
>   [  534.251473]  vc4_cleanup_fb+0x3c/0x4c [vc4]
>   [  534.251518]  drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper]
>   [  534.251604]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
>   [  534.251648]  commit_tail+0xac/0x190 [drm_kms_helper]
>   [  534.251723]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
>   [  534.251796]  drm_atomic_commit+0x58/0x70 [drm]
>   [  534.251936]  atomic_remove_fb+0x2a8/0x2f4 [drm]
>   [  534.252073]  drm_framebuffer_remove+0x164/0x18c [drm]
>   [  534.252209]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
>   [  534.252346]  process_one_work+0x200/0x4d0
>   [  534.252359]  worker_thread+0x2c8/0x470
>   [  534.252367]  kthread+0x12c/0x140
>   [  534.252374]  ret_from_fork+0x10/0x3c
>   [  534.252386] ---[ end trace a97341262fc57e44 ]---
>
>   And a similar one from 1008.9 (note that most of the time, the stack
>   trace *doesn't* appear hence I'm not sure if it's related to the
>   display freeze itself, or something auxiliary):
>
>   [  221.914617] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [  221.914617] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  221.914795] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [  232.154711] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [  232.154898] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   I can produce this same stack trace, but *without* a corresponding
>   freeze by manually locking the  desktop (Super+L) and waiting for the
>   display fade. However, after the stack trace appears, one can press a
>   key to bring the display back and login again happily. Here are
>   several repeated traces from such activity under the 1008.9 proposed
>   kernel:
>
>   [ 1043.431061] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1043.431136] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1043.431384] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1053.671415] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1053.671705] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1063.911800] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1063.912147] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1181.162739] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1181.418774] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1181.419072] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1191.658996] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1191.659289] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1201.899168] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1201.899438] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1332.461450] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1332.461460] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1332.461717] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1342.701602] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1342.701890] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1352.941798] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
>   [ 1352.942067] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   Note that even when the display is frozen (and cannot be resurrected),
>   only the display driver appears to crash; the system remains
>   operational (at least for some time) happily responding to SSH login
>   requests or, if video is playing, continuing audio output.
>
>   The same occurs with the current linux-firmware-raspi2 release (which
>   the above stack traces were taken from), or with the latest firmware
>   (installed from an experimental package in my
>   https://launchpad.net/~waveform/+archive/ubuntu/firmware PPA).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions
>

Revision history for this message

andrum99 (andrum99) wrote on 2021-10-15 (last edit on 2021-10-15):

#30

Download full text (4.1 KiB)

I'm seeing this on Impish on my machine. Kernel is 5.13.0-1008-raspi #9-Ubuntu. Desktop comes up but then randomly freezes with the following in dmesg:

[ 283.872220] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:83:crtc-4] flip_done timed out
[ 283.872223] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[ 283.872490] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:83:crtc-4] commit wait timed out
[ 294.112288] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[ 294.112576] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:211:plane-26] commit wait timed out
[ 304.352387] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[ 304.352664] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
[ 304.369388] ------------[ cut here ]------------
[ 304.369406] refcount_t: underflow; use-after-free.
[ 304.369447] WARNING: CPU: 1 PID: 22 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
[ 304.369478] Modules linked in: nfnetlink rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm btintel bnep snd_soc_hdmi_codec btsdio bluetooth ecdh_generic ecc vc4 brcmfmac brcmutil input_leds snd_soc_core cfg80211 snd_compress snd_pcm_dmaengine snd_bcm2835(C) snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi raspberrypi_hwmon snd_seq bcm2835_v4l2(C) bcm2835_codec(C) videobuf2_vmalloc snd_seq_device bcm2835_isp(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig snd_timer videobuf2_memops vc_sm_cma(C) videobuf2_v4l2 videobuf2_common videodev snd bcm2835_gpiomem mc rpivid_mem uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq libcrc32c hid_generic usbhid dm_mirror dm_region_hash dm_log spidev v3d crct10dif_ce gpu_sched dwc2 i2c_brcmstb drm_kms_helper roles udc_core i2c_bcm2835 syscopyarea sysfillrect sysimgblt fb_sys_fops spi_bcm2835 cec drm xhci_pci xhci_pci_renesas phy_generic ac97_bus
[ 304.369880] aes_arm64
[ 304.369891] CPU: 1 PID: 22 Comm: kworker/1:0 Tainted: G C 5.13.0-1008-raspi #9-Ubuntu
[ 304.369902] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[ 304.369909] Workqueue: events drm_mode_rmfb_work_fn [drm]
[ 304.370077] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[ 304.370087] pc : refcount_dec_not_one+0xa0/0xbc
[ 304.370098] lr : refcount_dec_not_one+0xa0/0xbc
[ 304.370106] sp : ffff8000100ebb50
[ 304.370110] x29: ffff8000100ebb50 x28: ffff5d76a5c53a00 x27: ffff5d7644e78000
[ 304.370129] x26: ffff5d7644e78000 x25: 0000000000000006 x24: ffff5d7691b91a80
[ 304.370145] x23: ffffdeb5d3dda018 x22: ffff5d76a4ff2980 x21: ffff5d764f18f480
[ 304.370161] x20: ffff5d76a5d835ac x19: ffff5d76a5d83400 x18: 0000000000000000
[ 304.370177] x17: 0000000000000000 x16: ffffdeb62d842574 x15: 0000000000000000
[ 304.370192] x14: 0000000000000000 x13: 0000000000000030 x12: 0000000000004000
[ 304.370208] x11: ffffdeb62e8fdfd0 x10: 00000000fffff000 x9 : ffffdeb62d309f64
[ 304.370223] x8 : 00000000ffffefff x7 : ffffdeb62e8fdfd0 x6 : 0000000000000000
[ 304.370239] x5 : ffff5d76f799f948 x4 : 0000000000000000 x3 : 00...

I'm seeing this on Impish on my machine. Kernel is  5.13.0-1008-raspi #9-Ubuntu. Desktop comes up but then randomly freezes with the following in dmesg:

[  283.872220] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:83:crtc-4] flip_done timed out
[  283.872223] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[  283.872490] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:83:crtc-4] commit wait timed out
[  294.112288] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[  294.112576] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:211:plane-26] commit wait timed out
[  304.352387] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[  304.352664] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
[  304.369388] ------------[ cut here ]------------
[  304.369406] refcount_t: underflow; use-after-free.
[  304.369447] WARNING: CPU: 1 PID: 22 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc
[  304.369478] Modules linked in: nfnetlink rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm btintel bnep snd_soc_hdmi_codec btsdio bluetooth ecdh_generic ecc vc4 brcmfmac brcmutil input_leds snd_soc_core cfg80211 snd_compress snd_pcm_dmaengine snd_bcm2835(C) snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi raspberrypi_hwmon snd_seq bcm2835_v4l2(C) bcm2835_codec(C) videobuf2_vmalloc snd_seq_device bcm2835_isp(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig snd_timer videobuf2_memops vc_sm_cma(C) videobuf2_v4l2 videobuf2_common videodev snd bcm2835_gpiomem mc rpivid_mem uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq libcrc32c hid_generic usbhid dm_mirror dm_region_hash dm_log spidev v3d crct10dif_ce gpu_sched dwc2 i2c_brcmstb drm_kms_helper roles udc_core i2c_bcm2835 syscopyarea sysfillrect sysimgblt fb_sys_fops spi_bcm2835 cec drm xhci_pci xhci_pci_renesas phy_generic ac97_bus
[  304.369880]  aes_arm64
[  304.369891] CPU: 1 PID: 22 Comm: kworker/1:0 Tainted: G         C        5.13.0-1008-raspi #9-Ubuntu
[  304.369902] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[  304.369909] Workqueue: events drm_mode_rmfb_work_fn [drm]
[  304.370077] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[  304.370087] pc : refcount_dec_not_one+0xa0/0xbc
[  304.370098] lr : refcount_dec_not_one+0xa0/0xbc
[  304.370106] sp : ffff8000100ebb50
[  304.370110] x29: ffff8000100ebb50 x28: ffff5d76a5c53a00 x27: ffff5d7644e78000
[  304.370129] x26: ffff5d7644e78000 x25: 0000000000000006 x24: ffff5d7691b91a80
[  304.370145] x23: ffffdeb5d3dda018 x22: ffff5d76a4ff2980 x21: ffff5d764f18f480
[  304.370161] x20: ffff5d76a5d835ac x19: ffff5d76a5d83400 x18: 0000000000000000
[  304.370177] x17: 0000000000000000 x16: ffffdeb62d842574 x15: 0000000000000000
[  304.370192] x14: 0000000000000000 x13: 0000000000000030 x12: 0000000000004000
[  304.370208] x11: ffffdeb62e8fdfd0 x10: 00000000fffff000 x9 : ffffdeb62d309f64
[  304.370223] x8 : 00000000ffffefff x7 : ffffdeb62e8fdfd0 x6 : 0000000000000000
[  304.370239] x5 : ffff5d76f799f948 x4 : 0000000000000000 x3 : 0000000000000027
[  304.370254] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff5d76402add00
[  304.370270] Call trace:
[  304.370274]  refcount_dec_not_one+0xa0/0xbc
[  304.370283]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
[  304.370340]  vc4_cleanup_fb+0x3c/0x4c [vc4]
[  304.370389]  drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper]
[  304.370479]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
[  304.370528]  commit_tail+0xac/0x190 [drm_kms_helper]
[  304.370612]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
[  304.370692]  drm_atomic_commit+0x58/0x70 [drm]
[  304.370847]  atomic_remove_fb+0x2a8/0x2f4 [drm]
[  304.370998]  drm_framebuffer_remove+0x164/0x18c [drm]
[  304.371148]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
[  304.371297]  process_one_work+0x200/0x4d0
[  304.371311]  worker_thread+0x2c8/0x470
[  304.371319]  kthread+0x12c/0x140
[  304.371328]  ret_from_fork+0x10/0x3c
[  304.371339] ---[ end trace 6ac80fe19eebcafd ]---

Revision history for this message

andrum99 (andrum99) wrote on 2021-10-15:

#31

Test kernel from https://kernel.ubuntu.com/~juergh/lp1946368/ fixes it for me 👍

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-15:

#32

@fossfreedom, that is weird. Can you post the log from the failed boot? journalctrl -b -1 or something.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-16:

#33

@fossfreedom, can you also post the binary edid of your monitor? /sys/class/drm/card1-HDMI-A-1/edid

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-17:

#34

fossfreedom edid monitor Edit (256 bytes, application/octet-stream)

Unfortunately there doesnt appear to be any logs produced with the kms boot - just the fkms boot.

I presume logs are not immediately written to the SDCard - checked this via journalctl --list-boots that only shows the fkms session boots

anyway - enc the edid of the monitor

Revision history for this message

andrum99 (andrum99) wrote on 2021-10-18:

#35

Just noticed that with the kernel from https://kernel.ubuntu.com/~juergh/lp1946368/ my Pi 4B is no longer using wayland - Xorg is used instead. Not sure if this is intentional. Ideally wayland would be used for desktop compositing, since there is considerable screen tearing with Xorg.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-18:

#36

@andrum99, that is certainly not intentional. My Pi 4 continues to happily run wayland with that test kernel.

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-18:

#37

@juergh - apologies - I've diagnosed my boot freeze issue - it was a power supply issue. Changing to a brand new supply makes the boot work. KMS must have just tipped the voltage available.

The good news is that installing the 6 debs from the test kernel no longer causes freezes. So congrats on resolving this.

Revision history for this message

William Wilson (jawn-smith) wrote on 2021-10-18:

#38

It seems changing the power supply (along with the test kernel provided by juergh) has resolved my issues as well.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-18:

#39

I like these answers :-) Thanks for helping to nail this down.

Juerg Haefliger (juergh) on 2021-10-18

description:

updated

Juerg Haefliger (juergh) on 2021-10-18

description:

updated

Juerg Haefliger (juergh) on 2021-10-18

Changed in linux-raspi (Ubuntu Impish):
status:	Confirmed → In Progress

Revision history for this message

Benjamin Lupton (balupton) wrote on 2021-10-18:

#40

I'm also experiencing this on a non-critical raspberry pi 400 setup. I'm pondering whether I can wait for the test kernel fix to be released in a more mainstream way - are we talking days, weeks, or months for those changes to get out to mainstream?

Revision history for this message

andrum99 (andrum99) wrote on 2021-10-18:

#41

Apologies - the problem with my Pi 4B desktop reverting to X11 when I installed the kernel packages from https://kernel.ubuntu.com/~juergh/lp1946368/ was caused by a problem with my boot/root drive, which is an SSD in a USB 3 enclosure. For some reason it doesn't work quite right with UAS mode, having worked fine with spinning rust (hard disk) previously in UAS mode.

Setting the relevant quirk to disable UAS mode before booting Ubuntu 21.10 on the Pi 4B fixes the problem, and once the kernel from https://kernel.ubuntu.com/~juergh/lp1946368/ is installed the desktop stops freezing 👍 and uses wayland 👍

Revision history for this message

andrum99 (andrum99) wrote on 2021-10-18:

#42

Can you tell me how to get ZFS back? Installing the kernel packages from https://kernel.ubuntu.com/~juergh/lp1946368/ results in the ZFS modules being deleted from my system. It looks like the modules are missing from the version of the linux-modules-5.13.0-1008-raspi package at https://kernel.ubuntu.com/~juergh/lp1946368/.

Revision history for this message

fprietog (fprietog) wrote on 2021-10-18 (last edit on 2021-10-18):

#43

@andrum99

Probably not related to the missing zfs module in the testing package but be warned that there is a warning for the current impish zfs kennel module:

=== Attention: ZFS kernel panic mitigation ===

"The version of the ZFS driver included in the 5.13.0-19 kernel contains a bug that can result in filesystem corruption. Users of ZFS are advised to wait until the first Stable Release Update of the kernel in 21.10 before upgrading." Trent Lloyd's long standing bug report of the ZFS kernel panic is mitigated with the 5.13.0-20 impish-proposed kernel.

https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476

Revision history for this message

andrum99 (andrum99) wrote on 2021-10-18:

#44

@fprietog Thanks for the heads up.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-19:

#45

@andrum99, my test kernel doesn't include zfs modules. The final release kernel will do though.

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-19:

#46

@balupton, the plan is to roll the fixes into the current SRU cycle with a release to -updates on 8 Nov (per https://kernel.ubuntu.com/). Kernel prep is this week so you can expect something in -proposed by the end of this week.

Changed in linux-raspi (Ubuntu Impish):
status:	In Progress → Fix Committed

Revision history for this message

Benjamin Lupton (balupton) wrote on 2021-10-22:

#47

Thanks. Could you post back with step by step instructions for a semi-technical user on how to install the fix kernel when it lands in proposed?

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-22:

#48

Once it's in proposed:
$ sudo apt-add-repository -p proposed
$ sudo apt install linux-raspi

And then if you want to remove proposed again:
$ sudo apt-add-repository -r -p proposed

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-22:

#49

I reinstalled my Ubuntu-Budgie 21.10.
All updates are on October 22. 2021.
Proposed channel is activated.

Executed this order!

$ sudo apt install linux-raspi

Unfortunately, no improvement!
In fkms mode the video playback works.
With kms mode, the system, the video, the mouse pointer in spite of update freezes again and only Power-Off gets the Raspi 4b 8GB running again.

$ uname -a
Linux rw-rpi0 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-22:

#50

Download full text (11.3 KiB)

The fix is not yet in proposed.

Everyone will be notified when it is via a post on this thread asking for
it to be tested.

On Fri, 22 Oct 2021, 16:25 knoedel fan, <email address hidden> wrote:

> I reinstalled my Ubuntu-Budgie 21.10.
> All updates are on October 22. 2021.
> Proposed channel is activated.
>
> Executed this order!
>
> $ sudo apt install linux-raspi
>
> Unfortunately, no improvement!
> In fkms mode the video playback works.
> With kms mode, the system, the video, the mouse pointer in spite of update
> freezes again and only Power-Off gets the Raspi 4b 8GB running again.
>
> $ uname -a
> Linux rw-rpi0 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44
> UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
> HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
> Confirmed
> Status in linux-raspi source package in Impish:
> Fix Committed
>
> Bug description:
> [Impact]
>
> The UI of Impish desktop for raspi occasionally freezes which can be
> triggered by playing videos and moving windows around. Seems to happen
> more frequently when using higher resolutions and/or higher refresh
> rates (higher than 1920x1080@60Hz).
>
> Kernel errors are along the lines of:
> [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
> [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
> mmit wait timed out
> [ 513.762381] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
> done timed out
>
> [Test Case]
>
> Install current Impish desktop for raspi on a Pi 4. Use a high-
> refresh/resolution monitor. Play videos, move windows around.
>
> [Fix]
>
> The Pi foundation identified a couple of upstream vc4 commits that
> seem to interfere with their downstream patches. Revert those to match
> the Pi foundations currently released 5.10 kernel.
>
> [Where Problems Could Occur]
>
> The changes are confined to the vc4 driver, so problems would only
> show up if that driver is in use. Which is only the case for the
> Ubuntu raspi desktop image, so server images should not be impacted at
> all.
>
> [Original Description]
>
> Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
> for the Ubuntu Pi pre-installed desktop impish release, the HDMI
> output occasionally freezes. A known workaround at this time is to
> change the following line in /boot/firmware/config.txt:
>
> dtoverlay=vc4-kms-v3d
>
> To the following:
>
> dtoverlay=vc4-fkms-v3d
>
> In other words, to use the "fake" KMS overlay (fkms) instead of the
> "full" KMS overlay (kms).
>
> I've been unable to determine a reliable method of guaranteeing a
> freeze, but it appears to occur much more readily when video playback
> is occurring, and when other interactions (especially moving windows
> around, minimizing, restoring) occurs simultaneously. Display suspend
> also periodically causes...

The fix is not yet in proposed.

Everyone will be notified when it is via a post on this thread asking for
it to be tested.

On Fri, 22 Oct 2021, 16:25 knoedel fan, <1946368@bugs.launchpad.net> wrote:

> I reinstalled my Ubuntu-Budgie 21.10.
> All updates are on October 22. 2021.
> Proposed channel is activated.
>
> Executed this order!
>
> $ sudo apt install linux-raspi
>
> Unfortunately, no improvement!
> In fkms mode the video playback works.
> With kms mode, the system, the video, the mouse pointer in spite of update
> freezes again and only Power-Off gets the Raspi 4b 8GB running again.
>
> $ uname -a
> Linux rw-rpi0 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44
> UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946368
>
> Title:
>   HDMI output freezes under current/proposed impish kernels
>
> Status in linux-raspi package in Ubuntu:
>   Confirmed
> Status in linux-raspi source package in Impish:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   The UI of Impish desktop for raspi occasionally freezes which can be
>   triggered by playing videos and moving windows around. Seems to happen
>   more frequently when using higher resolutions and/or higher refresh
>   rates (higher than 1920x1080@60Hz).
>
>   Kernel errors are along the lines of:
>   [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
>   mmit wait timed out
>   [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
>   done timed out
>
>   [Test Case]
>
>   Install current Impish desktop for raspi on a Pi 4. Use a high-
>   refresh/resolution monitor. Play videos, move windows around.
>
>   [Fix]
>
>   The Pi foundation identified a couple of upstream vc4 commits that
>   seem to interfere with their downstream patches. Revert those to match
>   the Pi foundations currently released 5.10 kernel.
>
>   [Where Problems Could Occur]
>
>   The changes are confined to the vc4 driver, so problems would only
>   show up if that driver is in use. Which is only the case for the
>   Ubuntu raspi desktop image, so server images should not be impacted at
>   all.
>
>   [Original Description]
>
>   Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
>   for the Ubuntu Pi pre-installed desktop impish release, the HDMI
>   output occasionally freezes. A known workaround at this time is to
>   change the following line in /boot/firmware/config.txt:
>
>   dtoverlay=vc4-kms-v3d
>
>   To the following:
>
>   dtoverlay=vc4-fkms-v3d
>
>   In other words, to use the "fake" KMS overlay (fkms) instead of the
>   "full" KMS overlay (kms).
>
>   I've been unable to determine a reliable method of guaranteeing a
>   freeze, but it appears to occur much more readily when video playback
>   is occurring, and when other interactions (especially moving windows
>   around, minimizing, restoring) occurs simultaneously.  Display suspend
>   also periodically causes the same hang, which made me suspect this
>   might be related to #1944397 but it appears that had a separate cause
>   (now resolved).
>
>   The following dmesg outputs have been observed immediately after the
>   display hang; this one from 1007.8:
>
>   [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co
>   mmit wait timed out
>   [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_
>   done timed out
>   [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [PLANE:205:plane-25
>   ] commit wait timed out
>   [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [  534.250685] ------------[ cut here ]------------
>   [  534.250701] refcount_t: underflow; use-after-free.
>   [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87
> refcount_dec_not_one+0xa0/0xbc
>   [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher
> af_alg hci_uart btqca btrtl btbcm
>    btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds
> bluetooth snd_compress snd_bcm2835(C)
>    snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi
> snd_seq_midi_event bcm2835_codec(C) bcm
>   2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem
> bcm2835_mmal_vchiq(C) videobuf2_dma_contig
>   videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq
> videobuf2_common videodev snd_seq_devi
>   ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem
> rpivid_mem uio_pdrv_genirq uio sch_fq_
>   codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon
> zstd_compress hid_generic usbhid raid
>   6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles
> udc_core gpu_sched crct10dif_ce i2c_
>   brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci
> xhci_pci_renesas sysfillrect sysimgbl
>   t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
>   [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: G        WC
>     5.13.0-1007-raspi #8-Ubuntu
>   [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
>   [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
>   [  534.251239] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
>   [  534.251248] pc : refcount_dec_not_one+0xa0/0xbc
>   [  534.251257] lr : refcount_dec_not_one+0xa0/0xbc
>   [  534.251265] sp : ffff8000118cbb50
>   [  534.251269] x29: ffff8000118cbb50 x28: ffff6cf7ee894400 x27:
> ffff6cf80502e000
>   [  534.251285] x26: ffff6cf80502e000 x25: 0000000000000006 x24:
> ffff6cf7ee94c500
>   [  534.251300] x23: ffffa94dff246018 x22: ffff6cf833068880 x21:
> ffff6cf805027c80
>   [  534.251314] x20: ffff6cf88ead75ac x19: ffff6cf88ead7400 x18:
> 0000000000000000
>   [  534.251328] x17: 0000000000000000 x16: ffffa94e0a243314 x15:
> 0000000000000000
>   [  534.251342] x14: 0000000000000000 x13: 0000000000000030 x12:
> ffff800010035000
>   [  534.251356] x11: ffffa94e0b30dfd0 x10: 00000000fffff000 x9 :
> ffffa94e09d09f54
>   [  534.251370] x8 : 00000000ffffefff x7 : ffffa94e0b30dfd0 x6 :
> 0000000000000000
>   [  534.251384] x5 : ffff6cf8b799f948 x4 : 0000000000000000 x3 :
> 0000000000000027
>   [  534.251397] x2 : 0000000000000000 x1 : 0000000000000000 x0 :
> ffff6cf800abec80
>   [  534.251411] Call trace:
>   [  534.251416]  refcount_dec_not_one+0xa0/0xbc
>   [  534.251424]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
>   [  534.251473]  vc4_cleanup_fb+0x3c/0x4c [vc4]
>   [  534.251518]  drm_atomic_helper_cleanup_planes+0x74/0xa0
> [drm_kms_helper]
>   [  534.251604]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
>   [  534.251648]  commit_tail+0xac/0x190 [drm_kms_helper]
>   [  534.251723]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
>   [  534.251796]  drm_atomic_commit+0x58/0x70 [drm]
>   [  534.251936]  atomic_remove_fb+0x2a8/0x2f4 [drm]
>   [  534.252073]  drm_framebuffer_remove+0x164/0x18c [drm]
>   [  534.252209]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
>   [  534.252346]  process_one_work+0x200/0x4d0
>   [  534.252359]  worker_thread+0x2c8/0x470
>   [  534.252367]  kthread+0x12c/0x140
>   [  534.252374]  ret_from_fork+0x10/0x3c
>   [  534.252386] ---[ end trace a97341262fc57e44 ]---
>
>   And a similar one from 1008.9 (note that most of the time, the stack
>   trace *doesn't* appear hence I'm not sure if it's related to the
>   display freeze itself, or something auxiliary):
>
>   [  221.914617] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [  221.914617] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [  221.914795] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [  232.154711] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [  232.154898] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   I can produce this same stack trace, but *without* a corresponding
>   freeze by manually locking the  desktop (Super+L) and waiting for the
>   display fade. However, after the stack trace appears, one can press a
>   key to bring the display back and login again happily. Here are
>   several repeated traces from such activity under the 1008.9 proposed
>   kernel:
>
>   [ 1043.431061] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1043.431136] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1043.431384] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1053.671415] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1053.671705] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1063.911800] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1063.912147] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1181.162739] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1181.418774] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1181.419072] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1191.658996] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1191.659289] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1201.899168] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1201.899438] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>   [ 1332.461450] [drm:drm_atomic_helper_wait_for_flip_done
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
>   [ 1332.461460] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1332.461717] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out
>   [ 1342.701602] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1342.701890] [drm:drm_atomic_helper_wait_for_dependencies
> [drm_kms_helper]] *ERROR* [PLANE:70:plane-3] commit wait timed out
>   [ 1352.941798] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed
> out
>   [ 1352.942067] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
>
>   Note that even when the display is frozen (and cannot be resurrected),
>   only the display driver appears to crash; the system remains
>   operational (at least for some time) happily responding to SSH login
>   requests or, if video is playing, continuing audio output.
>
>   The same occurs with the current linux-firmware-raspi2 release (which
>   the above stack traces were taken from), or with the latest firmware
>   (installed from an experimental package in my
>   https://launchpad.net/~waveform/+archive/ubuntu/firmware PPA).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions
>
>

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-22 (last edit on 2021-10-22):

#51

I reinstalled my Ubuntu-Budgie 21.10 Desktop!!!!!! Not Ubuntu 21.10 Desktop!!!!
All updates are on October 22. 2021.
Proposed channel is activated.

Executed this order!

$ sudo apt install linux-raspi
$ sudo reboot

Unfortunately, no improvement!
In fkms mode the video playback works.
With kms mode, the system, the video, the mouse pointer in spite of update freezes again and only Power-Off gets the Raspi 4b 8GB running again.

$ uname -a
Linux rw-rpi0 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

$ rpi-eeprom-update
BOOTLOADER: up to date
   CURRENT: Do 29. Apr 16:11:25 UTC 2021 (1619712685)
    LATEST: Do 29. Apr 16:11:25 UTC 2021 (1619712685)
   RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
            Use raspi-config to change the release.

  VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 000138a1
    LATEST: 000138a1

Revision history for this message

Costin Botescu (colin-i) wrote on 2021-10-23:

#52

@knoedelfan
The fix is not already there.
You have "5.13.0-1008-raspi #9-Ubuntu" released on 2021-10-11.
When you "install" now you see "linux-raspi is already the newest version".

Revision history for this message

Tim Halloran (hallorant) wrote on 2021-10-23:

#53

Also having this problem, it seems to trigger immediately on dual monitors on a pi 4 (8G). I can get it to go for a bit on one monitor.

Ganesh Chandar Devulapalli (ganeshcd) on 2021-10-27

Changed in linux-raspi (Ubuntu Impish):
status:	Fix Committed → Fix Released

Revision history for this message

fossfreedom (fossfreedom) wrote on 2021-10-27:

#54

I have no idea why the status has changed ... the fix hasn't entered the archive yet.

Changed in linux-raspi (Ubuntu Impish):
status:	Fix Released → Fix Committed

Revision history for this message

Andy Valley (andyinthevalley) wrote on 2021-10-27:

#55

Just upgraded, still crashes same as before.

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-28 (last edit on 2021-10-28):

#56

Do you mean the problem with fkms vs. kms?
I installed an update this morning.
Ubuntu-Budgie 21. 10 proposed.

Then switched to kms and the Raspi Pi 4 restarted.

Video started and after 3 seconds the video freezes, BT audio output stops, mouse pointer freezes.

As soon as I move the mouse pointer, it happens instantly.

Revision history for this message

Viktor G. (viktor-g) wrote on 2021-10-28 (last edit on 2021-10-28):

#57

5.13.0.1009.15 unfortunately does not improve the problem.
(fresh installed ubuntu 21.10 desktop and rpi4 4gb)

Revision history for this message

Juerg Haefliger (juergh) wrote on 2021-10-28:

#58

-1009 does not include the HDMI fix. That's just an in-between release to support the new Pi Zero 2 device that was just announced today. -1010 is the fixed version. It's currently building and should reach proposed later today or tomorrow.

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-28:

#59

Vielen Dank Juerg für diese Info!

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2021-10-29:

#60

This bug is awaiting verification that the linux-raspi/5.13.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: verification-needed-impish

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-29 (last edit on 2021-10-29):

#61

robert@rw-rpi0:~$ uname -a
Linux rw-rpi0 5.13.0-1010-raspi #11-Ubuntu SMP PREEMPT Thu Oct 28 08:32:52 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Update (proposed) for Ubuntu-Budgie 21.10 Raspberry Pi 4B 8GB.

config.txt in kms-mode
Screen without Audio plugged to HDMI1
Audio over BT-Loudspeaker

Video and audio run synchronously in kms mode. Without issue.
Bug is fixed.
Test in Mozilla Firefox. Video and audio run synchronously in kms mode without issue.
Bug is fixed.

Many thanks to the Team from Ubuntu!

tags: added: verification-done-impish

Revision history for this message

fprietog (fprietog) wrote on 2021-10-29:

#62

Tested:
Linux fpgrpi 5.13.0-1010-raspi #11-Ubuntu SMP PREEMPT Thu Oct 28 08:32:52 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Environments tested: X11 and wayland

Problem is solved!

tags:

added: verification-done-impish
removed: verification-needed-impish

Revision history for this message

wendellgee (wendellgee) wrote on 2021-10-29:

#63

Confirming, the problem seems to be solved.

Tested:

driver: dtoverlay=vc4-kms-v3d

uname -a
Linux u2110rpi 5.13.0-1010-raspi #11-Ubuntu SMP PREEMPT Thu Oct 28 08:32:52 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

No freeze for both Wayland and X11.

Big thank you Ubuntu Team!

Revision history for this message

Daniel Johnsen (err0rtpl0x) wrote on 2021-10-30:

#64

Anyone who can explain to a noob how to install the kernel? i run Ubuntu desktop 21.10 on raspberry pi 400. Im pretty new to all this.

Revision history for this message

knoedel fan (knoedelfan) wrote on 2021-10-30 (last edit on 2021-10-30):

#65

Daniel: You have to activate the developer options inside the update management. Only then, you get the update from propose canal! A normal update does not help without a development option. This option you get when click settings in Main window of update management ( Software & Updates program ).
After switch on development option new package are reading into your system. After ending this download you can click ok from update management to start a search for new updates inside propose canal. This update is a pre-release.

Read this too: https://wiki.ubuntu.com/Testing/EnableProposed

Revision history for this message

Daniel Johnsen (err0rtpl0x) wrote on 2021-10-30:

#66

Knoedel: Thank you, i actually just downloaded the 2 deb files from https://kernel.ubuntu.com/~juergh/lp1946368/ and rebooted my pi, and havnt ran into any freezing issues after this.

Revision history for this message

Ak (cwo99) wrote on 2021-11-01:

#67

When it will be published to the updates channel? Can't find any information about the release cycle.

Revision history for this message

Viktor G. (viktor-g) wrote on 2021-11-01:

#68

I think 8th november.
(Link: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/comments/46 )

Revision history for this message

Dennis Golden (dlgintx) wrote on 2021-11-02:

#69

config.text for test Edit (1.3 KiB, text/plain)

Either I did something wrong, or it doesn't work for me. I followed these steps:
$ sudo apt-add-repository -p proposed
$ sudo apt install linux-raspi

uname -a output:
Linux ubuntu 5.13.0-1010-raspi #11-Ubuntu SMP PREEMPT Thu Oct 28 08:32:52 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

After the rainbow splash, cursor blinking waiting for boot the screen goes black and shows no signal.

Output of ls -l boot and rpi-eeprom-update:
ubuntu@ubuntu:~$ ls -l /boot
total 66888
-rw------- 1 root root 5112454 Oct 25 08:22 System.map-5.13.0-1009-raspi
-rw------- 1 root root 5110476 Oct 28 02:59 System.map-5.13.0-1010-raspi
-rw-r--r-- 1 root root 241336 Oct 25 08:22 config-5.13.0-1009-raspi
-rw-r--r-- 1 root root 241266 Oct 28 02:59 config-5.13.0-1010-raspi
lrwxrwxrwx 1 root root 44 Nov 1 20:14 dtb -> dtbs/5.13.0-1010-raspi/./bcm2711-rpi-4-b.dtb
lrwxrwxrwx 1 root root 44 Oct 31 20:22 dtb-5.13.0-1009-raspi -> dtbs/5.13.0-1009-raspi/./bcm2711-rpi-4-b.dtb
lrwxrwxrwx 1 root root 44 Nov 1 20:14 dtb-5.13.0-1010-raspi -> dtbs/5.13.0-1010-raspi/./bcm2711-rpi-4-b.dtb
drwxr-xr-x 4 root root 4096 Nov 1 20:14 dtbs
drwxr-xr-x 4 root root 7680 Dec 31 1969 firmware
lrwxrwxrwx 1 root root 28 Nov 1 20:13 initrd.img -> initrd.img-5.13.0-1010-raspi
-rw-r--r-- 1 root root 19391282 Oct 31 20:21 initrd.img-5.13.0-1009-raspi
-rw-r--r-- 1 root root 19390433 Nov 1 20:14 initrd.img-5.13.0-1010-raspi
lrwxrwxrwx 1 root root 28 Nov 1 20:13 initrd.img.old -> initrd.img-5.13.0-1009-raspi
lrwxrwxrwx 1 root root 25 Nov 1 20:13 vmlinuz -> vmlinuz-5.13.0-1010-raspi
-rw------- 1 root root 9491368 Oct 25 08:22 vmlinuz-5.13.0-1009-raspi
-rw------- 1 root root 9489364 Oct 28 02:59 vmlinuz-5.13.0-1010-raspi
lrwxrwxrwx 1 root root 25 Nov 1 20:13 vmlinuz.old -> vmlinuz-5.13.0-1009-raspi
ubuntu@ubuntu:~$ sudo rpi-eeprom-update
BOOTLOADER: up to date
   CURRENT: Thu Apr 29 16:11:25 UTC 2021 (1619712685)
    LATEST: Thu Apr 29 16:11:25 UTC 2021 (1619712685)
   RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
            Use raspi-config to change the release.

  VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 000138a1
    LATEST: 000138a1

Either I did something wrong, or it doesn't work for me. I followed these steps:
$ sudo apt-add-repository -p proposed
$ sudo apt install linux-raspi

uname -a output:
Linux ubuntu 5.13.0-1010-raspi #11-Ubuntu SMP PREEMPT Thu Oct 28 08:32:52 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

After the rainbow splash, cursor blinking waiting for boot the screen goes black and shows no signal.

Output of ls -l boot and rpi-eeprom-update:
ubuntu@ubuntu:~$ ls -l /boot
total 66888
-rw------- 1 root root  5112454 Oct 25 08:22 System.map-5.13.0-1009-raspi
-rw------- 1 root root  5110476 Oct 28 02:59 System.map-5.13.0-1010-raspi
-rw-r--r-- 1 root root   241336 Oct 25 08:22 config-5.13.0-1009-raspi
-rw-r--r-- 1 root root   241266 Oct 28 02:59 config-5.13.0-1010-raspi
lrwxrwxrwx 1 root root       44 Nov  1 20:14 dtb -> dtbs/5.13.0-1010-raspi/./bcm2711-rpi-4-b.dtb
lrwxrwxrwx 1 root root       44 Oct 31 20:22 dtb-5.13.0-1009-raspi -> dtbs/5.13.0-1009-raspi/./bcm2711-rpi-4-b.dtb
lrwxrwxrwx 1 root root       44 Nov  1 20:14 dtb-5.13.0-1010-raspi -> dtbs/5.13.0-1010-raspi/./bcm2711-rpi-4-b.dtb
drwxr-xr-x 4 root root     4096 Nov  1 20:14 dtbs
drwxr-xr-x 4 root root     7680 Dec 31  1969 firmware
lrwxrwxrwx 1 root root       28 Nov  1 20:13 initrd.img -> initrd.img-5.13.0-1010-raspi
-rw-r--r-- 1 root root 19391282 Oct 31 20:21 initrd.img-5.13.0-1009-raspi
-rw-r--r-- 1 root root 19390433 Nov  1 20:14 initrd.img-5.13.0-1010-raspi
lrwxrwxrwx 1 root root       28 Nov  1 20:13 initrd.img.old -> initrd.img-5.13.0-1009-raspi
lrwxrwxrwx 1 root root       25 Nov  1 20:13 vmlinuz -> vmlinuz-5.13.0-1010-raspi
-rw------- 1 root root  9491368 Oct 25 08:22 vmlinuz-5.13.0-1009-raspi
-rw------- 1 root root  9489364 Oct 28 02:59 vmlinuz-5.13.0-1010-raspi
lrwxrwxrwx 1 root root       25 Nov  1 20:13 vmlinuz.old -> vmlinuz-5.13.0-1009-raspi
ubuntu@ubuntu:~$ sudo rpi-eeprom-update 
BOOTLOADER: up to date
   CURRENT: Thu Apr 29 16:11:25 UTC 2021 (1619712685)
    LATEST: Thu Apr 29 16:11:25 UTC 2021 (1619712685)
   RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
            Use raspi-config to change the release.

VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 000138a1
    LATEST: 000138a1

Revision history for this message

Dennis Golden (dlgintx) wrote on 2021-11-02:

#70

BTW: I should say that I am using the plasma desktop, but this is is failing before anything is running. The network is up and will respond to ping, but won't accept a connection.

Revision history for this message

Dennis Golden (dlgintx) wrote on 2021-11-03:

#71

Okay, I started with fresh desktop install. It hung one time before I was able to update the kernel. So far it's running as it should.

Thank you all for your comments and guidance.

Revision history for this message

ko4la (ko4la) wrote on 2021-11-06:

#72

Thx a lot.

Same here therefore I used this :
$ sudo apt-add-repository -p proposed
$ sudo apt install linux-raspi
$ sudo apt-add-repository -r -p proposed
$ sudo reboot

No more issue.

Revision history for this message

Lloyd E James (edjames1950) wrote on 2021-11-06:

#73

To make life easier, on the problem Ubuntu machine, I installed ssh server:
sudo apt install openssh-server
and left an open ssh connection to it from another RPi.
When the Ubuntu machine display froze, the OS itself was still running, and from other machine, I unlocked the Ubuntu lockup with
sudo service gdm restart
I don't like rebooting a machine by cutting power for ... reasons.
I've not tried the s/kms/fkms trick yet, but I am doing daily updates. I'm also getting a lot up uptime between freezes.

Revision history for this message

Costin Botescu (colin-i) wrote on 2021-11-07:

#74

Write fkms to config.txt from boot partition before inserting the sd card. Then install linux-raspi from proposed or wait for updates. Then revert to kms.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-11-17:

#75

Download full text (25.3 KiB)

This bug was fixed in the package linux-raspi - 5.13.0-1010.12

---------------
linux-raspi (5.13.0-1010.12) impish; urgency=medium

* impish/linux-raspi: 5.13.0-1010.12 -proposed tracker (LP: #1950142)

  * [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
    5.13.0-1010.11-raspi (LP: #1950117)
    - firmware: raspberrypi: Partially revert 'firmware: bcm2835: Support
      ARCH_BCM270x'

* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md

  * HDMI output freezes under current/proposed impish kernels (LP: #1946368)
    - Revert "drm/vc4: Increase the core clock to a minimum of 500MHz"
    - Revert "drm/vc4: Increase the core clock based on HVS load"
    - Revert "drm/vc4: fix vc4_atomic_commit_tail() logic"
    - Revert "drm: Introduce a drm_crtc_commit_wait helper"
    - Revert "drm/vc4: kms: Convert to atomic helpers"
    - Revert "drm/vc4: kms: Remove async modeset semaphore"
    - Revert "drm/vc4: kms: Remove unassigned_channels from the HVS state"
    - Revert "drm/vc4: kms: Wait on previous FIFO users before a commit"
    - drm/vc4: Increase the core clock based on HVS load
    - drm/vc4: Increase the core clock to a minimum of 500MHz

[ Ubuntu: 5.13.0-21.21 ]

  * impish/linux: 5.13.0-21.21 -proposed tracker (LP: #1947347)
  * It hangs while booting up with AMD W6800 [1002:73A3] (LP: #1945553)
    - drm/amdgpu: Rename flag which prevents HW access
    - drm/amd/pm: Fix a bug communicating with the SMU (v5)
    - drm/amd/pm: Fix a bug in semaphore double-lock
  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check
  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2
  * Check for changes relevant for security certifications (LP: #1945989)
    - [Packaging] Add a new fips-checks script
    - [Packaging] Add fips-checks as part of finalchecks
  * BCM57800 SRIOV bug causes interfaces to disappear (LP: #1945707)
    - bnx2x: Fix enabling network interfaces without VFs
  * CVE-2021-3759
    - memcg: enable accounting of ipc resources
  * [impish] Remove the downstream xr-usb-uart driver (LP: #1945938)
    - SAUCE: xr-usb-serial: remove driver
    - [Config] update modules list
  * Fix A yellow screen pops up in an instant (< 1 second) and then disappears
    before loading the system (LP: #1945932)
    - drm/i915: Stop force enabling pipe bottom color gammma/csc
  * Impish update: v5.13.18 upstream stable release (LP: #1946249)
    - Linux 5.13.18
  * Impish update: v5.13.17 upstream stable release (LP: #1946247)
    - locking/mutex: Fix HANDOFF condition
    - regmap: fix the offset of register error log
    - regulator: tps65910: Silence deferred probe error
    - crypto: mxs-dcp - Check for DMA mapping errors
    - sched/deadline: Fix reset_on_fork reporting of DL tasks
    - power: supply: axp288_fuel_gauge: Report register-address on readb / writeb
      ...

This bug was fixed in the package linux-raspi - 5.13.0-1010.12

---------------
linux-raspi (5.13.0-1010.12) impish; urgency=medium

* impish/linux-raspi: 5.13.0-1010.12 -proposed tracker (LP: #1950142)

* [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
    5.13.0-1010.11-raspi (LP: #1950117)
    - firmware: raspberrypi: Partially revert 'firmware: bcm2835: Support
      ARCH_BCM270x'

* Packaging resync (LP: #1786013)
    - [Packaging] update Ubuntu.md

* HDMI output freezes under current/proposed impish kernels (LP: #1946368)
    - Revert "drm/vc4: Increase the core clock to a minimum of 500MHz"
    - Revert "drm/vc4: Increase the core clock based on HVS load"
    - Revert "drm/vc4: fix vc4_atomic_commit_tail() logic"
    - Revert "drm: Introduce a drm_crtc_commit_wait helper"
    - Revert "drm/vc4: kms: Convert to atomic helpers"
    - Revert "drm/vc4: kms: Remove async modeset semaphore"
    - Revert "drm/vc4: kms: Remove unassigned_channels from the HVS state"
    - Revert "drm/vc4: kms: Wait on previous FIFO users before a commit"
    - drm/vc4: Increase the core clock based on HVS load
    - drm/vc4: Increase the core clock to a minimum of 500MHz

[ Ubuntu: 5.13.0-21.21 ]

* impish/linux: 5.13.0-21.21 -proposed tracker (LP: #1947347)
  * It hangs while booting up with AMD W6800 [1002:73A3] (LP: #1945553)
    - drm/amdgpu: Rename flag which prevents HW access
    - drm/amd/pm: Fix a bug communicating with the SMU (v5)
    - drm/amd/pm: Fix a bug in semaphore double-lock
  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check
  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2
  * Check for changes relevant for security certifications (LP: #1945989)
    - [Packaging] Add a new fips-checks script
    - [Packaging] Add fips-checks as part of finalchecks
  * BCM57800 SRIOV bug causes interfaces to disappear (LP: #1945707)
    - bnx2x: Fix enabling network interfaces without VFs
  * CVE-2021-3759
    - memcg: enable accounting of ipc resources
  * [impish] Remove the downstream xr-usb-uart driver (LP: #1945938)
    - SAUCE: xr-usb-serial: remove driver
    - [Config] update modules list
  * Fix A yellow screen pops up in an instant (< 1 second) and then disappears
    before loading the system (LP: #1945932)
    - drm/i915: Stop force enabling pipe bottom color gammma/csc
  * Impish update: v5.13.18 upstream stable release (LP: #1946249)
    - Linux 5.13.18
  * Impish update: v5.13.17 upstream stable release (LP: #1946247)
    - locking/mutex: Fix HANDOFF condition
    - regmap: fix the offset of register error log
    - regulator: tps65910: Silence deferred probe error
    - crypto: mxs-dcp - Check for DMA mapping errors
    - sched/deadline: Fix reset_on_fork reporting of DL tasks
    - power: supply: axp288_fuel_gauge: Report register-address on readb / writeb
      errors
    - crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop()
    - sched/deadline: Fix missing clock update in migrate_task_rq_dl()
    - rcu/tree: Handle VM stoppage in stall detection
    - EDAC/mce_amd: Do not load edac_mce_amd module on guests
    - hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns()
    - hrtimer: Ensure timerfd notification for HIGHRES=n
    - udf: Check LVID earlier
    - udf: Fix iocharset=utf8 mount option
    - isofs: joliet: Fix iocharset=utf8 mount option
    - bcache: add proper error unwinding in bcache_device_init
    - nbd: add the check to prevent overflow in __nbd_ioctl()
    - blk-throtl: optimize IOPS throttle for large IO scenarios
    - nvme-tcp: don't update queue count when failing to set io queues
    - nvme-rdma: don't update queue count when failing to set io queues
    - nvmet: pass back cntlid on successful completion
    - power: supply: smb347-charger: Add missing pin control activation
    - power: supply: max17042_battery: fix typo in MAx17042_TOFF
    - s390/cio: add dev_busid sysfs entry for each subchannel
    - s390/zcrypt: fix wrong offset index for APKA master key valid state
    - libata: fix ata_host_start()
    - sched/topology: Skip updating masks for non-online nodes
    - crypto: omap - Fix inconsistent locking of device lists
    - crypto: qat - do not ignore errors from enable_vf2pf_comms()
    - crypto: qat - handle both source of interrupt in VF ISR
    - crypto: qat - fix reuse of completion variable
    - crypto: qat - fix naming for init/shutdown VF to PF notifications
    - crypto: qat - do not export adf_iov_putmsg()
    - crypto: hisilicon/sec - fix the abnormal exiting process
    - crypto: hisilicon/sec - modify the hardware endian configuration
    - crypto: tcrypt - Fix missing return value check
    - fcntl: fix potential deadlocks for &fown_struct.lock
    - fcntl: fix potential deadlock for &fasync_struct.fa_lock
    - udf_get_extendedattr() had no boundary checks.
    - io-wq: remove GFP_ATOMIC allocation off schedule out path
    - s390/kasan: fix large PMD pages address alignment check
    - s390/pci: fix misleading rc in clp_set_pci_fn()
    - s390/debug: keep debug data on resize
    - s390/debug: fix debug area life cycle
    - s390/ap: fix state machine hang after failure to enable irq
    - sched/debug: Don't update sched_domain debug directories before
      sched_debug_init()
    - power: supply: cw2015: use dev_err_probe to allow deferred probe
    - m68k: emu: Fix invalid free in nfeth_cleanup()
    - crypto: x86/aes-ni - add missing error checks in XTS code
    - crypto: ecc - handle unaligned input buffer in ecc_swap_digits
    - sched/numa: Fix is_core_idle()
    - sched: Fix UCLAMP_FLAG_IDLE setting
    - rcu: Fix to include first blocked task in stall warning
    - rcu: Fix stall-warning deadlock due to non-release of rcu_node ->lock
    - m68k: Fix invalid RMW_INSNS on CPUs that lack CAS
    - block: return ELEVATOR_DISCARD_MERGE if possible
    - spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config
    - spi: spi-pic32: Fix issue with uninitialized dma_slave_config
    - genirq/timings: Fix error return code in irq_timings_test_irqs()
    - irqchip/loongson-pch-pic: Improve edge triggered interrupt support
    - lib/mpi: use kcalloc in mpi_resize
    - clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock
      source channel
    - block: nbd: add sanity check for first_minor
    - spi: coldfire-qspi: Use clk_disable_unprepare in the remove function
    - irqchip/apple-aic: Fix irq_disable from within irq handlers
    - irqchip/gic-v3: Fix priority comparison when non-secure priorities are used
    - crypto: qat - use proper type for vf_mask
    - certs: Trigger creation of RSA module signing key if it's not an RSA key
    - tpm: ibmvtpm: Avoid error message when process gets signal while waiting
    - io_uring: refactor io_submit_flush_completions()
    - x86/mce: Defer processing of early errors
    - spi: davinci: invoke chipselect callback
    - blk-crypto: fix check for too-large dun_bytes
    - regulator: vctrl: Use locked regulator_get_voltage in probe path
    - regulator: vctrl: Avoid lockdep warning in enable/disable ops
    - spi: sprd: Fix the wrong WDG_LOAD_VAL
    - spi: spi-zynq-qspi: use wait_for_completion_timeout to make
      zynq_qspi_exec_mem_op not interruptible
    - crypto: rmd320 - remove rmd320 in Makefile
    - EDAC/i10nm: Fix NVDIMM detection
    - drm/panfrost: Fix missing clk_disable_unprepare() on error in
      panfrost_clk_init()
    - drm/gma500: Fix end of loop tests for list_for_each_entry
    - ASoC: mediatek: mt8192:Fix Unbalanced pm_runtime_enable in
      mt8192_afe_pcm_dev_probe
    - ASoC: mediatek: mt8183: Fix Unbalanced pm_runtime_enable in
      mt8183_afe_pcm_dev_probe
    - media: TDA1997x: enable EDID support
    - leds: is31fl32xx: Fix missing error code in is31fl32xx_parse_dt()
    - soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally
    - media: cxd2880-spi: Fix an error handling path
    - drm/of: free the right object
    - bpf: Fix a typo of reuseport map in bpf.h.
    - bpf: Fix potential memleak and UAF in the verifier.
    - drm/of: free the iterator object on failure
    - gve: fix the wrong AdminQ buffer overflow check
    - libbpf: Fix the possible memory leak on error
    - ARM: dts: aspeed-g6: Fix HVI3C function-group in pinctrl dtsi
    - arm64: dts: renesas: r8a77995: draak: Remove bogus adv7511w properties
    - i40e: improve locking of mac_filter_hash
    - arm64: dts: qcom: sc7180: Set adau wakeup delay to 80 ms
    - soc: qcom: rpmhpd: Use corner in power_off
    - libbpf: Fix removal of inner map in bpf_object__create_map
    - gfs2: Fix memory leak of object lsi on error return path
    - arm64: dts: qcom: sm8250: fix usb2 qmp phy node
    - bpf, selftests: Fix test_maps now that sockmap supports UDP
    - firmware: fix theoretical UAF race with firmware cache and resume
    - driver core: Fix error return code in really_probe()
    - ionic: cleanly release devlink instance
    - media: dvb-usb: fix uninit-value in dvb_usb_adapter_dvb_init
    - media: dvb-usb: fix uninit-value in vp702x_read_mac_addr
    - media: dvb-usb: Fix error handling in dvb_usb_i2c_init
    - media: go7007: fix memory leak in go7007_usb_probe
    - media: go7007: remove redundant initialization
    - media: rockchip/rga: use pm_runtime_resume_and_get()
    - media: rockchip/rga: fix error handling in probe
    - media: coda: fix frame_mem_ctrl for YUV420 and YVU420 formats
    - media: atomisp: fix the uninitialized use and rename "retvalue"
    - Bluetooth: sco: prevent information leak in sco_conn_defer_accept()
    - Bluetooth: btusb: Fix a unspported condition to set available debug features
    - 6lowpan: iphc: Fix an off-by-one check of array index
    - tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos
    - ARM: dts: meson8: Use a higher default GPU clock frequency
    - ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties
    - ARM: dts: meson8b: mxq: Fix the pwm regulator supply properties
    - ARM: dts: meson8b: ec100: Fix the pwm regulator supply properties
    - net/mlx5e: Prohibit inner indir TIRs in IPoIB
    - net/mlx5e: Block LRO if firmware asks for tunneled LRO
    - cgroup/cpuset: Fix a partition bug with hotplug
    - drm: mxsfb: Enable recovery on underflow
    - drm: mxsfb: Increase number of outstanding requests on V4 and newer HW
    - drm: mxsfb: Clear FIFO_CLEAR bit
    - net: cipso: fix warnings in netlbl_cipsov4_add_std
    - net: ti: am65-cpsw-nuss: fix wrong devlink release order
    - drm: rcar-du: Don't put reference to drm_device in rcar_du_remove()
    - Bluetooth: mgmt: Fix wrong opcode in the response for add_adv cmd
    - tools: Free BTF objects at various locations
    - arm64: dts: renesas: hihope-rzg2-ex: Add EtherAVB internal rx delay
    - devlink: Break parameter notification sequence to be before/after
      unload/load driver
    - net/mlx5: Fix missing return value in mlx5_devlink_eswitch_inline_mode_set()
    - i2c: highlander: add IRQ check
    - leds: lgm-sso: Put fwnode in any case during ->probe()
    - leds: lgm-sso: Don't spam logs when probe is deferred
    - leds: lt3593: Put fwnode in any case during ->probe()
    - leds: rt8515: Put fwnode in any case during ->probe()
    - leds: trigger: audio: Add an activate callback to ensure the initial
      brightness is set
    - media: em28xx-input: fix refcount bug in em28xx_usb_disconnect
    - media: omap3isp: Fix missing unlock in isp_subdev_notifier_complete()
    - media: venus: hfi: fix return value check in sys_get_prop_image_version()
    - media: venus: venc: Fix potential null pointer dereference on pointer fmt
    - media: venus: helper: do not set constrained parameters for UBWC
    - soc: mmsys: mediatek: add mask to mmsys routes
    - PCI: PM: Avoid forcing PCI_D0 for wakeup reasons inconsistently
    - PCI: PM: Enable PME if it can be signaled from D3cold
    - bpf, samples: Add missing mprog-disable to xdp_redirect_cpu's optstring
    - soc: qcom: smsm: Fix missed interrupts if state changes while masked
    - debugfs: Return error during {full/open}_proxy_open() on rmmod
    - Bluetooth: increase BTNAMSIZ to 21 chars to fix potential buffer overflow
    - net: ti: am65-cpsw-nuss: fix RX IRQ state after .ndo_stop()
    - net: dsa: stop syncing the bridge mcast_router attribute at join time
    - net: dsa: mt7530: remove the .port_set_mrouter implementation
    - net: dsa: don't disable multicast flooding to the CPU even without an IGMP
      querier
    - PM: EM: Increase energy calculation precision
    - selftests/bpf: Fix bpf-iter-tcp4 test to print correctly the dest IP
    - leds: lgm-sso: Propagate error codes from callee to caller
    - drm/msm/mdp4: refactor HW revision detection into read_mdp_hw_revision
    - drm/msm/mdp4: move HW revision detection to earlier phase
    - drm/msm/dp: update is_connected status base on sink count at dp_pm_resume()
    - drm/msm/dpu: make dpu_hw_ctl_clear_all_blendstages clear necessary LMs
    - arm64: dts: exynos: correct GIC CPU interfaces address range on Exynos7
    - counter: 104-quad-8: Return error when invalid mode during ceiling_write
    - cgroup/cpuset: Miscellaneous code cleanup
    - cgroup/cpuset: Fix violation of cpuset locking rule
    - ASoC: Intel: Fix platform ID matching
    - Bluetooth: fix repeated calls to sco_sock_kill
    - drm/msm/dsi: Fix some reference counted resource leaks
    - drm/msm/dp: replug event is converted into an unplug followed by an plug
      events
    - net/mlx5: Fix unpublish devlink parameters
    - ASoC: rt5682: Implement remove callback
    - ASoC: rt5682: Properly turn off regulators if wrong device ID
    - usb: dwc3: meson-g12a: add IRQ check
    - usb: dwc3: qcom: add IRQ check
    - usb: gadget: udc: at91: add IRQ check
    - usb: gadget: udc: s3c2410: add IRQ check
    - usb: misc: brcmstb-usb-pinmap: add IRQ check
    - usb: phy: fsl-usb: add IRQ check
    - usb: phy: twl6030: add IRQ checks
    - usb: gadget: udc: renesas_usb3: Fix soc_device_match() abuse
    - selftests/bpf: Fix test_core_autosize on big-endian machines
    - devlink: Clear whole devlink_flash_notify struct
    - samples: pktgen: add missing IPv6 option to pktgen scripts
    - net: stmmac: fix INTR TBU status affecting irq count statistic
    - PM: cpu: Make notifier chain use a raw_spinlock_t
    - usb: host: ohci-tmio: add IRQ check
    - usb: phy: tahvo: add IRQ check
    - libbpf: Re-build libbpf.so when libbpf.map changes
    - mac80211: Fix insufficient headroom issue for AMSDU
    - locking/local_lock: Add missing owner initialization
    - lockd: Fix invalid lockowner cast after vfs_test_lock
    - SUNRPC: Fix a NULL pointer deref in trace_svc_stats_latency()
    - nfsd4: Fix forced-expiry locking
    - arm64: dts: marvell: armada-37xx: Extend PCIe MEM space
    - clk: staging: correct reference to config IOMEM to config HAS_IOMEM
    - [Config] updateconfigs for COMMON_CLK_XLNX_CLKWZRD
    - i2c: synquacer: fix deferred probing
    - hwmon: (pmbus/bpa-rs600) Don't use rated limits as warn limits
    - hwmon: remove amd_energy driver in Makefile
    - ASoC: fsl_rpmsg: Check -EPROBE_DEFER for getting clocks
    - firmware: raspberrypi: Fix a leak in 'rpi_firmware_get()'
    - usb: gadget: mv_u3d: request_irq() after initializing UDC
    - mm/swap: consider max pages in iomap_swapfile_add_extent
    - lkdtm: replace SCSI_DISPATCH_CMD with SCSI_QUEUE_RQ
    - Bluetooth: add timeout sanity check to hci_inquiry
    - i2c: iop3xx: fix deferred probing
    - i2c: s3c2410: fix IRQ check
    - i2c: hix5hd2: fix IRQ check
    - gfs2: init system threads before freeze lock
    - rsi: fix error code in rsi_load_9116_firmware()
    - rsi: fix an error code in rsi_probe()
    - octeontx2-af: cn10k: Fix SDP base channel number
    - octeontx2-pf: send correct vlan priority mask to npc_install_flow_req
    - octeontx2-pf: Don't install VLAN offload rule if netdev is down
    - octeontx2-pf: Fix algorithm index in MCAM rules with RSS action
    - m68k: coldfire: return success for clk_enable(NULL)
    - ASoC: Intel: kbl_da7219_max98927: Fix format selection for max98373
    - ASoC: Intel: Skylake: Leave data as is when invoking TLV IPCs
    - ASoC: Intel: Skylake: Fix module resource and format selection
    - mmc: sdhci: Fix issue with uninitialized dma_slave_config
    - mmc: dw_mmc: Fix issue with uninitialized dma_slave_config
    - mmc: moxart: Fix issue with uninitialized dma_slave_config
    - bpf: Fix possible out of bound write in narrow load handling
    - CIFS: Fix a potencially linear read overflow
    - i2c: mt65xx: fix IRQ check
    - i2c: xlp9xx: fix main IRQ check
    - octeontx2-pf: cn10k: Fix error return code in otx2_set_flowkey_cfg()
    - usb: ehci-orion: Handle errors of clk_prepare_enable() in probe
    - usb: bdc: Fix an error handling path in 'bdc_probe()' when no suitable DMA
      config is available
    - usb: bdc: Fix a resource leak in the error handling path of 'bdc_probe()'
    - tty: serial: fsl_lpuart: fix the wrong mapbase value
    - ASoC: wcd9335: Fix a double irq free in the remove function
    - ASoC: wcd9335: Fix a memory leak in the error handling path of the probe
      function
    - ASoC: wcd9335: Disable irq on slave ports in the remove function
    - iwlwifi: skip first element in the WTAS ACPI table
    - net/mlx5: Remove all auxiliary devices at the unregister event
    - net/mlx5e: Fix possible use-after-free deleting fdb rule
    - net/mlx5: E-Switch, Set vhca id valid flag when creating indir fwd group
    - net/mlx5e: Use correct eswitch for stack devices with lag
    - ice: Only lock to update netdev dev_addr
    - net: phy: marvell10g: fix broken PHY interrupts for anyone after us in the
      driver probe list
    - ath6kl: wmi: fix an error code in ath6kl_wmi_sync_point()
    - atlantic: Fix driver resume flow.
    - bcma: Fix memory leak for internally-handled cores
    - brcmfmac: pcie: fix oops on failure to resume and reprobe
    - ipv6: make exception cache less predictible
    - ipv4: make exception cache less predictible
    - net: qrtr: make checks in qrtr_endpoint_post() stricter
    - sch_htb: Fix inconsistency when leaf qdisc creation fails
    - net: sched: Fix qdisc_rate_table refcount leak when get tcf_block failed
    - net: qualcomm: fix QCA7000 checksum handling
    - octeontx2-af: Fix loop in free and unmap counter
    - octeontx2-af: Fix mailbox errors in nix_rss_flowkey_cfg
    - octeontx2-af: Fix static code analyzer reported issues
    - octeontx2-af: Set proper errorcode for IPv4 checksum errors
    - ipv4: fix endianness issue in inet_rtm_getroute_build_skb()
    - amdgpu/pm: add extra info to SMU msg pre-check failed message
    - ASoC: rt5682: Remove unused variable in rt5682_i2c_remove()
    - iwlwifi Add support for ax201 in Samsung Galaxy Book Flex2 Alpha
    - f2fs: guarantee to write dirty data when enabling checkpoint back
    - auxdisplay: hd44780: Fix oops on module unloading
    - io_uring: limit fixed table size by RLIMIT_NOFILE
    - io_uring: IORING_OP_WRITE needs hash_reg_file set
    - io_uring: io_uring_complete() trace should take an integer
    - bio: fix page leak bio_add_hw_page failure
    - raid1: ensure write behind bio has less than BIO_MAX_VECS sectors
    - cifs: Do not leak EDEADLK to dgetents64 for STATUS_USER_SESSION_DELETED
    - smb3: fix posix extensions mount option
    - tty: Fix data race between tiocsti() and flush_to_ldisc()
    - x86/efi: Restore Firmware IDT before calling ExitBootServices()
    - perf/x86/amd/ibs: Extend PERF_PMU_CAP_NO_EXCLUDE to IBS Op
    - x86/resctrl: Fix a maybe-uninitialized build warning treated as error
    - Revert "KVM: x86: mmu: Add guest physical address check in translate_gpa()"
    - KVM: s390: index kvm->arch.idle_mask by vcpu_idx
    - KVM: x86: Update vCPU's hv_clock before back to guest when tsc_offset is
      adjusted
    - KVM: x86: clamp host mapping level to max_level in kvm_mmu_max_mapping_level
    - KVM: x86/mmu: Avoid collision with !PRESENT SPTEs in TDP MMU lpage stats
    - KVM: VMX: avoid running vmx_handle_exit_irqoff in case of emulation
    - KVM: nVMX: Unconditionally clear nested.pi_pending on nested VM-Enter
    - KVM: arm64: Unregister HYP sections from kmemleak in protected mode
    - ARM: dts: at91: add pinctrl-{names, 0} for all gpios
    - io-wq: check max_worker limits if a worker transitions bound state
    - md/raid10: Remove unnecessary rcu_dereference in raid10_handle_discard
    - char: tpm: Kconfig: remove bad i2c cr50 select
    - fuse: truncate pagecache on atomic_o_trunc
    - fuse: flush extending writes
    - fuse: wait for writepages in syncfs
    - IMA: remove -Wmissing-prototypes warning
    - IMA: remove the dependency on CRYPTO_MD5
    - fbmem: don't allow too huge resolutions
    - RDMA/mlx5: Fix number of allocated XLT entries
    - backlight: pwm_bl: Improve bootloader/kernel device handover
    - clk: kirkwood: Fix a clocking boot regression
    - Linux 5.13.17
  * AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
    (LP: #1920674) // Impish update: v5.13.17 upstream stable release
    (LP: #1946247)
    - drm/amdgpu/acp: Make PM domain really work
  * Impish update: v5.13.16 upstream stable release (LP: #1946245)
    - firmware: dmi: Move product_sku info to the end of the modalias
    - igmp: Add ip_mc_list lock in ip_check_mc_rcu
    - net: ll_temac: Remove left-over debug message
    - Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables
      ASPM"
    - blk-mq: fix kernel panic during iterating over flush request
    - blk-mq: fix is_flush_rq
    - blk-mq: clearing flush request reference in tags->rqs[]
    - ALSA: usb-audio: Add registration quirk for JBL Quantum 800
    - Bluetooth: Add additional Bluetooth part for Realtek 8852AE
    - Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more
      generic
    - usb: host: xhci-rcar: Don't reload firmware after the completion
    - usb: xhci-mtk: fix issue of out-of-bounds array access
    - usb: cdnsp: fix the wrong mult value for HS isoc or intr
    - usb: gadget: tegra-xudc: fix the wrong mult value for HS isoc or intr
    - usb: mtu3: restore HS function when set SS/SSP
    - usb: mtu3: use @mult for HS isoc or intr
    - usb: mtu3: fix the wrong HS mult value
    - xhci: fix even more unsafe memory usage in xhci tracing
    - xhci: fix unsafe memory usage in xhci tracing
    - xhci: Fix failure to give back some cached cancelled URBs.
    - x86/reboot: Limit Dell Optiplex 990 quirk to early BIOS versions
    - PCI: Call Max Payload Size-related fixup quirks early
    - Linux 5.13.16
  * Impish update: v5.13.15 upstream stable release (LP: #1946242)
    - ext4: fix e2fsprogs checksum failure for mounted filesystem
    - gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V
      formats
    - reset: reset-zynqmp: Fixed the argument data type
    - qed: Fix the VF msix vectors flow
    - net: dsa: mv88e6xxx: Update mv88e6393x serdes errata
    - riscv: dts: microchip: Use 'local-mac-address' for emac1
    - riscv: dts: microchip: Add ethernet0 to the aliases node
    - net: macb: Add a NULL check on desc_ptp
    - qede: Fix memset corruption
    - perf/x86/intel/pt: Fix mask of num_address_ranges
    - ceph: fix possible null-pointer dereference in ceph_mdsmap_decode()
    - perf/x86/amd/ibs: Work around erratum #1197
    - perf/x86/amd/power: Assign pmu.module
    - cryptoloop: add a deprecation warning
    - xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG
    - USB: serial: pl2303: fix GL type detection
    - USB: serial: cp210x: fix control-characters error handling
    - USB: serial: cp210x: fix flow-control error handling
    - ALSA: hda/realtek: Quirk for HP Spectre x360 14 amp setup
    - ALSA: usb-audio: Fix regression on Sony WALKMAN NW-A45 DAC
    - ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17
    - ALSA: pcm: fix divide error in snd_pcm_lib_ioctl
    - media: stkwebcam: fix memory leak in stk_camera_probe
    - Linux 5.13.15
  * Re-enable DEBUG_INFO_BTF where it was dissabled (LP: #1945632)
    - [Config] Re-enable CONFIG_DEBUG_INFO_BTF=y on armhf
  * Fix missing HDMI audio on Intel RKL (LP: #1945556)
    - drm/i915/audio: Use BIOS provided value for RKL HDA link
  * USB Type-C hotplug event not handled properly in TGL-H system during s2idle
    (LP: #1931072)
    - drm/i915: Force a TypeC PHY disconnect during suspend/shutdown
  * Packaging resync (LP: #1786013)
    - [Packaging] update Ubuntu.md

[ Ubuntu: 5.13.0-20.20 ]

* impish/linux: 5.13.0-20.20 -proposed tracker (LP: #1947380)
  * PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
    sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl))
    failed (LP: #1906476)
    - debian/dkms-versions -- Update zfs to latest version

[ Ubuntu: 5.13.0-19.19 ]

* impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337)
  * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001)
    - [Config] disable KFENCE

[ Ubuntu: 5.13.0-18.18 ]

* impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995)
  * [21.10 FEAT] KVM: Use interpretation of specification exceptions
    (LP: #1932157)
    - KVM: s390: Enable specification exception interpretation

-- Juerg Haefliger <juergh@canonical.com>  Tue, 09 Nov 2021 11:16:34 +0100

Changed in linux-raspi (Ubuntu Impish):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2022-02-02:

#76

Download full text (44.5 KiB)

This bug was fixed in the package linux-raspi - 5.15.0-1002.2

---------------
linux-raspi (5.15.0-1002.2) jammy; urgency=medium

* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)

  * Packaging resync (LP: #1786013)
    - [Packaging] update Ubuntu.md
    - debian/dkms-versions -- update from kernel-versions (main/master)

  * Kernel fails to boot in ScalingStack (LP: #1959102)
    - [Config] raspi: Set VIRTIO_PCI=m
    - [Config] raspi: Set ACPI=y

  * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
    (LP: #1958854)
    - brcmfmac: firmware: Fix crash in brcm_alt_fw_path
    - ARM: dts: Remove VL805 USB node from CM4 dts
    - mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
    - pwm: raspberrypi-poe: Add option of being created by MFD or FW
    - power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
    - power: rpi-poe: Add option of being created by MFD or FW
    - defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
    - dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
    - drivers: bcm2835_unicam: Disable trigger mode operation
    - arm: Remove spurious .fnend directive
    - drm/vc4: Fix deadlock on DSI device attach error
    - drm/vc4: dsi: Correct max divider to 255 (not 7)
    - defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
    - dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
    - dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
    - ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
    - update rpi-display-overlay.dts pins for 5.10+

[ Ubuntu: 5.15.0-18.18 ]

  * jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
  * CVE-2021-4155
    - xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
  * CVE-2022-0185
    - SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
  * [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
    kernel part (LP: #1953334)
    - KVM: s390: add debug statement for diag 318 CPNC data
  * OOB write on BPF_RINGBUF (LP: #1956585)
    - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
      than 0
  * Miscellaneous Ubuntu changes
    - [Config] re-enable shiftfs
    - [SAUCE] shiftfs: support kernel 5.15
    - [Config] update toolchain versions
  * Miscellaneous upstream changes
    - vfs: fs_context: fix up param length parsing in legacy_parse_param

linux-raspi (5.15.0-1001.1) jammy; urgency=medium

* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README

* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5

  * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
    (LP: #1958146)
    - clk: bcm-2835: Pick the closest clock rate
    - clk: bcm-2835: Remove rounding up the dividers
    - drm/vc4: hdmi: Set a default HSM rate
    - drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
    - drm/vc4: hdmi: Make sure the controller is powered in detect
    - drm/vc4: hdmi: Make sure the controller is powered up during bind
    - drm/vc4: hdmi: Rework the ...

This bug was fixed in the package linux-raspi - 5.15.0-1002.2

---------------
linux-raspi (5.15.0-1002.2) jammy; urgency=medium

* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)

* Packaging resync (LP: #1786013)
    - [Packaging] update Ubuntu.md
    - debian/dkms-versions -- update from kernel-versions (main/master)

* Kernel fails to boot in ScalingStack (LP: #1959102)
    - [Config] raspi: Set VIRTIO_PCI=m
    - [Config] raspi: Set ACPI=y

* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
    (LP: #1958854)
    - brcmfmac: firmware: Fix crash in brcm_alt_fw_path
    - ARM: dts: Remove VL805 USB node from CM4 dts
    - mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
    - pwm: raspberrypi-poe: Add option of being created by MFD or FW
    - power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
    - power: rpi-poe: Add option of being created by MFD or FW
    - defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
    - dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
    - drivers: bcm2835_unicam: Disable trigger mode operation
    - arm: Remove spurious .fnend directive
    - drm/vc4: Fix deadlock on DSI device attach error
    - drm/vc4: dsi: Correct max divider to 255 (not 7)
    - defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
    - dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
    - dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
    - ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
    - update rpi-display-overlay.dts pins for 5.10+

[ Ubuntu: 5.15.0-18.18 ]

* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
  * CVE-2021-4155
    - xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
  * CVE-2022-0185
    - SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
  * [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
    kernel part (LP: #1953334)
    - KVM: s390: add debug statement for diag 318 CPNC data
  * OOB write on BPF_RINGBUF (LP: #1956585)
    - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
      than 0
  * Miscellaneous Ubuntu changes
    - [Config] re-enable shiftfs
    - [SAUCE] shiftfs: support kernel 5.15
    - [Config] update toolchain versions
  * Miscellaneous upstream changes
    - vfs: fs_context: fix up param length parsing in legacy_parse_param

linux-raspi (5.15.0-1001.1) jammy; urgency=medium

* Missing overlays/README (LP: #1954757)
    - SAUCE: Install overlays/README

* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
    - SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5

* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
    (LP: #1958146)
    - clk: bcm-2835: Pick the closest clock rate
    - clk: bcm-2835: Remove rounding up the dividers
    - drm/vc4: hdmi: Set a default HSM rate
    - drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
    - drm/vc4: hdmi: Make sure the controller is powered in detect
    - drm/vc4: hdmi: Make sure the controller is powered up during bind
    - drm/vc4: hdmi: Rework the pre_crtc_configure error handling
    - drm/vc4: hdmi: Split the CEC disable / enable functions in two
    - drm/vc4: hdmi: Make sure the device is powered with CEC
    - drm/vc4: hdmi: Warn if we access the controller while disabled
    - drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
    - drm/vc4: crtc: Drop feed_txp from state
    - drm/vc4: Fix non-blocking commit getting stuck forever
    - drm/vc4: crtc: Copy assigned channel to the CRTC
    - drm/vc4: hdmi: Add a spinlock to protect register access
    - drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
    - drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
    - drm/vc4: hdmi: Check the device state in prepare()
    - drm/vc4: hdmi: Introduce an output_enabled flag
    - drm/vc4: hdmi: Introduce a scdc_enabled flag
    - drm/vc4: hdmi: Remove the DDC probing for status detection
    - drm/vc4: hdmi: Fix HPD GPIO detection
    - drm/vc4: Make vc4_crtc_get_encoder public
    - drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
    - drm/vc4: crtc: Rework the encoder retrieval code (again)
    - drm/vc4: crtc: Add some logging
    - drm/vc4: Leverage the load tracker on the BCM2711
    - drm/vc4: hdmi: Raise the maximum clock rate
    - drm/vc4: hdmi: Enable the scrambler on reconnection
    - drm/vc4: Increase the core clock based on HVS load
    - drm/vc4: select PM
    - drm/probe-helper: Create a HPD IRQ event helper for a single connector
    - drm/vc4: hdmi: Actually check for the connector status in hotplug
    - firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
    - drm/vc4: Remove conflicting framebuffers before callind bind_all
    - drm/vc4: Notify the firmware when DRM is in charge
    - arm: partially revert 702b94bff3c50542a6e4ab9a4f4cef093262fe65
    - Revert "rtc: pcf8523: properly handle oscillator stop bit"
    - Revert "staging: bcm2835-audio: Drop DT dependency"
    - Revert "spi: spidev: Fix CS polarity if GPIO descriptors are used"
    - Revert "mailbox: avoid timer start from callback"
    - Revert "Bluetooth: Always request for user confirmation for Just Works (LE
      SC)"
    - Revert "Bluetooth: Always request for user confirmation for Just Works"
    - smsx95xx: fix crimes against truesize
    - smsc95xx: Experimental: Enable turbo_mode and packetsize=2560 by default
    - Allow mac address to be set in smsc95xx
    - cgroup: Disable cgroup "memory" by default
    - Protect __release_resource against resources without parents
    - irq-bcm2836: Avoid "Invalid trigger warning"
    - irqchip: bcm2835: Add FIQ support
    - irqchip: irq-bcm2835: Add 2836 FIQ support
    - spi: spidev: Completely disable the spidev warning
    - dmaengine: bcm2835: Load driver early and support legacy API
    - rtc: Add SPI alias for pcf2123 driver
    - watchdog: bcm2835: Support setting reboot partition
    - reboot: Use power off rather than busy spinning when halt is requested
    - bcm: Make RASPBERRYPI_POWER depend on PM
    - Register the clocks early during the boot process, so that special/critical
      clocks can get enabled early on in the boot process avoiding the risk of
      disabling a clock, pll_divider or pll when a claiming driver fails to
      install propperly - maybe it needs to defer.
    - bcm2835-rng: Avoid initialising if already enabled
    - clk-bcm2835: Mark used PLLs and dividers CRITICAL
    - clk-bcm2835: Add claim-clocks property
    - clk-bcm2835: Read max core clock from firmware
    - sound: Demote deferral errors to INFO level
    - Update vfpmodule.c
    - i2c: bcm2835: Add debug support
    - irqchip: irq-bcm2836: Remove regmap and syscon use
    - lan78xx: Enable LEDs and auto-negotiation
    - amba_pl011: Don't use DT aliases for numbering
    - amba_pl011: Round input clock up
    - amba_pl011: Insert mb() for correct FIFO handling
    - amba_pl011: Add cts-event-workaround DT property
    - tty: amba-pl011: Add un/throttle support
    - tty: amba-pl011: Avoid rare write-when-full error
    - pinctrl-bcm2835: Set base to 0 give expected gpio numbering
    - Main bcm2708/bcm2709 linux port
    - Add dwc_otg driver
    - bcm2708 framebuffer driver
    - Pulled in the multi frame buffer support from the Pi3 repo
    - fbdev: add FBIOCOPYAREA ioctl
    - Speed up console framebuffer imageblit function
    - dmaengine: Add support for BCM2708
    - MMC: added alternative MMC driver
    - Adding bcm2835-sdhost driver, and an overlay to enable it
    - vc_mem: Add vc_mem driver for querying firmware memory addresses
    - Add /dev/gpiomem device for rootless user GPIO access
    - Add SMI driver
    - Add Chris Boot's i2c driver
    - char: broadcom: Add vcio module
    - firmware: bcm2835: Support ARCH_BCM270x
    - BCM2708: Add core Device Tree support
    - leds: Add the "input" trigger, for pwr_led
    - Added Device IDs for August DVB-T 205
    - Improve __copy_to_user and __copy_from_user performance
    - gpio-poweroff: Allow it to work on Raspberry Pi
    - mfd: Add Raspberry Pi Sense HAT core driver
    - Add support for all the downstream rpi sound card drivers
    - rpi_display: add backlight driver and overlay
    - bcm2835-virtgpio: Virtual GPIO driver
    - OF: DT-Overlay configfs interface
    - brcm: adds support for BCM43341 wifi
    - hci_h5: Don't send conf_req when ACTIVE
    - config: Add default configs
    - ARM64: Round-Robin dispatch IRQs between CPUs.
    - ARM64: Force hardware emulation of deprecated instructions.
    - cache: export clean and invalidate
    - AXI performance monitor driver (#2222)
    - ARM: bcm2835: Set Serial number and Revision
    - dwc-otg: FIQ: Fix "bad mode in data abort handler"
    - ARM: Activate FIQs to avoid __irq_startup warnings
    - i2c-gpio: Also set bus numbers from reg property
    - added capture_clear option to pps-gpio via dtoverlay (#2433)
    - lan78xx: Read initial EEE status from DT
    - hid: Reduce default mouse polling interval to 60Hz
    - Add ability to export gpio used by gpio-poweroff
    - firmware/raspberrypi: Notify firmware of a reboot
    - irqchip: irq-bcm2835: Calc. FIQ_START at boot-time
    - of: configfs: Use of_overlay_fdt_apply API call
    - net: lan78xx: Disable TCP Segmentation Offload (TSO)
    - brcmfmac: Re-enable firmware roaming support
    - lan78xx: Move enabling of EEE into PHY init code
    - cxd2880: CXD2880_SPI_DRV should select DVB_CXD2880 with
      MEDIA_SUBDRV_AUTOSELECT
    - firmware: raspberrypi: Add backward compatible get_throttled
    - sc16is7xx: Don't spin if no data received
    - drivers: thermal: step_wise: add support for hysteresis
    - drivers: thermal: step_wise: avoid throttling at hysteresis temperature
      after dropping below it
    - Update issue templates (#2736)
    - net: lan78xx: Support auto-downshift to 100Mb/s
    - firmware: raspberrypi: Report the fw variant during probe
    - lan78xx: Debounce link events to minimize poll storm
    - lan78xx: EEE support is now a PHY property
    - bcm2835-dma: Add support for per-channel flags
    - rtc: rv3028: Add backup switchover mode support
    - lan78xx: use default alignment for rx buffers
    - media: tc358743: Increase FIFO level to 374.
    - media: tc358743: fix connected/active CSI-2 lane reporting
    - media: tc358743: Add support for 972Mbit/s link freq.
    - media: tc358743: Check I2C succeeded during probe.
    - media: adv7180: Default to the first valid input
    - media: adv7180: Add YPrPb support for ADV7282M
    - media: videodev2: Add helper defines for printing FOURCCs
    - dt-bindings: Document BCM283x CSI2/CCP2 receiver
    - MAINTAINERS: Add entry for BCM2835 Unicam driver
    - media: tc358743: Return an appropriate colorspace from tc358743_set_fmt
    - staging: mmal-vchiq: Avoid use of bool in structures
    - staging: mmal-vchiq: Add support for event callbacks.
    - staging: vc04_services: Support sending data to MMAL ports
    - media: videobuf2: Allow exporting of a struct dmabuf
    - staging: mmal-vchiq: Fix client_component for 64 bit kernel
    - clk: clk-bcm2835: Use %zd when printing size_t
    - staging: mmal_vchiq: Add in the Bayer encoding formats
    - staging: mmal-vchiq: Update mmal_parameters.h with recently defined params
    - staging: mmal-vchiq: Free the event context for control ports
    - staging: mmal-vchiq: Fix memory leak in error path
    - w1: w1-gpio: Make GPIO an output for strong pullup
    - arm: bcm2835: Fix FIQ early ioremap
    - arm: bcm2835: DMA can only address 1GB
    - hwrng: iproc-rng200: Add BCM2838 support
    - bcmgenet: constrain max DMA burst length
    - bcmgenet: Better coalescing parameter defaults
    - net: genet: enable link energy detect powerdown for external PHYs
    - spi: bcm2835: enable shared interrupt support
    - clk-bcm2835: Don't wait for pllh lock
    - soc: bcm: bcm2835-pm: Add support for 2711.
    - clk: bcm2835: Add support for setting leaf clock rates while running.
    - clk: bcm2835: Allow reparenting leaf clocks while they're running.
    - usb: add plumbing for updating interrupt endpoint interval state
    - xhci: implement xhci_fixup_endpoint for interval adjustments
    - usbhid: call usb_fixup_endpoint after mangling intervals
    - arm: bcm2835: Add bcm2838 compatible string.
    - drm/v3d: Add support for 2711.
    - drm/v3d: Skip MMU flush if the device is currently off.
    - drm/v3d: Hook up the runtime PM ops.
    - i2c: bcm2835: Set clock-stretch timeout to 35ms
    - clk-bcm2835: Avoid null pointer exception
    - drm/v3d: HACK: gut runtime pm for now.
    - drm/v3d: Clock V3D down when not in use.
    - drivers: char: add chardev for mmap'ing the RPiVid control registers
    - hid: usb: Add device quirks for Freeway Airmouse T3 and MX3
    - Add HDMI1 facility to the driver.
    - net: bcmgenet: Workaround #2 for Pi4 Ethernet fail
    - xhci: Use more event ring segment table entries
    - configs: arm64/bcm2711: Enable V3D
    - arch/arm: Add model string to cpuinfo
    - arch/arm64: Add Revision, Serial, Model to cpuinfo
    - media: dt-bindings: Add binding for the Sony IMX219 sensor
    - v4l2: Add a Greyworld AWB mode.
    - staging: bcm2835-camera: Add greyworld AWB mode
    - drm/v3d: Delete pm_runtime support
    - ARM: bcm: Switch board, clk and pinctrl to bcm2711 compatible
    - Rename HDMI ALSA device names, check for enable state
    - dt-bindings: Add binding for the Infineon IRS1125 sensor
    - media: i2c: Add a driver for the Infineon IRS1125 depth sensor
    - drm/v3d: Suppress all but the first MMU error
    - drm/v3d: Plug dma_fence leak
    - staging: vchiq_arm: Register vcsm-cma as a platform driver
    - staging: vchiq_arm: Register bcm2835-codec as a platform driver
    - net:phy:2711 Allow ethernet LED mode to be set via device tree
    - v3d_drv: Handle missing clock more gracefully
    - v3d_gem: Kick the clock so firmware knows we are using firmware clock
      interface
    - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks
    - clk-bcm2835: Disable v3d clock
    - staging: vchiq_arm: Set up dma ranges on child devices
    - staging: vchiq: Use the old dma controller for OF config on platform devices
    - ARM: bcm: Backport BCM2711 support from upstream
    - Initialise rpi-firmware before clk-bcm2835
    - staging: vchiq_arm: Give vchiq children DT nodes
    - pinctrl: bcm2835: Remove gpiochip on error
    - drivers: char: vcio: Use common compat header
    - video: fbdev: bcm2708_fb: Use common compat header
    - of: overlay: Correct symbol path fixups
    - dt-bindings: pci: Add DT docs for Brcmstb PCIe device
    - bcmgenet: Disable skip_umac_reset by default
    - drm/fourcc: Add packed 10bit YUV 4:2:0 format
    - media: uapi: hevc: Add scaling matrix control
    - media: uapi: hevc: Add segment address field
    - media: videodev2.h: Add a format for column YUV4:2:0 modes
    - media: dt-bindings: media: Add binding for the Raspberry PI HEVC decoder
    - staging: media: Add Raspberry Pi V4L2 H265 decoder
    - dt-bindings: clock: Add a binding for the RPi Firmware clocks
    - dt-bindings: display: vc4: hdmi: Add BCM2711 HDMI controllers bindings
    - drm: Checking of the pitch is only valid for linear formats
    - driver: char: rpivid: Remove legacy name support
    - spi: Force CS_HIGH if GPIO descriptors are used
    - driver: char: rpivid: Don't map more than wanted
    - media: bcm2835-unicam: Driver for CCP2/CSI2 camera interface
    - media: uapi: v4l2-core: Add sensor ancillary data V4L2 foucc type.
    - media: uapi: Add MEDIA_BUS_FMT_SENSOR_DATA media bus format
    - media: bcm2835-unicam: Add support for mulitple device nodes.
    - media: bcm2835-unicam: Add embedded data node.
    - media: bcm2835-unicam: Use dummy buffer if none have been queued
    - media: bcm2835-unicam: Disable event-related ioctls on metadata node
    - media: bcm2835-unicam: Add support for the FRAME_SYNC event
    - media: bcm2835-unicam: Re-fetch mbus code from subdev on a g_fmt call
    - media: uapi: v4l2-core: Add ISP statistics output V4L2 fourcc type
    - media: uapi: v4l-ctrls: Add CID base for the bcm2835-isp driver
    - staging: vchiq: Load bcm2835_isp driver from vchiq
    - bcm2835-dma: Add proper 40-bit DMA support
    - media: bcm2835-unicam: Add support for VIDIOC_[S|G]_SELECTION
    - media: bcm2835-unicam: Do not stop streaming in unicam_release
    - media: bcm2835-unicam: Fix reference counting in unicam_open
    - media: i2c: tc358743: Fix fallthrough warning
    - media: bcm2835: unicam: Fix uninitialized warning
    - video: bcm2708_fb: Disable FB if no displays found
    - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding
    - media: bcm2835-unicam: Always service interrupts
    - sc16is7xx: Fix for hardware flow control
    - staging: vc04_services: mmal-vchiq: Update parameters list
    - staging:vc04_services: bcm2835-camera: Request headers with I-frame
    - media: bcm2835-unicam: Retain packing information on G_FMT
    - zswap: Defer zswap initialisation
    - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1
    - snd_bcm2835: disable HDMI audio when vc4 is used (#3640)
    - gpiolib: Don't prevent IRQ usage of output GPIOs
    - PCI: brcmstb: Add DT property to control L1SS
    - media: irs1125: Using i2c_transfer for ic2 reads
    - media: irs1125: Refactoring and debug messages
    - media: irs1125: Atomic access to imager reconfiguration
    - media: irs1125: Keep HW in sync after imager reset
    - staging: bcm2835-audio: Add missing MODULE_ALIAS
    - brcmfmac: Prefer a ccode from OTP over nvram file
    - drivers: media: Remove the downstream version of bcm2835-unicam
    - media: bcm2835-unicam: Driver for CCP2/CSI2 camera interface
    - media: bcm2835-unicam: Add support for get_mbus_config to set num lanes
    - media: bcm2835-unicam: Avoid gcc warning over {0} on endpoint
    - media: i2c: imx290: set the format before VIDIOC_SUBDEV_G_FMT is called
    - media: i2c: imx290: Add support for 74.25MHz clock
    - media: i2c: imx290: Correct range for V4L2_CID_GAIN to 0-238
    - media: i2c: imx290: Convert HMAX setting into V4L2_CID_HBLANK
    - media: i2c: imx290: Add support for V4L2_CID_VBLANK
    - media: i2c: imx290: Add exposure control to the driver.
    - media: i2c: imx290: Add H and V flip controls
    - media: dt-bindings: media: i2c: Add mono version to IMX290 bindings
    - media : i2c: imx290: Add support for the mono sensor variant.
    - media: i2c: imx290: Switch set_hmax to use imx290_write_buffered_reg
    - serial: 8250: bcm2835aux - defer if clock is zero
    - media: Add a pixel format for MIPI packed 12bit luma only.
    - media: Add a pixel format for MIPI packed 14bit luma only.
    - media: bcm2835-unicam: Add support for 12bit mono packed format
    - media: bcm2835-unicam: Add support for 14bit mono sources
    - media: bcm2835-unicam: Add support for unpacked 14bit Bayer formats
    - bcm2835-dma: Add NO_WAIT_RESP flag
    - media: i2c: imx290: Explicitly set v&h blank on mode change
    - media: i2c: imx290: Add support for g_selection to report cropping
    - media: i2c: imx290: Set the colorspace fields in the format
    - media: bcm2835-unicam: Reinstate V4L2_CAP_READWRITE in the caps
    - media: bcm2835-unicam: Ensure type is VIDEO_CAPTURE in [g|s]_selection
    - media: bcm2835: unicam: Set VPU min clock freq to 250Mhz.
    - dt-bindings: bcm2835-unicam: Update documentation with new clock params
    - leds: Add the actpwr trigger
    - bcm2835-dma: Advertise the full DMA range
    - media: bcm2835: unicam: Select MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API
    - staging: media: rpivid: Select MEDIA_CONTROLLER and
      MEDIA_CONTROLLER_REQUEST_API
    - media: bcm2835-unicam: Drop WARN on uing direct cache alias
    - media: i2c: tc358743: Only allow supported pixel fmts in set_fmt
    - dwc_otg: whitelist_table is now productlist_table
    - include/firmware: Add enum for RPI_FIRMWARE_FRAMEBUFFER_GET_DISPLAY_ID
    - media: i2c: Add driver for Sony IMX477 sensor
    - media: i2c: imx477: Add support for adaptive frame control
    - media: i2c: imx477: Return correct result on sensor id verification
    - media: i2c: imx477: Parse and register properties
    - media: bcm2835-unicam: Always service interrupts
    - media: bcm2835: unicam: Fix uninitialized warning
    - media: bcm2835-unicam: Fixup review comments from Hans.
    - media: bcm2835-unicam: Retain packing information on G_FMT
    - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1
    - staging/fbtft: Add support for display variants
    - brcmfmac: Increase power saving delay to 2s
    - rpivid_h265: Fix width/height typo
    - net: bcmgenet: Reset RBUF on first open
    - char: Add broadcom char drivers back to build files
    - dwc_otg: initialise sched_frame for periodic QHs that were parked
    - staging: bcm2835-camera: Replace deprecated V4L2_PIX_FMT_BGR32
    - staging: vc04_services: Add new vc-sm-cma driver
    - staging: vchiq-mmal: Add support for 14bit Bayer
    - staging: mmal-vchiq: Add monochrome image formats
    - staging: mmal-vchiq: Use vc-sm-cma to support zero copy
    - staging: vc04_services: Add a V4L2 M2M codec driver
    - bcm2835-dma: only reserve channel 0 if legacy dma driver is enabled
    - uapi: bcm2835-isp: Add bcm2835-isp uapi header file
    - staging: vc04_services: ISP: Add a more complex ISP processing component
    - gpio: Add gpio-fsm driver
    - staging: bcm2835-audio: Add disable-headphones flag
    - rpisense-fb: Set pseudo_pallete to prevent crash on fbcon takeover
    - dwc_otg: Minimise header and fix build warnings
    - rpivid_h625: Fix build warnings
    - bcm2708_fb: Fix a build warning
    - watchdog: bcm2835: Ignore params after the partition number
    - firmware: raspberrypi: Add support for tryonce reboot flag
    - phy: broadcom: split out the BCM54213PE from the BCM54210E IDs
    - phy: broadcom: Add bcm54213pe configuration
    - PCI: brcmstb: Restore initial fundamental reset
    - Input: edt-ft5x06: Poll the device if no interrupt is configured.
    - drm/panel/raspberrypi-touchscreen: Use independent I2C actions with delay.
    - drm/panel/raspberrypi-ts: Insert delay before polling for startup state
    - dt-bindings: Add compatible for BCM2711 DSI1
    - media: bcm2835-unicam: Correctly handle error propagation for stream on
    - media: bcm2835-unicam: Return early from stop_streaming() if stopped
    - media: bcm2835-unicam: Clear clock state when stopping streaming
    - PCI: brcmstb: Advertise MSI-X support
    - net: lan78xx: Ack pending PHY ints when resetting
    - media: i2c: imx477: Selection compliance fixes
    - vc-sm-cma: fixed kbuild problem
    - staging/vc04_services: Add additional unpacked raw formats
    - staging/bcm2835-codec: Add the unpacked (16bpp) raw formats
    - staging/bcm2835-codec: Log the number of excess supported formats
    - staging/bcm2835-isp: Add the unpacked (16bpp) raw formats
    - staging/bcm2835-isp: Log the number of excess supported formats
    - bcm2835-dma: Avoid losing CS flags after interrupt
    - arch/arm: Add __memset alias to memset_rpi.S
    - bcm2835-dma: Add bcm2835-dma: Add DMA_WIDE_SOURCE and DMA_WIDE_DEST flags
    - uapi: bcm2835-isp: Add colour denoise configuration
    - staging: vc04_services: ISP: Add colour denoise control
    - spi: bcm2835: Workaround/fix for zero-length transfers
    - kbuild: Silence unavoidable dtc overlay warnings
    - media: i2c: imx290: Replace V4L2_CID_GAIN with V4L2_CID_ANALOGUE_GAIN
    - media: i2c: imx290: Fix number of controls in v4l2_ctrl_handler_init
    - dt-binding: display: bcm2711-hdmi: Add CEC and hotplug interrupts
    - staging:bcm2835-camera: Fix the cherry-pick of AWB Greyworld
    - bcm2835-isp: Allow formats with different colour spaces.
    - staging: rpivid: Fix crash when CMA alloc fails
    - media: i2c: imx477: Remove auto frame length adjusting
    - media: i2c: imx477: Add very long exposure control to the driver
    - media: i2c: imx290: Fix up exposure calcuations and ranges
    - media: i2c: imx290: Handle exposure correctly when vblank changes
    - media: i2c: imx477: Fix crop height for 2028x1080 mode
    - media: i2c: imx477: Replace existing 1012x760 mode
    - media: i2c: imx477: Remove internal v4l2_mbus_framefmt from the state
    - media: i2c: imx477: Remove unused function parameter
    - media: bcm2835-unicam: Fix bug in buffer swapping logic
    - Assign crypto aliases to different AES implementation modules
    - media/v4l2_m2m: In buffered mode run jobs if either port is streaming
    - staging/bcm2835-codec: Correct logging of size_t to %zu
    - staging/bcm2835-codec: Add support for pixel aspect ratio
    - staging/bcm2835-codec: Implement additional g_selection calls for decode
    - staging/bcm2835-codec: Add VC-1 support.
    - hack: fixup bcm2835-unicam
    - media: i2c: add ov9281 driver.
    - media: i2c: ov9281: fix mclk issue when probe multiple camera.
    - media: i2c: ov9281: add enum_frame_interval function for iq tool 2.2 and
      hal3
    - media: i2c: ov9281: Fixup for recent kernel releases, and remove custom code
    - media: i2c: ov9281: Read chip ID via 2 reads
    - media: i2c: ov9281: Add support for 8 bit readout
    - media: ov9281: Add 1280x720 and 640x480 modes
    - Fixed picture line bug in all ov9281 modes
    - Added hflip and vflip controls to ov9281
    - media: ov5647: Fix return codes from ov5647_write/ov5647_read functions.
    - media: i2c: ov5647: Parse and register properties
    - clk-raspberrypi: Also support HEVC clock
    - rpivid: Request maximum hevc clock
    - staging/bcm2835-camera: Add support for DMABUFs
    - staging: fbtft: Add minipitft13 variant
    - dwc-otg: fix clang -Wignored-attributes warning
    - dwc-otg: fix clang -Wsometimes-uninitialized warning
    - dwc-otg: fix clang -Wpointer-bool-conversion warning
    - staging: vcsm-cma: Fix memory leak from not detaching dmabuf
    - clk: Introduce a clock request API
    - bcm2835-unicam: Switch to new clock api
    - rpivid: Switch to new clock api
    - rpivid: Only clk_request_done once
    - dwc_otg: fix an undeclared variable
    - drm/panel: jdi-lt070me05000: Use gpiod_set_value_cansleep
    - clk: requests: Ignore if the pointer is null
    - clk: requests: Dereference the request pointer after the check
    - staging/bcm2835-codec: Fix support for levels 4.1 and 4.2
    - staging/bcm2835-codec: Set the colourspace appropriately for RGB formats
    - staging/bcm2835-codec: Pass corrupt frame flag.
    - staging/bcm2835-camera: Add support for H264 levels 4.1 and 4.2
    - staging/bcm2835-codec: Do not update crop from S_FMT after res change
    - staging/bcm2835-isp: Fix compiler warning
    - gpio-poweroff: Remember the old poweroff handler
    - media: i2c: ov5647: Correct pixel array offset
    - media: i2c: ov5647: Correct minimum VBLANK value
    - media: i2c: ov5647: Fix v4l2-compliance failure subscribing to events
    - media: rpivid: Remove the need to have num_entry_points set
    - media: rpivid: Convert to MPLANE
    - media: rpivid: Add an enable count to irq claim Qs
    - RFC: media: Add media_request_{pin,unpin} API
    - media: rpivid: Add a Pass0 to accumulate slices and rework job finish
    - media: rpivid: Map cmd buffer directly
    - media: rpivid: Improve values returned when setting output format
    - media: rpivid: Improve stream_on/off conformance & clock setup
    - media: rpivid: Improve SPS/PPS error handling/validation
    - bcm2835: Allow compressed frames to set sizeimage (#4386)
    - media: i2c: imx477: Fix for long exposure limit calculations
    - clk: bcm2835: Pass DT node to rpi_firmware_get
    - bcm2835-pcm.c: Support multichannel audio
    - bcm2835-pcm: Fix up multichannel pcm audio
    - media: i2c: imx290: Support 60fps in 2 lane operation
    - media: i2c: imx290: Fix the pixel rate at 148.5Mpix/s
    - media: i2c: imx290: Fix clock setup register assignments
    - media: rpivid: Fix H265 aux ent reuse of the same slot
    - media: i2c: ov9281: Remove override of subdev name
    - staging: vc04_services: isp: Set the YUV420/YVU420 format stride to 64 bytes
    - Documentation: devicetree: Add documentation for imx378 sensor
    - media: i2c: imx477: Extend driver to support imx378 sensor
    - dt-bindings: clk: raspberrypi: Remove unused property
    - dt-bindings: display: vc4: Add phandle to the firmware
    - bcm2711_thermal: Don't clamp temperature at zero
    - media: bcm2835-unicam: Forward input status from subdevice
    - media: v4l2-subdev: add subdev-wide state struct
    - drm/vc4: Adopt the dma configuration from the HVS or V3D component
    - Support RPi DPI interface in mode6 for 18-bit color
    - drm/vc4: Add support for DRM_FORMAT_P030 to vc4 planes
    - drm/vc4: Add support for YUV color encodings and ranges
    - drm/vc4: Add FKMS as an acceptable node for dma ranges.
    - drm/vc4: A present but empty dmas disables audio
    - drm/vc4: Add debugfs node that dumps the current display lists
    - drm/vc4: Add all the HDMI registers into the debugfs dumps
    - drm/vc4: Add the 2711 HVS as a suitable DMA node
    - vc4_hdmi: Report that 3d/stereo is allowed
    - vc4: Clear unused infoframe packet RAM registers
    - drm/vc4: Change the default DPI format to being 18bpp, not 24.
    - vc4/drm: Avoid full hdmi audio fifo writes
    - vc4/drm: Fix source offsets with DRM_FORMAT_P030
    - vc4/drm: vc4_plane: Remove subpixel positioning check
    - vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
    - drm/vc4: hdmi: Convert to the new clock request API
    - drm/vc4: Correct pixel order for DSI0
    - drm/vc4: Register dsi0 as the correct vc4 encoder type
    - drm/vc4: Fix dsi0 interrupt support.
    - drm/vc4: Add correct stop condition to vc4_dsi_encoder_disable iteration
    - drm/atomic: Don't fixup modes that haven't been reset
    - drm/vc4: Allow DBLCLK modes even if horz timing is odd.
    - clk: Always clamp the rounded rate
    - drm/vc4: Increase the core clock based on HVS load
    - drm/vc4: hdmi: Simplify the connector state retrieval
    - drm/vc4: Fix timings for interlaced modes
    - dwc_otg: Update NetBSD usb.h header licence
    - drm/vc4: Fix margin calculations for the right/bottom edges
    - drm/vc4: Fix timings for VEC modes
    - drm/vc4: Refactor VEC TV mode setting
    - drm/vc4: Fix definition of PAL-M mode
    - drm/vc4: Add support for more analog TV standards
    - drm/vc4: Allow setting the TV norm via module parameter
    - drm/vc4: Refactor mode checking logic
    - drm/vc4: Add firmware-kms mode
    - media: i2c: imx477: Fix framerates for 1332x990 mode
    - SQUASH: fbmem: Use fallthrough keyword
    - ASoC: bcm: Compiler warnings in audioinjector-octo
    - media: i2c: tc358743: Fix compiler warning
    - ASoC: bcm: Add chipdip-dac driver
    - drm/vc4: hdmi: Unregister codec device on unbind
    - media: i2c: imx290: Add fwnode properties controls
    - media: i2c: ov9281: Add fwnode properties controls
    - media: i2c: ov7251: Add fwnode properties controls
    - media: v4l2: Remove v4l2-ctrls.c
    - media: v4l2: Add HEVC_SCALING_MATRIX attribute to v4l2-ctrl-*
    - media: rpivid: Update to compile with new hevc decode params
    - media: v4l2: Add Greyworld AWB control name
    - videodev2.h: add V4L2_CTRL_FLAG_DYNAMIC_ARRAY
    - v4l2-ctrls: add support for dynamically allocated arrays.
    - media: rpivid: Make slice ctrl dynamic
    - media: rpivid: Only create aux entries for H265 if needed
    - usb: xhci: workaround for bogus SET_DEQ_PENDING endpoint state
    - media: i2c: imx477: Allow control of on-sensor DPC
    - sound/usb: add device quirks for A4Tech FHD 1080p webcams
    - sound/usb: call usb_autopm_get_interface() for devices that should not
    - brcmfmac: Try product-specific clm_blob names first
    - staging: vchiq_arm: Add 36-bit address support
    - staging: vchiq_arm: children inherit DMA config
    - staging: vchiq_arm: Usa a DMA pool for small bulks
    - drm/vc4: Reset HDMI MISC_CONTROL register.
    - drm/vc4: Release workaround buffer and DMA in error paths and unbind
    - drm/vc4: Correct DSI divider calculations
    - drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised
    - drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare
    - drm/panel/raspberrypi-touchscreen: Handle I2C errors.
    - drm/panel-simple: Add a timing for the Raspberry Pi 7" panel
    - Input: edt-ft54x6: Clean up timer and workqueue on remove
    - regulator: rpi-panel: Register with a unique backlight name
    - regulator: rpi-panel: Handle I2C errors/timing to the Atmel
    - regulator: rpi-panel: Serialise operations.
    - regulator: rpi-panel: Ensure the backlight is off during probe.
    - regulator: rpi-panel: Convert to drive lines directly
    - regulator: rpi-panel: Add GPIO control for panel and touch resets
    - staging/bcm2835-codec: Change the default codec res to 32x32
    - staging/vchiq-mmal: Add buffer flags for interlaced video
    - staging/vchiq-mmal: Add parameters for interlaced video support
    - staging/bcm2835-codec: Add support for decoding interlaced streams
    - staging/bcm2835-codec: Correct ENUM_FRAMESIZES stepsize to 2
    - staging/bcm2835-codec: Return buffers to QUEUED not ERROR state
    - staging/bcm2835_codec: Log MMAL flags in hex
    - staging: bcm2835-codec: Allow custom specified strides/bytesperline.
    - staging/vchiq-mmal: Add the deinterlace image effects enums
    - staging/bcm2835_codec: Add support for image_fx to deinterlace
    - staging/bcm2835-v4l2_codec: Fix for encode selection API
    - Add Raspberry Pi PoE+ HAT support
    - configs: Add CAN_PEAK_USB=m
    - ARM: dts: Restore downstream dtbs to Makefile
    - media: rpivid: Avoid returning EINVAL to a G_FMT ioctl
    - net: phy: lan87xx: Allow more time for link detect
    - media: rpivid: Remove unused ctx state variable and defines
    - media: rpivid: Ensure IRQs have completed before uniniting context
    - staging: bcm2835-codec: Allow decode res changed before STREAMON(CAPTURE)
    - staging/bcm2835-codec: Do not send buffers to the VPU unless streaming
    - staging/mmal-vchiq: Rationalise included headers
    - staging: bcm2835-codec: Format changed should trigger drain
    - staging: bcm2835-codec: Signal the firmware to stop on all changes
    - staging/mmal-vchiq: Add module parameter to enable logging.
    - staging: bcm2835-codec: Queue flushed buffers instead of completing
    - staging: mmal-vchiq: Reset buffers_with_vpu on port_enable
    - staging: bcm2835_codec: Correct flushing code for refcounting
    - staging: bcm2835-codec: Ensure all ctrls are set on streamon
    - staging: bcm2835-codec: Add support for H&V Flips to ISP
    - overlays: add support for the MLX90640 thermal camera
    - overlays: Add generic mcp2515 overlay
    - regulator: rpi-panel: Remove get_brightness hook
    - bcm2835_smi_dev: Fix handling of word-odd lengths
    - Revert "mmc: sdhci-iproc: Fix vmmc regulators on iProc"
    - mmc: sdhci-iproc: Fix vmmc regulators (pre-bcm2711)
    - dt-bindings: media: i2c: Add IMX519 CMOS sensor binding
    - media: i2c: Add driver for IMX519 sensor
    - media: i2c: imx519: Advertise embedded data node on media pad 1
    - configs: Add CONFIG_VIDEO_IMX519=m
    - overlays: Add imx519-overlay.dts
    - dtoverlays: Add overlay for ST7735R (160x128) TinyDRM driver
    - dwc_otg: pay attention to qh->interval when rescheduling periodic queues
    - Hifiberry DAC+ADCPro DT overlay: add optional headphone amp
    - Hifiberry DAC+ADCPro: adding optional headphone amp control
    - Add module for 8111h chip used in various CM4 boards
    - drivers/gpio: Add a driver that wraps the PWM API as a GPIO controller
    - rtc: pcf85063: Always clear EXT_TEST from set_time
    - char: vcio: Rewrite as a firmware node child
    - ARM: dts: Make vcio a child of the firmware node
    - ARM: dts: bcm2835_audio missing firmware reference
    - ARM: dts: Delete vestigial vcsm node
    - config: Enable FSFS_FS_SECURITY
    - gpio: bcm-virt: Fix the get() method
    - configs: Add CONFIG_FB_SIMPLE to bcmrpi3_defconfig
    - media: i2c: imx219: Sensor should report RAW color space
    - media: i2c: imx290: Sensor should report RAW color space
    - media: i2c: imx477: Sensor should report RAW color space
    - media: i2c: imx519: Sensor should report RAW color space
    - media: i2c: ov5647: Sensor should report RAW color space
    - media: i2c: ov9281: Sensor should report RAW color space
    - vc04_services: isp: Report input node as wanting full range RAW color space
    - media/bcm2835-unicam: Parse pad numbers correctly
    - media/bcm2835-unicam: Add support for configuration via MC API
    - ARM: dts: vc4-kms-v3d: Always disable firmware HDMI
    - staging/bcm2835-camera: Add support for H264_MIN_QP, H264_MAX_QP
    - staging/bcm2835-camera: Add support for MPEG_VIDEO_FORCE_KEY_FRAME
    - ARM: dts: Add Pi Zero 2 support
    - clk-raspberrypi: Support VEC clock
    - dt: Move VEC clock to clk-raspberrypi
    - clk-bcm2835: Remove VEC clock support
    - drm/vc4: Add support for gamma on BCM2711
    - drm/vc4: Add debugfs node that dumps the vc5 gamma PWL entries
    - drm/vc4: hvs: Force modeset on gamma lut change
    - media: i2c: imx477: Add vsync trigger_mode parameter
    - drm/vc4: Relax VEC modeline requirements and add progressive mode support
    - drm/vc4: Make VEC progressive modes readily accessible
    - bcm2835-v4l2-codec: Remove advertised support of VP8
    - ARM: dts: Rename Zero 2 W DT files
    - brcmfmac: Don't promote INFO logging to ERR
    - dtoverlays: Update all image sensor overlays for Media Controller option
    - ARM: dt: Add DT nodes for the WLAN interfaces
    - brcmfmac: Read alternative firmware names from DT
    - ARM: dts: Provide WLAN firmware names for Zero 2 W
    - drm: Check whether the gamma lut has changed before updating
    - brcmfmac: Protect against reprobing
    - drm/vc4: kms: Fix return code check
    - drm/vc4: kms: Move clock request to our HVS state
    - overlays: Add fbtft overlay
    - configs: Regenerate defconfigs
    - configs: Add NTFS3 support
    - configs: Add kernel SMB3 server support
    - config: Set TCA8418 to module
    - overlays: Additional parameters for gpio-poweroff
    - configs: Add TCA6416 driver module
    - drm: Fix double free from checking if gamma lut has been updated
    - drm/vc4: Enable gamma block only when required.
    - drm/vc4: Only add gamma properties once.
    - dtoverlays: Remove i2c0mux and i20if status from edt-ft5406.dtsi
    - drm/vc4: Validate the size of the gamma_lut
    - drm/vc4: Don't try disabling SCDC on Pi0-3.
    - enable several virtual devices for hosting virtual machines
    - configs: add CONFIG_HID_PLAYSTATION=m and CONFIG_PLAYSTATION_FF=y
    - configs: add LEDS_PWM=y
    - configs: Add USB gadget support (for Zero 2 W)
    - media: i2c: ov5647: Support HFLIP and VFLIP
    - drivers: bcm2835_isp: Allow multiple users for the ISP driver.
    - drivers: bcm2835_isp: Fix div by 0 bug.
    - Pass V4L2_CID_MPEG_VIDEO_H264_MIN_QP/MAX_QP to bcm2835-v4l2-codec
    - ARM: dts: Update rpi-400 and cm4 dts to match 4-b
    - spi: spidev: Restore loading from Device Tree
    - drm/vc4: Add support for composite syncs to vc4_dpi
    - drm/vc4: Ensure vc4_hdmi doesn't use 2711 HPD registers on Pi0-3
    - ARM: dts: gpio-ranges property is now required
    - input: edt-ft5x06: Handle unreliable TOUCH_UP events
    - dtoverlays: Use edt-ft5506 for 10 points, instead of edt-ft5x06
    - staging/bcm2835-codec: bytesperline for YUV420/YVU420 needs to be 64
    - media: rpivid: remove min_buffers_needed from src queue
    - staging/bcm2835-codec: Allow a different stride alignment per role
    - drivers: bcm2835_unicam: Add logging message when a frame is dropped.
    - regulator/rpi-panel-attiny: Don't read the LCD power status
    - regulator/rpi-panel-attiny: Use two transactions for I2C read
    - input: edt-ft5x06: Only look at the number of points reported
    - drm/vc4: Move HDMI reset to pm_resume
    - clk: bcm: rpi: Add the BCM283x pixel clock.
    - dt: bcm283x: Change BCM283x HDMI to use firmware clock driver
    - Revert "Revert "overlays: vc4-kms-v3d: Change composite handling""
    - drm/panel-simple: Populate bpc when using panel-dpi
    - drm/panel-simple: When using panel-dpi, update desc
    - drm/panel-simple: Allow the bus format to be read from DT for panel-dpi
    - drm/vc4: dpi: Add option for inverting pixel clock and output enable
    - drm/vc4: dpi: Ensure a default format is selected
    - dt: bcm270x: Add GPIO defines for RGB565 DPI output modes
    - dtoverlays: Add a generic DPI panel overlay for KMS
    - xhci: quirks: add link TRB quirk for VL805
    - xhci: correct room_on_ring() for cases where there is a single segment
    - media: imx219: Advertise embedded data node on media pad 1
    - vc4/drm: Ignore vc4_hdmi->output_enabled for allowing audio (#4759)
    - ARM: dts: Create bcm2711-rpi-cm4s.dts (#4761)
    - xhci: refactor out TRBS_PER_SEGMENT define in runtime code
    - usb: xhci: add VLI_TRB_CACHE_BUG quirk
    - drm/vc4: Fix build without DRM_VC4_HDMI_CEC
    - dt: Create static regulators and clocks for camera nodes
    - dtoverlays: Convert the camera sensor overlays to use the new regs and clks.
    - media: i2c: ov5647: Add support for regulator control.
    - dtoverlays: Convert ov5647 to use the regulator framework
    - media: i2c: ov7251: Make the enable GPIO optional.
    - ARM: dts: bcm2711-cm4s Correct i2c0mux to use 0/1 and 28/29 & 2 regulators
    - dtoverlays: Add option to select camera as on CAM0 of CM
    - ASoC:ma120x0p: Increase maximum sample rate to 192KHz
    - staging/bcm2835-isp: Fix cleanup after init fail
    - drm/vc4: kms: Take old state core clock rate into account
    - drm/vc4: hvs: Store channel in variable
    - drm/vc4: hvs: Remove dlist setup duplication
    - drm/vc4: hvs: Move the dlist setup to its own function
    - drm/vc4: hvs: Ignore atomic_flush if we're disabled
    - drm/vc4: plane: Use dlist offset instead of pointer
    - drm/vc4: hvs: Create a shadow dlist
    - drm/vc4: Skip writes to disabled packet RAM
    - drm/edid: Don't clear YUV422 if using deep color
    - drm/edid: Rename drm_hdmi_avi_infoframe_colorspace to _colorimetry
    - drm/vc4: hdmi: Add full range RGB helper
    - drm/vc4: hdmi: Use full range helper in csc functions
    - drm/vc4: hdmi: Move XBAR setup to csc_setup
    - drm/vc4: hdmi: Replace CSC_CTL hardcoded value by defines
    - drm/vc4: hdmi: Define colorspace matrices
    - drm/vc4: hdmi: Change CSC callback prototype
    - drm/vc4: hdmi: Move clock validation to its own function
    - drm/vc4: hdmi: Move clock calculation into its own function
    - drm/vc4: hdmi: Take the sink maximum TMDS clock into account
    - drm/vc4: hdmi: Take bpp into account for the scrambler
    - drm/vc4: hdmi: Always try to have the highest bpc
    - drm/vc4: hdmi: Support HDMI YUV output
    - media: v4l2-ctrls: Add V4L2_CID_NOTIFY_GAINS control
    - media: v4l2-ctrls: Document V4L2_CID_NOTIFY_GAINS control
    - Extending ili9881c driver support for nwe080 panel
    - Enable ili9881 panel and pwm backlight driver by default
    - Add panel overlay for CutiePi
    - dtoverlays: Enable cam1_clock when using tc358743 or irs1125
    - uapi/v4l2-controls: Reset V4L2_CID_USER_BCM2835_ISP_BASE to same as 5.10
    - drm/vc4: hdmi: Fix HDMI monitor detection in polled mode
    - drm/vc4: hdmi: Fix no video output on DVI monitors
    - drm/vc4: Correct interrupt enable bits on hvs4
    - staging/bcm2835-codec: Fix typo
    - media: i2c: ov9281: Increase diff between VTS and max exposure
    - bcm2835-v4l2-isp: Add missing lock initialization
    - configs: Enable Azoteq IQS550/572/525
    - overlays: Add overlay for Azoteq IQS550
    - dtoverlays: Add backlight-gpio parameter to vc4-kms-dpi-generic
    - configs: add CONFIG_LEDS_TRIGGER_PATTERN=m
    - drm/vc4: Fix interrupt masking for HVS5.
    - drm/vc4: Add alpha_blend_mode property to each plane.
    - arm: Fix custom rpi __memset32 and __memset64
    - overlays: Add vl805 overlay
    - arm: Fix annoying .eh_frame section warnings
    - drm/vc4: Disable Gamma control on HVS5 due to issues writing the table
    - drm/vc4: hdmi: Fix clock value used for validating hdmi modes
    - [Config] raspi: updateconfigs after rebase to rpi-5.15.y (2022-01-14)

* Miscellaneous Ubuntu changes
    - [Packaging] raspi: Initial import of debian.raspi from impish:linux-raspi
      (5.13.0-1014.16)
    - [Packaging] raspi: Initial version of linux-raspi for Jammy
    - SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart0
    - SAUCE: arm: dts: Add 'brcm,bcm2835-gpio' compatible for gpio
    - SAUCE: Revert "cgroup: Disable cgroup "memory" by default"

[ Ubuntu: 5.15.0-17.17 ]

* jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

linux-raspi (5.15.0-1000.0) jammy; urgency=medium

* Initial version of linux-raspi for Jammy.

-- Juerg Haefliger <juergh@canonical.com>  Fri, 28 Jan 2022 14:42:07 +0100

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

Ubuntu
linux-raspi package

HDMI output freezes under current/proposed impish kernels

Bug Description

CVE References

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	linux-raspi (Ubuntu)	Fix Released	Critical	Unassigned
	Impish	Fix Released	Critical	Unassigned

Ubuntulinux-raspi package

HDMI output freezes under current/proposed impish kernels

Bug Description

CVE References

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux-raspi package