Raspberry pi 4 USB controller randomly crashes

Bug #1930629 reported by Filip Weiss
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-raspi (Ubuntu)
Fix Released
Undecided
Juerg Haefliger
Focal
Fix Released
Undecided
Juerg Haefliger
Hirsute
Fix Released
Undecided
Juerg Haefliger
Impish
Fix Released
Undecided
Juerg Haefliger

Bug Description

[ Impact ]

USB disks attached to a Pi experience something like:

[ 494.062055] sd 2:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 494.069923] sd 2:0:0:0: [sda] tag#12 CDB: Write(10) 2a 00 00 02 6d 4f 00 00 48 00
[ 499.182085] sd 2:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
[ 499.190310] sd 2:0:0:0: [sda] tag#13 CDB: Write(10) 2a 00 00 02 6d 97 00 00 4d 00
[ 504.302113] sd 2:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT
[ 504.310336] sd 2:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 00 00 95 da 00 00 01 00

And:

[ 535.538311] scsi host2: uas_eh_device_reset_handler start
[ 535.544699] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.554032] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

[ Test Case ]

See below.

[ Where Problems Could Occur ]

Modifications are limited to the USB host xhci driver so problems will likely show up when accessing devices that use this host driver.

[ Original Description ]

My raspberry pi 4 running Ubuntu 20.04 server is constantly having trouble the the usb controller.
I have 2 externally powered USB hubs connected that have a few HDDs plugged in.

After a seemingly random amount of time (between 1 minute and 2 days) the usb controller will crash completely. No USB devices are detected anymore after that, i have to reboot the system.

I have tried:
* Providing a lot of cooling (metal case + desktop size fan)
* Switching the USB Hubs to a different brand
* Switching the power supply of the USB hubs
* Switching the power supply of the raspberry

Nothing helped, so i concluded that this probably is a kernel bug. I think the USB controller should not crash at the very least.

I've attached my dmesg.

lsb_release -rd
  Description: Ubuntu 20.04.2 LTS
  Release: 20.04

linux-raspi version: 5.4.0.1035.70

uname -a
  Linux pi 5.4.0-1035-raspi #38-Ubuntu SMP PREEMPT Tue Apr 20 21:37:03 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

lsusb (after crash)
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-1035-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
ImageMediaBuild: 20210201.1
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci-vt: -[0000:00]---00.0-[01]----00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
Package: linux-raspi
PackageArchitecture: arm64
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=E4:5F:01:1D:06:FE vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
ProcVersionSignature: Ubuntu 5.4.0-1035.38-raspi 5.4.106
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-1035-raspi N/A
 linux-backports-modules-5.4.0-1035-raspi N/A
 linux-firmware 1.187.12
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
StagingDrivers: bcm2835_isp bcm2835_v4l2 bcm2835_mmal_vchiq bcm2835_codec snd_bcm2835 vc_sm_cma
Tags: arm64-image raspi-image focal uec-images staging
Uname: Linux 5.4.0-1035-raspi aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
acpidump:

CVE References

Revision history for this message
Filip Weiss (filip-weiss) wrote :
Revision history for this message
Juerg Haefliger (juergh) wrote :

Can you provide some additional data?
$ apport-collect 1930629

Revision history for this message
Filip Weiss (filip-weiss) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected arm64-image focal raspi-image staging uec-images
description: updated
Revision history for this message
Filip Weiss (filip-weiss) wrote : CRDA.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : Dependencies.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : Lspci.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : Lsusb-v.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : ProcModules.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : UdevDb.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote : WifiSyslog.txt

apport information

Revision history for this message
Filip Weiss (filip-weiss) wrote (last edit ):

I ran apport-collect as requested :)

I ran it AFTER the problem occured (again).

One more note: I upgraded the firmware to the very latest version using rpi-update (https://github.com/Hexxeh/rpi-update) because i was desperate. It did not fix the problem.

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

Could be related but i have different symptoms. I can still reboot the pi and nothing hangs (except IO to the disconnected drives of course).

I have tried more things to debug this. It seems that on raspi-os with the same setup the USB controller does not crash but some seagate drives still disconnect randomly. They keep spinning up and disconnecting after that. Only fix is a reboot.

It also happens less frequently on USB2. I don't get why. Sound like a thermal issue to me, but i also have a fan in place for the external HDDs. My second guess would be power supply, but i have a 5A one connected to the hub, and it's only the seagate drives that disconnect.

Anyway, while using raspi-os still does not solve my problem it at least does not crash the USB controller.
Maybe ubuntu needs to update the raspi firmware or kernel to also get this behaviour?

Revision history for this message
Juerg Haefliger (juergh) wrote :
Download full text (13.4 KiB)

Hit something that looks related:

[ 494.062055] sd 2:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 494.069923] sd 2:0:0:0: [sda] tag#12 CDB: Write(10) 2a 00 00 02 6d 4f 00 00 48 00
[ 499.182085] sd 2:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
[ 499.190310] sd 2:0:0:0: [sda] tag#13 CDB: Write(10) 2a 00 00 02 6d 97 00 00 4d 00
[ 504.302113] sd 2:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT
[ 504.310336] sd 2:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 00 00 95 da 00 00 01 00
[ 504.318248] sd 2:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT
[ 504.326469] sd 2:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 00 00 99 8b 00 00 1a 00
[ 504.334437] sd 2:0:0:0: [sda] tag#15 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
[ 504.342655] sd 2:0:0:0: [sda] tag#15 CDB: Write(10) 2a 00 00 00 08 01 00 00 01 00
[ 504.350586] sd 2:0:0:0: [sda] tag#14 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[ 504.358801] sd 2:0:0:0: [sda] tag#14 CDB: Write(10) 2a 00 00 02 6d e4 00 00 34 00
[ 504.382114] scsi host2: uas_eh_device_reset_handler start
[ 504.470745] usb 2-2.2: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 504.501501] scsi host2: uas_eh_device_reset_handler success
[ 505.096703] xhci_hcd 0000:01:00.0: ERROR Transfer event for unknown stream ring slot 5 ep 7
[ 505.105187] xhci_hcd 0000:01:00.0: @000000042e805080 00000000 00000000 05000000 05088001
[ 535.538311] scsi host2: uas_eh_device_reset_handler start
[ 535.544699] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.554032] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.563364] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.572693] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.582020] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.591345] sd 2:0:0:0: [sda] tag#17 uas_zap_pending 0 uas-tag 1 inflight: CMD
[ 535.591346] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 535.608031] sd 2:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 00 02 6d 4f 00 00 48 00
[ 535.615624] sd 2:0:0:0: [sda] tag#18 uas_zap_pending 0 uas-tag 2 inflight: CMD
[ 535.623038] sd 2:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 00 02 6d 97 00 00 4d 00
[ 535.630629] sd 2:0:0:0: [sda] tag#16 uas_zap_pending 0 uas-tag 3 inflight: CMD
[ 535.638042] sd 2:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 00 00 95 da 00 00 01 00
[ 535.645632] sd 2:0:0:0: [sda] tag#19 uas_zap_pending 0 uas-tag 4 inflight: CMD
[ 535.653044] sd 2:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 00 00 99 8b 00 00 1a 00
[ 535.660635] sd 2:0:0:0: [sda] tag#22 uas_zap_pending 0 uas-tag 5 inflight: CMD
[ 535.668048] sd 2:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 00 00 08 01 00 00 01 00
[ 535.675638] sd 2:0:0:0: [sda] tag#23 uas_zap_pending 0 uas-tag 6 inflight: CMD
[ 535.683050] sd 2:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 00 02 6d e4 00 00 34 00
[ 535.770913] usb ...

Revision history for this message
Filip Weiss (filip-weiss) wrote (last edit ):

How did you do that @juergh? Similar setup?

In the meantime i have tried to narrow the bug down further:

* I have replaced the raspberry pi
* Ensured that i use grounded power supplied for the hubs
* Tested with raspi-os & old "known good" kernel 4.19 (from https://github.com/raspberrypi/linux/issues/3981)

I experienced the problem with all of these. The error messages differ but the end result of all USB devices disconnecting was the same (btw this includes a USB stick that is NOT connected to a hub).
So i think this is not an ubuntu specific problem.

This problem does not occur if i use the USB2 ports.

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

There might be multiple issues. One seems to be UAS and/or SCSI pass-through related. From your dmesg, this looks interesting:

[ 2638.936483] usb 2-1.4.3: reset SuperSpeed Gen 1 USB device number 10 using xhci_hcd
[ 2638.960797] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

I believe 2-1.4.3 is your ASMT (asmedia) device. What exactly is that? That reset could have been a result of a smartd poke (you're running smartd, right?) and might cause additional problems down the line. Can you decrease the smartd interval to check if the problem shows up earlier? Kill the smartd daemon and run it manually like: smartd -d -i 15.

Regarding USB2: The USB2 and USB3 controllers are completely different. USB2 is part of the SoC whereas USB3 is a PCIe attached dedicated controller. Different drivers and obviously lots of other differences.

Revision history for this message
Filip Weiss (filip-weiss) wrote :

Thanks for looking into it and for the USB explanation.

The asmedia device is the oldest HDD enclosure that is connected to the pi.

Smartd was running on the ubuntu pi but did not run on raspi-os. I can still try to increase the checks though, maybe it will make it more reproducible..?

Revision history for this message
Juerg Haefliger (juergh) wrote :
Changed in linux-raspi (Ubuntu Focal):
assignee: nobody → Juerg Haefliger (juergh)
Juerg Haefliger (juergh)
Changed in linux-raspi (Ubuntu Impish):
status: Invalid → New
Changed in linux-raspi (Ubuntu Hirsute):
assignee: nobody → Juerg Haefliger (juergh)
Changed in linux-raspi (Ubuntu Impish):
assignee: nobody → Juerg Haefliger (juergh)
Revision history for this message
Filip Weiss (filip-weiss) wrote :

Thanks for still looking into this. I actually shut down my project because of the HDD bugs.
Sorry for not responding, that was the reason.

But to resolve this issue I would plug everything thing in one more time and test it again, if you think this could fix it.

Seeing that the fix is 3 days old this probably did not land in the ubuntu or raspi-os repos yet, or is it?

Revision history for this message
Luca Carlon (carlon-luca) wrote :

I have been testing the patches for 6 days now. No deadlock yet. I typically had deadlocks in 2 hours to 3 days, but even weeks in some cases.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux-raspi (Ubuntu Hirsute):
status: New → Confirmed
Changed in linux-raspi (Ubuntu):
status: New → Confirmed
Juerg Haefliger (juergh)
description: updated
Revision history for this message
Luca Carlon (carlon-luca) wrote :

Any news about this critical issue? This bug causes data corruption, instability of the system and loss of remote control of the system (a reboot can deadlock the system before ssh is up).

Revision history for this message
Juerg Haefliger (juergh) wrote :
Changed in linux-raspi (Ubuntu Impish):
status: Confirmed → Fix Committed
Changed in linux-raspi (Ubuntu Hirsute):
status: Confirmed → Fix Committed
Changed in linux-raspi (Ubuntu Focal):
status: Confirmed → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-raspi/5.11.0-1018.19 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'.

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-hirsute
Revision history for this message
Filip Weiss (filip-weiss) wrote :

5 days to test is not enough considering that the bug might take longer to occur.

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

I understand. Can you at least run some (basic) tests and confirm we didn't introduce a regression?

Revision history for this message
Dave Jones (waveform) wrote :

Yup, still testing here too; I've got at least one SATA cable and drive that used to reliably show this issue, but usually only after numerous hours so it's taking some time to verify. Also got a few other SATA cables and drives I'd like to test out quickly just to make sure there's no basic regressions.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-raspi/5.4.0-1044.48 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (163.8 KiB)

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

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

  * impish/linux-raspi: 5.13.0-1007.8 -proposed tracker (LP: #1943746)

  * impish/linux-raspi: Update to upstream raspberrypi rpi-5.13.y (2021-08-27)
    (LP: #1942881)
    - bcm2835: Allow compressed frames to set sizeimage (#4386)
    - media: i2c: imx477: Fix for long exposure limit calculations
    - ASoC: hdmi-codec: Rework to support more controls
    - snd: iec958: split status creation and fill
    - ASoC: hdmi-codec: Add iec958 controls
    - ASoC: hdmi-codec: Add a prepare hook
    - 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: Increase the core clock based on HVS load
    - clk: bcm2835: Pass DT node to rpi_firmware_get
    - ARM: dts: Add firmware reference to sdhost node
    - mmc: sdhost: Pass DT pointer to rpi_firmware_get
    - drm/vc4: Register HDMI codec
    - drm/vc4: hdmi: Remove redundant variables
    - 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
    - drm/vc4: Fix timings for interlaced modes
    - drm/vc4: Don't create hvs_load_tracker on fkms
    - media: rpivid: Fix H265 aux ent reuse of the same slot
    - Support RPi DPI interface in mode6 for 18-bit color
    - overlays: Add dpi18cpadhi, vc4-kms-dpi-at056tn53v1
    - drm: vc4: Fix pixel-wrap issue with DVP teardown
    - drm/vc4: Increase the core clock to a minimum of 500MHz
    - media: i2c: ov9281: Remove override of subdev name
    - drm/vc4: hdmi: Use a fixed rate for the HSM clock on BCM2835
    - drm/vc4: hdmi: Enable the scrambler on reconnection
    - configs: Add CONFIG_MACVTAP=m (arm64 only)
    - staging: vc04_services: isp: Set the YUV420/YVU420 format stride to 64 bytes
    - Documentation: devicetree: Add documentation for imx378 sensor
    - overlays: Add overlay for imx378 sensor
    - media: i2c: imx477: Extend driver to support imx378 sensor
    - overlays: Make i2c-rtc and i2c-rtc-gpio share RTCs
    - dt-bindings: clk: raspberrypi: Remove unused property
    - dt-bindings: display: vc4: Add phandle to the firmware
    - 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: dts: rpi: Add the firmware node to vc4
    - drm/vc4: hdmi: Put the device on error in pre_crtc_configure
    - 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: Add missing clk_disable_unprepare on error path
    - drm/vc4: hdmi: Warn if we access the controller while disabled
    - drm/vc4: hdmi: Move initial register read after pm_runtime_get
    - vc4/drv: Only notify firmware of display done with kms
    - dwc_otg: Update NetBSD usb.h header li...

Changed in linux-raspi (Ubuntu Impish):
status: Fix Committed → Fix Released
Dave Jones (waveform)
tags: added: verification-done-hirsute
removed: verification-needed-hirsute
Revision history for this message
Dave Jones (waveform) wrote :

Finished verifying that it at least hasn't broken anything in the hirsute release; tested USB boot and operation on a Pi 4B rev 1.1, rev 1.4, two board variants of the 400, and a 3B+ with two different SSDs and four different SATA-USB interfaces (two ASMedia, one JMicron, and one Sabrent - the latter turned out to be iffy under all kernels, so no regression there!).

Given the length of time over which this bug tends to reproduce (sometimes as long as a couple of days), I can't say for certain it's fixed in all cases but the system on which it reliably reproduced before (an 8GB Pi 4 with an ASMedia interface between a Samsung SSD) has been running without interruption all week, and none of the other configurations displayed any issues so I'd be reasonably confident in saying there's no regressions at least.

I'll move onto Focal tests next...

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (81.1 KiB)

This bug was fixed in the package linux-raspi - 5.11.0-1019.20

---------------
linux-raspi (5.11.0-1019.20) hirsute; urgency=medium

  * hirsute/linux-raspi: 5.11.0-1019.20 -proposed tracker (LP: #1944172)

  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-08-26 (LP: #1942170)
    - sound/usb: add device quirks for A4Tech FHD 1080p webcams
    - sound/usb: call usb_autopm_get_interface() for devices that should not
    - overlays: ghost-amp: Add DAC mute control
    - clk: Introduce a clock request API
    - drm/vc4: hdmi: Convert to the new clock request API
    - drm/vc4: hdmi: Convert to the new clock request API
    - bcm2835-unicam: Switch to new clock api
    - rpivid: Switch to new clock api
    - net: usb: r8152: use new tasklet API
    - r8152: replace several functions about phy patch request
    - r8152: adjust the flow of power cut for RTL8153B
    - r8152: enable U1/U2 for USB_SPEED_SUPER
    - r8152: check if the pointer of the function exists
    - r8152: replace netif_err with dev_err
    - r8152: spilt rtl_set_eee_plus and r8153b_green_en
    - r8152: set inter fram gap time depending on speed
    - r8152: adjust rtl8152_check_firmware function
    - r8152: add help function to change mtu
    - r8152: support new chips
    - r8152: support PHY firmware for RTL8156 series
    - r8152: search the configuration of vendor mode
    - rpivid: Only clk_request_done once
    - dwc_otg: fix an undeclared variable
    - Revert "drm/vc4: Add configuration for BCM2711 DSI1."
    - Revert "drm/vc4: Add support for DSI0"
    - drm/vc4: drv: Remove the DSI pointer in vc4_drv
    - drm/vc4: dsi: Use snprintf for the PHY clocks instead of an array
    - drm/vc4: dsi: Introduce a variant structure
    - drm/vc4: dsi: Add support for DSI0
    - drm/vc4: dsi: Add configuration for BCM2711 DSI1
    - 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/panel: jdi-lt070me05000: Use gpiod_set_value_cansleep
    - defconfigs: Add PANEL_JDI_LT070ME05000 DSI panel
    - dtoverlays: Add overlays for JDI LT070ME05000 1200x1920 DSI panel
    - clk: requests: Ignore if the pointer is null
    - drm/vc4: hvs: Make the HVS bind first
    - drm/vc4: hdmi: Properly compute the BVB clock rate
    - drm/vc4: hdmi: Check and warn if we can't reach 4kp60 frequencies
    - drm/vc4: hdmi: Enable the scrambler
    - drm/vc4: hdmi: Raise the maximum clock rate
    - vc4/drm: hdmi: Handle case when bvb clock is null
    - overlays: spi-rtc: Add ds3232 and ds3234
    - drm/vc4: Fix VEC address for BCM2711 in the devicetrees
    - drm/vc4: Separate VEC compatible variants
    - configs: Enable ATA and AHCI for SATA drive support.
    - 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 s...

Changed in linux-raspi (Ubuntu Hirsute):
status: Fix Committed → Fix Released
Revision history for this message
Dave Jones (waveform) wrote :

Finished a similar verification run on focal; tested USB boot and operation on a Pi 4B rev 1.1, rev 1.4, two board variants of the 400, and a 3B+ with one SSD (the other I was using for another test run) and three SATA-USB interfaces (two ASMedia, one JMicro, excluded the Sabrent as I suspect my one is broken).

Again, given the length of time over which the bug tends to reproduce, I can't say for certain it's fixed in all cases but none of these configurations displayed any issues, all booted happily, and ran smartctl successfully.

tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (34.4 KiB)

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

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

  * focal/linux-raspi: 5.4.0-1044.48 -proposed tracker (LP: #1942552)

  * Raspberry pi 4 USB controller randomly crashes (LP: #1930629)
    - usb: xhci: workaround for bogus SET_DEQ_PENDING endpoint state
    - xhci: guard accesses to ep_state in xhci_endpoint_reset()

  [ Ubuntu: 5.4.0-85.95 ]

  * focal/linux: 5.4.0-85.95 -proposed tracker (LP: #1942557)
  * please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248)
    - [Config] Disable virtualbox dkms build
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.09.06)
  * LRMv5: switch primary version handling to kernel-versions data set
    (LP: #1928921)
    - [Packaging] switch to kernel-versions
  * disable “CONFIG_HISI_DMA” config for ubuntu version (LP: #1936771)
    - Disable CONFIG_HISI_DMA
    - [Config] Record hisi_dma no longer built for arm64
  * memory leaking when removing a profile (LP: #1939915)
    - apparmor: Fix memory leak of profile proxy
  * CryptoExpress EP11 cards are going offline (LP: #1939618)
    - s390/zcrypt: Support for CCA protected key block version 2
    - s390: Replace zero-length array with flexible-array member
    - s390/zcrypt: Use scnprintf() for avoiding potential buffer overflow
    - s390/zcrypt: replace snprintf/sprintf with scnprintf
    - s390/ap: Remove ap device suspend and resume callbacks
    - s390/zcrypt: use fallthrough;
    - s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc
    - s390/ap: remove power management code from ap bus and drivers
    - s390/ap: introduce new ap function ap_get_qdev()
    - s390/zcrypt: use kzalloc
    - s390/zcrypt: fix smatch warnings
    - s390/zcrypt: code beautification and struct field renames
    - s390/zcrypt: split ioctl function into smaller code units
    - s390/ap: rename and clarify ap state machine related stuff
    - s390/zcrypt: provide cex4 cca sysfs attributes for cex3
    - s390/ap: rework crypto config info and default domain code
    - s390/zcrypt: simplify cca_findcard2 loop code
    - s390/zcrypt: remove set_fs() invocation in zcrypt device driver
    - s390/ap: remove unnecessary spin_lock_init()
    - s390/zcrypt: Support for CCA APKA master keys
    - s390/zcrypt: introduce msg tracking in zcrypt functions
    - s390/ap: split ap queue state machine state from device state
    - s390/ap: add error response code field for ap queue devices
    - s390/ap: add card/queue deconfig state
    - s390/sclp: Add support for SCLP AP adapter config/deconfig
    - s390/ap: Support AP card SCLP config and deconfig operations
    - s390/ap/zcrypt: revisit ap and zcrypt error handling
    - s390/zcrypt: move ap_msg param one level up the call chain
    - s390/zcrypt: Introduce Failure Injection feature
    - s390/zcrypt: fix wrong format specifications
    - s390/ap: fix ap devices reference counting
    - s390/zcrypt: return EIO when msg retry limit reached
    - s390/zcrypt: fix zcard and zqueue hot-unplug memleak
    - s390/ap: Fix hanging ioctl caused by wrong msg counter
  * memfd from ubun...

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.