Firmware transaction timeout on Pi4B #4047
Comments
|
In case it is relevant, here are the active lines in /boot/config.txt |
|
Just in case anyone else is encountering the bug: |
|
Perhaps related or similar to: #4033 |
|
I am getting this same hang today after updating and reboot. |
|
Possibly duplicate of this issue: raspberrypi/firmware#1516 |
|
I was having a similar issue decoding h264 with a quite similar backtrace, I was using raspberrypi-firmware (1.20210104-1) and kernel 5.4.83 but it was solved after updating to raspberrypi-firmware (1.20210108-1) released last Friday. |
|
Similar issue here... the triggering action is very different. It locks up the camera at seemingly random times. After a lock, the camera, which is attached to the camera port via ribbon cable, will not function until the next restart. Usually it will hang on reboot. Today, it did reboot cleanly after the lock and after the camera was manually unplugged. This had been working well for about a year before the issue started surfacing. Last value in strace before raspistill hangs indefinately is dmesg attached. This also appears to have been asked on superuser.com (https://superuser.com/questions/1597683/raspbian-failed-to-change-fw-clk-arm-frequency) |
|
Just to add. Similar issue here. It locks the camera at random times. Raspi Pi 4 Headless. Tested with two different camera models. |
|
Quoting is useless. It just means that a firmware transaction has failed to get a response. There is no further useful debug information in there. Please don't bother quoting the backtrace. For a recent camera related issue see raspberrypi/firmware#1552 (now resolved and fix available via rpi-update) The OP appears to be audio related. In which case again there has been an audio fix recently, and the kernel has bumped from 5.4 to 5.10. Please retest on the latest kernel. |
|
I just encountered the same issue with my $ dmesg --follow
[...]
[92775.071098] usb 1-1.1: new high-speed USB device number 15 using xhci_hcd
[92785.041330] usb 1-1.1: new high-speed USB device number 16 using xhci_hcd
[92785.172497] usb 1-1.1: New USB device found, idVendor=0781, idProduct=74d1, bcdDevice= 1.00
[92785.172519] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[92785.172538] usb 1-1.1: Product: Rockbox media player
[92785.172555] usb 1-1.1: Manufacturer: Rockbox.org
[92785.172572] usb 1-1.1: SerialNumber: 2A8C3688501E9FF6100000000
[92785.189881] input: Rockbox.org Rockbox media player Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:0781:74D1.0006/input/input10
[92785.252460] input: Rockbox.org Rockbox media player Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:0781:74D1.0006/input/input11
[92785.252714] hid-generic 0003:0781:74D1.0006: input,hidraw0: USB HID v1.10 Keyboard [Rockbox.org Rockbox media player] on usb-0000:01:00.0-1.1/input0
[92809.840502] usb 1-1.1: USB disconnect, device number 16
[92824.472104] usb 1-1.1: new high-speed USB device number 17 using xhci_hcd
[92831.202229] ------------[ cut here ]------------
[92831.202265] WARNING: CPU: 3 PID: 26310 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0xec/0x128
[92831.202280] Firmware transaction timeout
[92831.202294] Modules linked in: sg joydev cmac bnep hci_uart btbcm bluetooth ecdh_generic ecc brcmfmac brcmutil usblp sha256_generic vc4 cfg80211 cec rfkill drm_kms_helper v3d gpu_sched raspberrypi_hwmon bcm2835_isp(C) bcm2835_codec(C) v4l2_mem2mem bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) drm videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops snd_bcm2835(C) videobuf2_v4l2 videobuf2_common drm_panel_orientation_quirks snd_soc_core videodev vc_sm_cma(C) snd_compress snd_pcm_dmaengine mc snd_pcm rpivid_mem snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops backlight nvmem_rmem uio_pdrv_genirq uio g_ether usb_f_rndis u_ether libcomposite dwc2 roles ip_tables x_tables nhpoly1305 chacha_generic libchacha chacha_neon adiantum libpoly1305 algif_skcipher af_alg ipv6 dm_crypt dm_mod
[92831.203296] CPU: 3 PID: 26310 Comm: kworker/3:0 Tainted: G C 5.10.63-v7l+ #1457
[92831.203306] Hardware name: BCM2711
[92831.203331] Workqueue: events get_values_poll [raspberrypi_hwmon]
[92831.203348] Backtrace:
[92831.203379] [<c0b835a4>] (dump_backtrace) from [<c0b83938>] (show_stack+0x20/0x24)
[92831.203394] r7:ffffffff r6:00000000 r5:60000013 r4:c12e6b3c
[92831.203412] [<c0b83918>] (show_stack) from [<c0b87d24>] (dump_stack+0xcc/0xf8)
[92831.203432] [<c0b87c58>] (dump_stack) from [<c0220b10>] (__warn+0xfc/0x114)
[92831.203447] r10:da404008 r9:00000009 r8:c09bceb4 r7:00000040 r6:00000009 r5:c09bceb4
[92831.203458] r4:c0ea170c r3:c1205094
[92831.203474] [<c0220a14>] (__warn) from [<c0b840dc>] (warn_slowpath_fmt+0xa4/0xd8)
[92831.203486] r7:00000040 r6:c0ea170c r5:c1205048 r4:c0ea172c
[92831.203503] [<c0b8403c>] (warn_slowpath_fmt) from [<c09bceb4>] (rpi_firmware_transaction+0xec/0x128)
[92831.203516] r9:c1a772c0 r8:00000010 r7:00000000 r6:ffffff92 r5:c1a772c0 r4:c1205048
[92831.203532] [<c09bcdc8>] (rpi_firmware_transaction) from [<c09bcfac>] (rpi_firmware_property_list+0xbc/0x170)
[92831.203544] r7:c1205048 r6:da404000 r5:00001000 r4:da40401c
[92831.203558] [<c09bcef0>] (rpi_firmware_property_list) from [<c09bd0d0>] (rpi_firmware_property+0x70/0x118)
[92831.203572] r10:c66bac4c r9:00030046 r8:00000010 r7:c1a772c0 r6:c7e45ed8 r5:00000004
[92831.203582] r4:c66bac40
[92831.203600] [<c09bd060>] (rpi_firmware_property) from [<bf2890c0>] (get_values_poll+0x4c/0x150 [raspberrypi_hwmon])
[92831.203614] r10:00000000 r9:00000000 r8:000000c0 r7:eff31a00 r6:eff2e6c0 r5:c2f52b4c
[92831.203625] r4:c1205048 r3:00000004
[92831.203646] [<bf289074>] (get_values_poll [raspberrypi_hwmon]) from [<c023db68>] (process_one_work+0x250/0x5a0)
[92831.203656] r5:c32edf00 r4:c2f52b4c
[92831.203673] [<c023d918>] (process_one_work) from [<c023df18>] (worker_thread+0x60/0x5c4)
[92831.203687] r10:eff2e6c0 r9:c1203d00 r8:eff2e6d8 r7:00000008 r6:eff2e6c0 r5:c32edf14
[92831.203696] r4:c32edf00
[92831.203713] [<c023deb8>] (worker_thread) from [<c02459f8>] (kthread+0x170/0x174)
[92831.203726] r10:c3dffe74 r9:c32edf00 r8:c023deb8 r7:c7e44000 r6:00000000 r5:c66bae40
[92831.203736] r4:c3331b40
[92831.203752] [<c0245888>] (kthread) from [<c02000ec>] (ret_from_fork+0x14/0x28)
[92831.203763] Exception stack(0xc7e45fb0 to 0xc7e45ff8)
[92831.203775] 5fa0: 00000000 00000000 00000000 00000000
[92831.203788] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[92831.203800] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[92831.203814] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0245888
[92831.203824] r4:c66bae40
[92831.203837] ---[ end trace 8c2a1b359e189a16 ]---
[92831.203872] hwmon hwmon1: Failed to get throttled (-110)
[92832.242279] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 4294967186 (-34)
[92833.282241] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-arm frequency: -110
[92834.602333] xhci_hcd 0000:01:00.0: Abort failed to stop command ring: -110
[92834.634377] xhci_hcd 0000:01:00.0: Host halt failed, -110
[92834.634382] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
[92834.634399] xhci_hcd 0000:01:00.0: HC died; cleaning up
[92834.634500] xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
[92834.634618] usb 1-1: USB disconnect, device number 2
[92835.582329] usb 1-1.1: device not accepting address 17, error -108
[92835.582683] usb 1-1-port1: couldn't allocate usb_device
[92835.582741] usb 1-1.4: USB disconnect, device number 4Could this also be related to #4597? |
|
I’m having the same problem today. I was running After this error, vcgencmd doesn’t work anymore (it just hangs) and dmesg contains numerous other errors like |
|
@gralpli probably best to create a new issue. But it would be useful if you could provide some clues to what provoked the failure. e.g. if you spot a pattern or running a certain program leads to "firmware transaction timeout" we may be able to reproduce it. |
|
Any updates? I have the same problem with Firmware transaction timeout. I am running Xorg session and today I had a black screen, I tried to restart lightdm but without success ( |
|
As has been mentioned previously "Firmware transaction timeout" on its own gives little information. Something has killed the firmware, so any subsequent call to it will fail and timeout. What were you doing prior? Were you playing video or using camera? |
|
I have installed rpi in kiosk, with touchscreen and content is displayed in chromium, there are some css animations. There is also installed monitoring system which checks if screen works, it periodically checks xrandr output if there is correct resolution and rotation (screen is rotated to left, portrait orientation). Kiosk runs 24h, but chromium is driven by crontab (start at 7:00, stop at 19:00). Window manager: openbox Can chromium also cause "Firmware transaction timeout"? Or frequent calling of |
|
Chromium can cause that if it plays embedded videos - does it? |
|
It happened again, chromium was loaded, but with white screen instead of black. |
|
Looks like you are using the (now deprecated) fkms driver, and are on kernel 5.10. Are you on Buster? You should switch to a bullseye image (which has 6.1 kernel) as whatever issues you have may have been fixed. |
|
Yes that is true, dtoverlay=vc4-fkms-v3d, Raspbian GNU/Linux 10 (buster), Linux raspberrypi 5.10.52-v7l+ |
|
It happened again, I had to restart system using What about some watchdog, can it automatically restart system when this error happens? |
|
You could enable the watchdog service which will reboot on a kernel hang, but I don't think you are hitting this here. A better check would be script that checks that firmware side is responsive. Possibly something like: The while should run forever, but if firmware fails to respond, it will try rebooting and then forcing a reboot. |
|
I've got again Firmware transaction timeout, but with kernel 6.1. Here is my dmesg output in attachment and some info:
Should I use kms instead of fkms? |
fkms, bullseye and 6.1 are all legacy and are not receiving bug fixes, It may fix your issue already, and will benefit from future bug fixes. |
Describe the bug
"Firmware transaction timeout" message and gst-launch hang on a Pi 4B 4GB when running
gst-launch-1.0 playbin uri=https://some.domain/720p25-h264-aac.m3u8To reproduce
Boot Pi 4B with Raspberry Pi OS (without X server), then run
gst-launch-1.0 playbin uri=https://some.domain/720p25-h264-aac.m3u8I can try to upload the m3u8 file and associated stream somewhere.
So far, this has been 100% reproducible.
Expected behaviour
No hang.
Actual behaviour
"Firmware transaction timeout" message and gst-launch hang on a Pi 4B 4GB when running
gst-launch-1.0 playbin uri=https://some.domain/720p25-h264-aac.m3u8System
raspinfo hangs, pasting all output before the hang:
System Information
Raspberry Pi 4 Model B Rev 1.2
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
Raspberry Pi reference 2020-08-20
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 9a3a10bf1019ebb2d59053564dc6b90068bad27d, stage4
Linux pi4-nak1 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux
Revision : b03112
Serial : 100000004ad7632c
Model : Raspberry Pi 4 Model B Rev 1.2
Logs
If applicable, add the relevant output from
dmesgor similar.Additional context
Attached devices:
The text was updated successfully, but these errors were encountered: