rpi3b+ becomes unresponsive after closing a program

Bug #1880388 reported by RJ
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-raspi (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
linux-raspi-5.4 (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned

Bug Description

I am running ROS2 on this raspberry pi 3B+ that is running as the main computer on a turtlebot3. There is two USB devices connected to the RPi, one is to communicate with the LIDAR and the other is to communicate with the control board, a OpenCR board.

After "bringing the robot up" I open a new shell in tmux, and run `ros2 topic echo battery_state` which starts outputting ROS2 messages to the terminal. Upon ctrl+c'ing out of this, the system become unresponsive. I repeated this while connected to the serial console and captured the error messages that are being output.

Issue I rose on github:
https://github.com/ROBOTIS-GIT/turtlebot3/issues/593

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11
ProcVersionSignature: User Name 5.4.0-1011.11-raspi 5.4.34
Uname: Linux 5.4.0-1011-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27
Architecture: arm64
CasperMD5CheckResult: skip
Date: Sun May 24 10:31:26 2020
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

Serial console output:

MMC: mmc@7e202000: 0, mmcnr@7e300000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... 6 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
## Info: input data size = 6 = 0x6
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2603 bytes read in 6 ms (422.9 KiB/s)
## Executing script at 02400000
8378005 bytes read in 364 ms (21.9 MiB/s)
Total of 1 halfword(s) were the same
Decompressing kernel...
Uncompressed size: 25905664 = 0x18B4A00
29426757 bytes read in 1262 ms (22.2 MiB/s)
Booting Ubuntu (with booti) from mmc 0:...
## Flattened Device Tree blob at 02600000
   Booting using the fdt blob at 0x2600000
   Using Device Tree in place at 0000000002600000, end 0000000002609f2f

Starting kernel ...

[ 1.966598] spi-bcm2835 3f204000.spi: could not get clk: -517
ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory
ext4
Thu Jan 1 00:00:07 UTC 1970
date: invalid date ' Wed Apr 1 17:23:46 2020'
-.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
sys-fs-fuse-connections.mount
sys-kernel-config.mount
systemd-sysctl.service
systemd-random-seed.service
systemd-sysusers.service
keyboard-setup.service
systemd-tmpfiles-setup-dev.service
swapfile.swap
lvm2-monitor.service
systemd-udevd.service
systemd-journald.service
systemd-udev-trigger.service
systemd-journal-flush.service
[ 14.813759] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 15.128676] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 15.174878] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
systemd-rfkill.service
systemd-udev-settle.service
netplan-wpa-wlan0.service
multipathd.service
[ 17.840942] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
systemd-fsckd.service
snap-core18-1708.mount
snap-core18-1753.mount
snap-lxd-14808.mount
snap-lxd-15066.mount
snap-snapd-7267.mount
systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service
boot-firmware.mount
console-setup.service
         Mounting Arbitrary Executable File Formats File System...
finalrd.service
[ OK ] Finished Tell Plymouth To Write Out Runtime Data.
[ OK ] Mounted Arbitrary Executable File Formats File System.
proc-sys-fs-binfmt_misc.mount
[ OK ] Finished Create Volatile Files and Directories.
systemd-tmpfiles-setup.service
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[ OK ] Finished Enable support for…onal executable binary formats.
binfmt-support.service
[ OK ] Finished Update UTMP about System Boot/Shutdown.
systemd-update-utmp.service
[ OK ] Finished Load AppArmor profiles.
apparmor.service
         Starting Load AppArmor prof… managed internally by snapd...
[ OK ] Finished Load AppArmor prof…es managed internally by snapd.
snapd.apparmor.service
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Set.
[ OK ] Reached target System Time Synchronized.
systemd-timesyncd.service
[ 25.080879] cloud-init[1148]: Cloud-init v. 20.1-10-g71af48df-0ubuntu5 running 'init-local' at Sun, 24 May 2020 08:15:54 +0000. Up 24.20 seconds.
[ OK ] Finished Initial cloud-init job (pre-networking).
[ OK ] Reached target Network (Pre).
cloud-init-local.service
         Starting Network Service...
[ OK ] Started Network Service.
systemd-networkd.service
         Starting Wait for Network to be Configured...
         Starting Network Name Resolution...
[ OK ] Finished Wait for Network to be Configured.
systemd-networkd-wait-online.service
         Starting Initial cloud-init…b (metadata service crawler)...
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Host and Network Name Lookups.
systemd-resolved.service
[ 29.538238] cloud-init[1170]: Cloud-init v. 20.1-10-g71af48df-0ubuntu5 running 'init' at Sun, 24 May 2020 08:15:59 +0000. Up 28.67 seconds.
[ 29.538788] cloud-init[1170]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++
[ 29.540670] cloud-init[1170]: ci-info: +--------+-------+----------------------------+---------------+--------+-------------------+
[ 29.541896] cloud-init[1170]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
[ 29.543805] cloud-init[1170]: ci-info: +--------+-------+----------------------------+---------------+--------+-------------------+
[ 29.545298] cloud-init[1170]: ci-info: | eth0 | False | . | . | . | b8:27:eb:89:55:2a |
[ 29.546816] cloud-init[1170]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |
[ 29.548589] cloud-init[1170]: ci-info: | lo | True | ::1/128 | . | host | . |
[ 29.550684] cloud-init[1170]: ci-info: | wlan0 | True | 192.168.1.104 | 255.255.255.0 | global | b8:27:xx:dc:xx:xx |
[ 29.552179] cloud-init[1170]: ci-info: | wlan0 | True | fe80::ba27:ebff:fedc:7f/64 | . | link | b8:27:xx:dc:xx:xx |
[ 29.554004] cloud-init[1170]: ci-info: +--------+-------+----------------------------+---------------+--------+-------------------+
[ 29.555532] cloud-init[1170]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info++++++++++++++++++++++++++++++
[ 29.557284] cloud-init[1170]: ci-info: +-------+-------------+-------------+-----------------+-----------+-------+
[ 29.558922] cloud-init[1170]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
[ 29.560561] cloud-init[1170]: ci-info: +-------+-------------+-------------+-----------------+-----------+-------+
[ 29.562171] cloud-init[1170]: ci-info: | 0 | 0.0.0.0 | 192.168.1.1 | 0.0.0.0 | wlan0 | UG |
[ 29.564460] cloud-init[1170]: ci-info: | 1 | 192.168.1.0 | 0.0.0.0 | 255.255.255.0 | wlan0 | U |
[ 29.566004] cloud-init[1170]: ci-info: | 2 | 192.168.1.1 | 0.0.0.0 | 255.255.255.255 | wlan0 | UH |
[ 29.567921] cloud-init[1170]: ci-info: +-------+-------------+-------------+-----------------+-----------+-------+
[ 29.569529] cloud-init[1170]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
[ 29.571384] cloud-init[1170]: ci-info: +-------+-------------+---------+-----------+-------+
[ 29.573242] cloud-init[1170]: ci-info: | Route | Destination | Gateway | Interface | Flags |
[ 29.575341] cloud-init[1170]: ci-info: +-------+-------------+---------+-----------+-------+
[ 29.577009] cloud-init[1170]: ci-info: | 1 | fe80::/64 | :: | wlan0 | U |
[ 29.578952] cloud-init[1170]: ci-info: | 3 | local | :: | wlan0 | U |
[ 29.580974] cloud-init[1170]: ci-info: | 4 | ff00::/8 | :: | wlan0 | U |
[ 29.582773] cloud-init[1170]: ci-info: +-------+-------------+---------+-----------+-------+
[ OK ] Finished Initial cloud-init job (metadata service crawler).
[ OK ] Reached target Cloud-config availability.
[ OK ] Reached target System Initialization.
cloud-init.service
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Periodic ext4 Onlin…data Check for All Filesystems.
[ OK ] Started Discard unused blocks once a week.
[ OK ] Started Refresh fwupd metadata regularly.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Message of the Day.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Paths.
[ OK ] Reached target Timers.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Listening on Open-iSCSI iscsid Socket.
[ OK ] Listening on Socket unix for snap application lxd.daemon.
         Starting Socket activation for snappy daemon.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Listening on Socket activation for snappy daemon.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
         Starting Accounts Service...
         Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started D-Bus System Message Bus.
dbus.service
[ OK ] Started Save initial kernel messages after boot.
dmesg.service
         Starting Remove Stale Onlin…xt4 Metadata Check Snapshots...
[ OK ] Started irqbalance daemon.
irqbalance.service
         Starting Dispatcher daemon for systemd-networkd...
[ OK ] Started Set the CPU Frequency Scaling governor.
ondemand.service
         Starting System Logging Service...
         Starting Snap Daemon...
         Starting Login Service...
         Starting WPA supplicant...
[ OK ] Finished Remove Stale Online ext4 Metadata Check Snapshots.
[ OK ] Started System Logging Service.
rsyslog.service
[ OK ] Started WPA supplicant.
wpa_supplicant.service
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Reached target Network.
avahi-daemon.service
[ OK ] Reached target Network is Online.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
         Starting LSB: automatic crash report generation...
         Starting Deferred execution scheduler...
         Starting Availability of block devices...
[ OK ] Started Regular background program processing daemon.
cron.service
         Starting Service for snap application lxd.activate...
         Starting OpenBSD Secure Shell server...
         Starting Permit User Sessions...
[ OK ] Started Deferred execution scheduler.
atd.service
[ OK ] Finished Availability of block devices.
blk-availability.service
[ OK ] Started Login Service.
systemd-logind.service
[ OK ] Finished Permit User Sessions.
systemd-user-sessions.service
         Starting Hold until boot process finishes up...
         Starting Terminate Plymouth Boot Screen...

Ubuntu 20.04 LTS whopper ttyS0

whopper login:

[ 379.937717] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 379.946532] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 379.957445] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 380.993421] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 381.002224] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 381.002229] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 382.049419] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 382.058204] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 382.069109] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 383.105431] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 383.117817] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 383.132371] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 384.161443] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 384.173864] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 384.188390] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 385.217451] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 385.229839] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 385.244342] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 386.273448] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 386.285902] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 386.300457] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 387.333453] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 387.345845] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 387.360371] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 388.385476] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 388.397857] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 388.412356] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 389.445471] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 389.457865] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 389.472366] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 390.117438] mmc0: timeout waiting for hardware interrupt.
[ 390.373441] mmc1: Timeout waiting for hardware interrupt.
[ 390.380828] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[ 390.501480] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 390.513696] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 390.528025] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 391.553488] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 391.565694] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 391.580033] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 392.609489] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 392.621701] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 392.636036] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 393.665497] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 393.677717] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 393.692057] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 394.725504] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 394.737709] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 394.752122] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 395.777509] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 1400000 (-110)
[ 395.789895] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:176: Error occurred setting a new frequency (1400000)
[ 395.804412] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 400.109498] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 400.117471] rcu: 3-...0: (0 ticks this GP) idle=3ce/1/0x4000000000000002 softirq=19876/19876 fqs=2442
[ 400.353510] mmc0: timeout waiting for hardware interrupt.
[ 400.609504] mmc1: Timeout waiting for hardware interrupt.
[ 400.616877] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[ 410.593565] mmc0: timeout waiting for hardware interrupt.
[ 410.849594] mmc1: Timeout waiting for hardware interrupt.
[ 410.856918] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[ 420.837624] mmc0: timeout waiting for hardware interrupt.
[ 421.089625] mmc1: Timeout waiting for hardware interrupt.
[ 421.096834] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[ 431.073685] mmc0: timeout waiting for hardware interrupt.
[ 431.329691] mmc1: Timeout waiting for hardware interrupt.
[ 431.336803] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[ 441.313750] mmc0: timeout waiting for hardware interrupt.
[ 441.569749] mmc1: Timeout waiting for hardware interrupt.
[ 441.576783] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110
[ 451.553804] mmc0: timeout waiting for hardware interrupt.
[ 451.809805] mmc1: Timeout waiting for hardware interrupt.
[ 451.816732] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -110

Revision history for this message
RJ (russkel) wrote :
description: updated
RJ (russkel)
description: updated
RJ (russkel)
summary: - rpi3b becomes unresponsive after closing a program
+ rpi3b+ becomes unresponsive after closing a program
description: updated
Revision history for this message
RJ (russkel) wrote :

Reportedly this was not an issue with 18.04.3, although I cannot say I have personally tried this.

Revision history for this message
Juerg Haefliger (juergh) wrote :

Can you attach kern.log?

Revision history for this message
RJ (russkel) wrote :

Sure. I have attached the most recent one.

Revision history for this message
Juerg Haefliger (juergh) wrote :

Sorry for the late reply. That kern.log doesn't help much since it doesn't contain any of the errors mentioned above.

From https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 it seems that 18.04.3 works but 18.04.4 does not? Is that a true statement?

Juerg Haefliger (juergh)
Changed in linux-raspi (Ubuntu Focal):
status: New → Confirmed
Revision history for this message
Juerg Haefliger (juergh) wrote :

I'm able to reproduce this on a Focal 5.4 kernel by sending data to a Pi via a USB/serial adapter. I'm not able to reproduce this with the Raspberry Pi OS running a 5.4 kernel. I recompiled the Raspi OS kernel using the Ubuntu config and *now* I can reproduce it. It seems it's a config option difference in the Ubuntu kernel that triggers this.

Revision history for this message
RJ (russkel) wrote :

Just want to add that I also had no problems with Raspberry Pi OS 64b beta, and is what I am using at the moment.

Thanks Juerg.

Revision history for this message
Juerg Haefliger (juergh) wrote :
Revision history for this message
Juerg Haefliger (juergh) wrote :
Revision history for this message
Juerg Haefliger (juergh) wrote :

@RJ, I've built a test kernel, can you give that a try?
$ sudo add-apt-repository ppa:juergh/lp1880388
$ sudo apt-get update
$ sudo apt install linux-raspi

Revision history for this message
RJ (russkel) wrote :

@juergh, sorry I didn't get an email notification for what ever reason.
I have loaded this onto a board and will try tomorrow and let you know! Thanks.

Juerg Haefliger (juergh)
Changed in linux-raspi (Ubuntu Focal):
status: Confirmed → Fix Committed
Revision history for this message
RJ (russkel) wrote :

Just reiterating what I mentioned in the Github issue, that the test kernel works great. Thanks.

Juerg Haefliger (juergh)
Changed in linux-raspi (Ubuntu Bionic):
status: New → Fix Committed
Changed in linux-raspi (Ubuntu):
status: New → Invalid
no longer affects: linux-raspi (Ubuntu Bionic)
no longer affects: linux-raspi (Ubuntu Bionic)
no longer affects: linux-raspi-5.4 (Ubuntu Focal)
Changed in linux-raspi-5.4 (Ubuntu):
status: New → Invalid
Changed in linux-raspi-5.4 (Ubuntu Bionic):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (106.7 KiB)

This bug was fixed in the package linux-raspi - 5.8.0-1002.5

---------------
linux-raspi (5.8.0-1002.5) groovy; urgency=medium

  * groovy/linux-raspi: 5.8.0-1002.5 -proposed tracker (LP: #1894068)

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

  * Miscellaneous Ubuntu changes
    - [Config] raspi: updateconfigs after rebase to Ubuntu-5.8.0-18.19
    - [Packaging] raspi: Add bootstrap PPA for getabis

  [ Ubuntu: 5.8.0-18.19 ]

  * groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)
  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * Groovy update: v5.8.4 upstream stable release (LP: #1893048)
    - drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
    - drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
    - drm/ast: Remove unused code paths for AST 1180
    - drm/ast: Initialize DRAM type before posting GPU
    - khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
    - ALSA: hda: avoid reset of sdo_limit
    - ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
    - ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
    - can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
      j1939_tp_txtimer()
    - can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
    - spi: Prevent adding devices below an unregistering controller
    - io_uring: find and cancel head link async work on files exit
    - mm/vunmap: add cond_resched() in vunmap_pmd_range
    - romfs: fix uninitialized memory leak in romfs_dev_read()
    - kernel/relay.c: fix memleak on destroy relay channel
    - uprobes: __replace_page() avoid BUG in munlock_vma_page()
    - squashfs: avoid bio_alloc() failure with 1Mbyte blocks
    - mm: include CMA pages in lowmem_reserve at boot
    - mm, page_alloc: fix core hung in free_pcppages_bulk()
    - ASoC: amd: renoir: restore two more registers during resume
    - RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
    - opp: Enable resources again if they were disabled earlier
    - opp: Put opp table in dev_pm_opp_set_rate() for empty tables
    - opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
    - ext4: do not block RWF_NOWAIT dio write on unallocated space
    - ext4: fix checking of directory entry validity for inline directories
    - jbd2: add the missing unlock_buffer() in the error path of
      jbd2_write_superblock()
    - scsi: zfcp: Fix use-after-free in request timeout handlers
    - selftests: kvm: Use a shorter encoding to clear RAX
    - s390/pci: fix zpci_bus_link_virtfn()
    - s390/pci: re-introduce zpci_remove_device()
    - s390/pci: fix PF/VF linking on hot plug
    - s390/pci: ignore stale configuration request event
    - mm/memory.c: skip spurious TLB flush for retried page fault
    - drm: amdgpu: Use the correct size when allocating memory
    - drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
    - drm/amd/display: Fix incorrect backlight register offset for DCN
    - drm/amd/display: Fix EDID parsing after resume from suspend
    - drm/amd/display: Blank stream before destroying HDCP session
    - drm/amd...

Changed in linux-raspi (Ubuntu):
status: Invalid → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (43.2 KiB)

This bug was fixed in the package linux-raspi-5.4 - 5.4.0-1019.21~18.04.1

---------------
linux-raspi-5.4 (5.4.0-1019.21~18.04.1) bionic; urgency=medium

  * bionic/linux-raspi-5.4: 5.4.0-1019.21~18.04.1 -proposed tracker
    (LP: #1894635)

  * rpi3b+ becomes unresponsive after closing a program (LP: #1880388) // Build
    preemptible raspi kernels (LP: #1890808)
    - [Config] raspi-bionic: Switch from PREEMPT_VOLUNTARY to PREEMPT

  [ Ubuntu: 5.4.0-1019.21 ]

  * focal/linux-raspi: 5.4.0-1019.21 -proposed tracker (LP: #1894636)
  * rpi3b+ becomes unresponsive after closing a program (LP: #1880388) // Build
    preemptible raspi kernels (LP: #1890808)
    - [Config] raspi: Switch from PREEMPT_VOLUNTARY to PREEMPT
  * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654)
  * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109)
    - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
  * Packaging resync (LP: #1786013)
    - update dkms package versions
    - update dkms package versions
  * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
    - [packaging] add signed modules for nvidia 450 and 450-server
  * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support
    (LP: #1892849)
    - s390/pci: fix zpci_bus_link_virtfn()
    - s390/pci: re-introduce zpci_remove_device()
    - s390/pci: fix PF/VF linking on hot plug
  * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name
    (LP: #1891454)
    - s390/cpum_cf, perf: change DFLT_CCERROR counter name
  * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression
    introduced by multi-function support (LP: #1891437)
    - s390/pci: fix enabling a reserved PCI function
  * CVE-2020-12888
    - vfio/type1: Support faulting PFNMAP vmas
    - vfio-pci: Fault mmaps to enable vma tracking
    - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
  * [Hyper-V] VSS and File Copy daemons intermittently fails to start
    (LP: #1891224)
    - [Packaging] Bind hv_vss_daemon startup to hv_vss device
    - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
  * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704)
    - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense
    - ALSA: hda - Add DP-MST jack support
    - ALSA: hda - Add DP-MST support for non-acomp codecs
    - ALSA: hda - Add DP-MST support for NVIDIA codecs
    - ALSA: hda: hdmi - fix regression in connect list handling
    - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx
    - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms
    - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms
    - ALSA: hda - Fix DP-MST support for NVIDIA codecs
  * Focal update: v5.4.60 upstream stable release (LP: #1892899)
    - smb3: warn on confusing error scenario with sec=krb5
    - genirq/affinity: Make affinity setting if activated opt-in
    - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()
    - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context()
    - PCI: Add device even if driver attach failed
    - PCI: qcom: Define some PARF params needed...

Changed in linux-raspi-5.4 (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (42.9 KiB)

This bug was fixed in the package linux-raspi - 5.4.0-1019.21

---------------
linux-raspi (5.4.0-1019.21) focal; urgency=medium

  * focal/linux-raspi: 5.4.0-1019.21 -proposed tracker (LP: #1894636)

  * rpi3b+ becomes unresponsive after closing a program (LP: #1880388) // Build
    preemptible raspi kernels (LP: #1890808)
    - [Config] raspi: Switch from PREEMPT_VOLUNTARY to PREEMPT

  [ Ubuntu: 5.4.0-48.52 ]

  * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654)
  * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109)
    - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
  * Packaging resync (LP: #1786013)
    - update dkms package versions
    - update dkms package versions
  * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
    - [packaging] add signed modules for nvidia 450 and 450-server
  * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support
    (LP: #1892849)
    - s390/pci: fix zpci_bus_link_virtfn()
    - s390/pci: re-introduce zpci_remove_device()
    - s390/pci: fix PF/VF linking on hot plug
  * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name
    (LP: #1891454)
    - s390/cpum_cf, perf: change DFLT_CCERROR counter name
  * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression
    introduced by multi-function support (LP: #1891437)
    - s390/pci: fix enabling a reserved PCI function
  * CVE-2020-12888
    - vfio/type1: Support faulting PFNMAP vmas
    - vfio-pci: Fault mmaps to enable vma tracking
    - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
  * [Hyper-V] VSS and File Copy daemons intermittently fails to start
    (LP: #1891224)
    - [Packaging] Bind hv_vss_daemon startup to hv_vss device
    - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
  * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704)
    - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense
    - ALSA: hda - Add DP-MST jack support
    - ALSA: hda - Add DP-MST support for non-acomp codecs
    - ALSA: hda - Add DP-MST support for NVIDIA codecs
    - ALSA: hda: hdmi - fix regression in connect list handling
    - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx
    - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms
    - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms
    - ALSA: hda - Fix DP-MST support for NVIDIA codecs
  * Focal update: v5.4.60 upstream stable release (LP: #1892899)
    - smb3: warn on confusing error scenario with sec=krb5
    - genirq/affinity: Make affinity setting if activated opt-in
    - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()
    - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context()
    - PCI: Add device even if driver attach failed
    - PCI: qcom: Define some PARF params needed for ipq8064 SoC
    - PCI: qcom: Add support for tx term offset for rev 2.1.0
    - btrfs: allow use of global block reserve for balance item deletion
    - btrfs: free anon block device right after subvolume deletion
    - btrfs: don't allocate anonymous block device for user invisible roots
    - btrfs: r...

Changed in linux-raspi (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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