Closed sferlix closed 3 years ago
pelwell
commented
3 years ago What is typically running at the time? It looks like a camera app of some kind.
You could try adding start_debug=1 to config.txt, then when it fails check "sudo vcbdg log msg" as above but also "sudo vcdbg log assert".
sferlix
commented
3 years ago Yes, a camera app is running: a raspistill command is in crontab to collect an image every minute and to save it on the disk, overwriting the previous one.
About the sudo vcdbg log (posted above) there is something about camera:
017460.432: camsubs: Looking for camera 0: i2c_port = 0, led gpio = -1, power enable gpio = 133 017761.171: camsubs: Camera not found 017761.319: camsubs: Looking for camera 0: i2c_port = 0, led gpio = -1, power enable gpio = 133 018062.050: camsubs: Camera not found 018062.192: camsubs: Looking for camera 0: i2c_port = 0, led gpio = -1, power enable gpio = 133 018063.820: camsubs: Camera found OK
is this normal ? thanks a lot frank
sferlix
commented
3 years ago Update:
any help ?
please find below the message in the log
thanks in advance
frank
------------[ cut here ]------------ Feb 18 09:42:12 raspberrypi kernel: [58182.493366] WARNING: CPU: 3 PID: 18706 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0x ec/0x128 Feb 18 09:42:12 raspberrypi kernel: [58182.493374] Firmware transaction timeout Feb 18 09:42:12 raspberrypi kernel: [58182.493381] Modules linked in: rfcomm bnep hci_uart btbcm bluetooth ecdh_generic ecc fuse 8021q garp st p llc joydev brcmfmac brcmutil sha256_generic cfg80211 bcm2835_codec(C) i2c_bcm2835 v3d v4l2_mem2mem rfkill bcm2835_isp(C) gpu_sched videobuf2 _dma_contig snd_bcm2835(C) bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) vc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 cec raspberrypi_hwmon v ideobuf2_common videodev drm_kms_helper mc vc_sm_cma(C) drm drm_panel_orientation_quirks rpivid_mem snd_soc_core snd_compress snd_pcm_dmaengin e snd_pcm snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops backlight uio_pdrv_genirq nvmem_rmem uio i2c_dev ip_tables x_tables ipv6 Feb 18 09:42:12 raspberrypi kernel: [58182.493757] CPU: 3 PID: 18706 Comm: kworker/3:3 Tainted: G C 5.10.11-v7l+ #1399 Feb 18 09:42:12 raspberrypi kernel: [58182.493760] Hardware name: BCM2711 Feb 18 09:42:12 raspberrypi kernel: [58182.493785] Workqueue: events v3d_clock_down_work [v3d]
pelwell
commented
3 years ago That's just telling you that the firmware stopped responding - it's just an indication that something went wrong.
As I said above:
You could try adding start_debug=1 to config.txt, then when it fails check "sudo vcbdg log msg" as above but also "sudo vcdbg log assert".
sferlix
commented
3 years ago sure !
I was lucky because the error now showed up quickly, after hard reboot, without having to wait for hours.
please find it below. Hope this may help to address. thanks frank
sudo vcdbg log assert
005190.840: assert( timeout != 0 ) failed; ../../../../../vcfw/drivers/chip/vciv/2708/clock_2711.c::clock_wait_busy line 2014 rev 99d9a48
vcdbg_ctx_get_dump_stack: dump_stack failed
----------------
pi@raspberrypi:~/program $ sudo vcdb log msg
sudo: vcdb: command not found
pi@raspberrypi:~/program $ sudo vcdbg log msg
005194.358: arasan: arasan_emmc_open
005354.938: brfs: File read: /mfs/sd/config.txt
005355.781: brfs: File read: 1820 bytes
005449.610: brfs: File read: /mfs/sd/config.txt
006536.058: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
006538.689: *** Restart logging
006538.711: brfs: File read: 1820 bytes
006542.584: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
006579.677: HDMI0: hdmi_pixel_encoding: 300000000
006579.689: HDMI1: hdmi_pixel_encoding: 300000000
006584.702: dtb_file 'bcm2711-rpi-4-b.dtb'
006590.150: brfs: File read: /mfs/sd/bcm2711-rpi-4-b.dtb
006590.166: Loading 'bcm2711-rpi-4-b.dtb' to 0x100 size 0xbd2d
006602.763: brfs: File read: 48429 bytes
006613.971: brfs: File read: /mfs/sd/overlays/overlay_map.dtb
006676.967: brfs: File read: 1523 bytes
006679.169: brfs: File read: /mfs/sd/config.txt
006679.581: dtparam: i2c_arm=on
006687.981: dtparam: audio=on
006697.797: brfs: File read: 1820 bytes
006710.894: brfs: File read: /mfs/sd/overlays/vc4-fkms-v3d.dtbo
006727.721: Loaded overlay 'vc4-fkms-v3d'
006766.908: brfs: File read: 1446 bytes
006777.163: brfs: File read: /mfs/sd/cmdline.txt
006777.247: Read command line from file 'cmdline.txt':
006777.279: 'console=serial0,115200 console=tty1 root=PARTUUID=5239546c-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles'
008082.439: brfs: File read: 166 bytes
009454.125: brfs: File read: /mfs/sd/kernel7l.img
009454.164: Loading 'kernel7l.img' to 0x8000 size 0x65d6a8
009454.218: Device tree loaded to 0x1ffe3c00 (size 0xc39d)
009461.697: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
014467.164: vchiq_core: vchiq_init_state: slot_zero = 0xcfd80000, is_master = 1
014470.790: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
014478.413: TV service:host side not connected, dropping notification 0x00000002, 0x00000001, 0x00000010
018057.734: camsubs: Looking for camera 0: i2c_port = 0, led gpio = -1, power enable gpio = 133
018358.380: camsubs: Camera not found
pi@raspberrypi:~/program $ I also have this that sounds interesting (I hope):
Feb 18 11:39:21 raspberrypi kernel: [ 4.731063] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000
Feb 18 11:39:21 raspberrypi kernel: [ 4.733784] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000
Feb 18 11:39:21 raspberrypi kernel: [ 4.735954] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000
Feb 18 11:39:21 raspberrypi kernel: [ 4.739556] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000
Feb 18 11:39:21 raspberrypi kernel: [ 4.851446] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 4.853752] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Feb 18 11:39:21 raspberrypi kernel: [ 4.853779] [vc_sm_connected_init]: start
Feb 18 11:39:21 raspberrypi kernel: [ 4.871244] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 4.878584] mc: Linux media interface: v0.10
Feb 18 11:39:21 raspberrypi kernel: [ 4.882113] [vc_sm_connected_init]: installed successfully
Feb 18 11:39:21 raspberrypi kernel: [ 4.915813] bcm2835_audio bcm2835_audio: card created with 4 channels
Feb 18 11:39:21 raspberrypi kernel: [ 4.994666] bcm2835_audio bcm2835_audio: card created with 4 channels
Feb 18 11:39:21 raspberrypi kernel: [ 4.998555] videodev: Linux video capture interface: v2.00
Feb 18 11:39:21 raspberrypi kernel: [ 5.036313] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 5.047270] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 5.052151] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 5.064713] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 5.080318] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Feb 18 11:39:21 raspberrypi kernel: [ 5.086114] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
Feb 18 11:39:21 raspberrypi kernel: [ 5.091995] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
Feb 18 11:39:21 raspberrypi kernel: [ 5.096967] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
Feb 18 11:39:21 raspberrypi kernel: [ 5.456215] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 18 11:39:21 raspberrypi kernel: [ 5.580387] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Feb 18 11:39:21 raspberrypi kernel: [ 5.676132] usbcore: registered new interface driver brcmfmac
Feb 18 11:39:21 raspberrypi kernel: [ 5.702209] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
Feb 18 11:39:21 raspberrypi kernel: [ 6.474475] ------------[ cut here ]------------
Feb 18 11:39:21 raspberrypi kernel: [ 6.474525] WARNING: CPU: 1 PID: 170 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0xec/0x128
Feb 18 11:39:21 raspberrypi kernel: [ 6.474541] Firmware transaction timeout
Feb 18 11:39:21 raspberrypi kernel: [ 6.474556] Modules linked in: joydev vc4(+) brcmfmac brcmutil cec sha256_generic v3d(+) drm_kms_helper gpu_sched cfg80211 i2c_bcm2835 drm rfkill raspberrypi_hwmon bcm2835_codec(C+) bcm2835_v4l2(C+) bcm2835_isp(C+) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common drm_panel_orientation_quirks videodev snd_soc_core mc snd_bcm2835(C) vc_sm_cma(C) snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops backlight rpivid_mem uio_pdrv_genirq uio nvmem_rmem i2c_dev ip_tables x_tables ipv6
Feb 18 11:39:21 raspberrypi kernel: [ 6.475305] CPU: 1 PID: 170 Comm: systemd-udevd Tainted: G C 5.10.11-v7l+ #1399
Feb 18 11:39:21 raspberrypi kernel: [ 6.475320] Hardware name: BCM2711
Feb 18 11:39:21 raspberrypi kernel: [ 6.475335] Backtrace: Is that with the camera attached? The firmware says it can't find it, which isn't a good sign.
sferlix
commented
3 years ago yes, the camera properly it's attached. No one touched the camera and cable.
I have tried with 3 different cameras: official HQ, official NoIR and unofficial HQ. Same issue (not systematic, but happens randomly).. I also changed cables (actually, each camera has its own cable)
Please note that when the Pi becomes unresponsive, I have to switch off. Once I restart the Pi, it works fine without moving the camera (until next failure).
Could it be an issue with the board ? Maybe I could return the board, as I bought it on Amazon 1 week ago. thanks frank
pelwell
commented
3 years ago I rarely use the cameras, but it should be detected correct on each boot.
How is your system powered? Do you have any other peripherals attached?
In one of the earlier posts it says GPIO memory = 512, - I presume that's really talking about gpu_mem. Does it need to be such a large carve-out for the VPU?
sferlix
commented
3 years ago system is powered by power cable (the one provided by the case manufacturer)
sorry, it was gpu_mem = 512 formerly it was 256 and also 128. I decided to increase it after having experienced issues. I go back to 256
thanks
sferlix
commented
3 years ago Ciao,
while using the camera via command line (no crontab) to detect optimal parameters, I got into this:
ERROR: <class 'picamera.exc.PiCameraRuntimeError'>
Traceback (most recent call last):
File "skycam.py", line 137, in
picamera.exc.PiCameraRuntimeError: No data recevied from sensor. Check all connections, including the SUNNY chip on the camera board**
after this, I start getting:
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC ERROR: <class 'picamera.exc.PiCameraMMALError'>
So it seems you are rigth. But cables are well connected. Issue happens with all cameras I have tried. Should I return the Pi ?
thanks frank
EDIT: I can confirm that the error appears randomly. Without restarting or touching anything (cable included), the raspistill keeps working. Not sure this depends on the cable. I will buy another Pi 4 B and I will check.
sferlix
commented
3 years ago Again after 20ish hours.
Here are the logs (many of these messages)
`7829.036: imx477_open: read id 1143 succes 0! 3657842.042: Using RPI AWB 3665828.315: mmal: fail_destroy: Timed out waiting to destroy ril.camera 1907489.263: mmalsrv: mmal_server_create_control_service: failed to create control service - error 1 2313809.362: TV service:host side not connected, dropping notification 0x00000001, 0x00000007, 0x00000000 2315783.985: TV service:host side not connected, dropping notification 0x00000002, 0x00000004, 0x00000001 2322823.500: TV service:host side not connected, dropping notification 0x00000001, 0x00000007, 0x00000000 2323893.713: TV service:host side not connected, dropping notification 0x00000002, 0x00000004, 0x00000001
pi@raspberrypi:/var/log$ sudo vcdbg log assert 3422746.648: assert( temps->last_tone_mapping_params_valid ) failed; ../../../../../middleware/ISP/tuner/isp_tuner_brcm_agc.c::isp_tunerbrcmagc_switch_mode line 2745 rev 99d9a48 vcdbg_ctx_get_dump_stack: dump_stack failed `
Looks the same... all of the sudden, the camera seems to disappear..
pelwell
commented
3 years ago Is that the same Pi 4 or a different one?
sferlix
commented
3 years ago same Pi. Sorry, I just realized that some log messages are not readable..
ghost
commented
3 years ago I think I am seeing similar (not exactly same) issue and can reproduce the outcome via the following steps. Hopefully this helpful and not a different matter.
Apologies in advance for any reporting faux pas. This is my first GitHub post/comment.
I am running Raspberry Pi 3 Model B Plus Rev 1.3 with latest Raspian upgrades/updates as of today along with UFW and fail2ban installed. Using Pi Camera V2.
PART 1 ---------------------------------------------------------------------------------------------------
I was trying to get the following (test.py code below) to work but kept getting the memory error below... (note that the code works without memory error if camera default resolution 1920x1080 is used instead of 3264x2464)
After boot, via terminal...
$ cd scanner $ source venv/bin/activate (venv) $ pip list
Package Version
cycler 0.10.0
decorator 4.4.2
imageio 2.9.0
imutils 0.5.4
kiwisolver 1.3.1
matplotlib 3.3.4
networkx 2.5
numpy 1.20.1
opencv-contrib-python 4.1.0.25
picamera 1.13
Pillow 8.1.0
pip 18.1
pkg-resources 0.0.0
pyparsing 2.4.7
python-dateutil 2.8.1
PyWavelets 1.1.1
scikit-image 0.18.1
scipy 1.6.0
setuptools 40.8.0
six 1.15.0
tifffile 2021.2.1
(venv) $ cat test.py
from picamera.array import PiRGBArray from picamera import PiCamera import time
print("Code run started")
camera = PiCamera() camera.resolution = (3264,2464)
camera.start_preview() time.sleep(2.0) camera.stop_preview()
raw_capture = PiRGBArray(camera) time.sleep(2.0) camera.capture(raw_capture, format="bgr") image = raw_capture.array
print("Code run completed.")
(venv) $ python test.py Code run started mmal: mmal_vc_port_enable: failed to enable port vc.ril.camera:out:2(BGR3): ENOMEM mmal: mmal_port_enable: failed to enable port vc.ril.camera:out:2(BGR3)(0x19e0640) (ENOMEM) Traceback (most recent call last): File "/home/rpi/scanner/venv/lib/python3.7/site-packages/picamera/camera.py", line 1418, in capture encoder.start(output) File "/home/rpi/scanner/venv/lib/python3.7/site-packages/picamera/encoders.py", line 1166, in start super(PiRawImageMixin, self).start(output) File "/home/rpi/scanner/venv/lib/python3.7/site-packages/picamera/encoders.py", line 377, in start self.output_port.enable(self._callback) File "/home/rpi/scanner/venv/lib/python3.7/site-packages/picamera/mmalobj.py", line 1249, in enable prefix="Unable to enable port %s" % self.name) File "/home/rpi/scanner/venv/lib/python3.7/site-packages/picamera/exc.py", line 184, in mmal_check raise PiCameraMMALError(status, prefix) picamera.exc.PiCameraMMALError: Unable to enable port vc.ril.camera:out:2: Out of memory
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test.py", line 16, in
PART 2 ----------------------------------------------------------------------------------------------
Poking around the internet, suggestion was to increase GPU Memory to 256MB. Using Raspberry Pi Configuration, did this and rebooted device. Repeated the steps above, and the code "hangs" (and the display freezes), but remote SSH session accepted and log shows...
Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628475] ------------[ cut here ]------------ Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628507] WARNING: CPU: 2 PID: 34 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0xec/0x128 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628513] Firmware transaction timeout Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628519] Modules linked in: rfcomm cmac bnep hci_uart btbcm bluetooth ecdh_generic ecc fuse joydev uinput 8021q garp stp llc brcmfmac brcmutil raspberrypi_hwmon sha256_generic cfg80211 rfkill bcm2835_codec(C) v4l2_mem2mem bcm2835_isp(C) bcm2835_v4l2(C) videobuf2_vmalloc bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common snd_bcm2835(C) snd_pcm snd_timer videodev snd mc vc_sm_cma(C) nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 fixed xt_hl ip6_tables ip6t_rt uio_pdrv_genirq uio nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nft_compat nft_counter nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink i2c_dev ip_tables x_tables ipv6 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628898] CPU: 2 PID: 34 Comm: kworker/2:1 Tainted: G C 5.10.11-v7+ #1399 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628901] Hardware name: BCM2835 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628912] Workqueue: events dbs_work_handler Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628920] Backtrace: Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628934] [<809dc018>] (dump_backtrace) from [<809dc3a8>] (show_stack+0x20/0x24) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628941] r7:ffffffff r6:00000000 r5:60000013 r4:80ee5d14 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628951] [<809dc388>] (show_stack) from [<809e0558>] (dump_stack+0xcc/0xf8) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628960] [<809e048c>] (dump_stack) from [<8011ec64>] (warn+0xfc/0x114) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628968] r10:aac03008 r9:00000009 r8:8081db18 r7:00000040 r6:00000009 r5:8081db18 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628972] r4:80c6a3f4 r3:80e05050 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628981] [<8011eb68>] (warn) from [<809dca28>] (warn_slowpath_fmt+0xa4/0xd8) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628986] r7:00000040 r6:80c6a3f4 r5:80e05008 r4:80c6a414 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.628995] [<809dc988>] (warn_slowpath_fmt) from [<8081db18>] (rpi_firmware_transaction+0xec/0x128) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629002] r9:816ac440 r8:00000018 r7:00000000 r6:ffffff92 r5:816ac440 r4:80e05008 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629011] [<8081da2c>] (rpi_firmware_transaction) from [<8081dc10>] (rpi_firmware_property_list+0xbc/0x16c) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629016] r7:80e05008 r6:aac03000 r5:00001000 r4:aac03024 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629025] [<8081db54>] (rpi_firmware_property_list) from [<8081dd30>] (rpi_firmware_property+0x70/0x118) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629032] r10:8f3031cc r9:00030002 r8:00000018 r7:816ac440 r6:8168dd48 r5:0000000c Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629035] r4:8f3031c0 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629047] [<8081dcc0>] (rpi_firmware_property) from [<806aac48>] (raspberrypi_clock_property+0x54/0x7c) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629054] r10:00000000 r9:00000000 r8:81e60780 r7:00000000 r6:53724e00 r5:8168dd70 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629058] r4:80e05008 r3:0000000c Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629067] [<806aabf4>] (raspberrypi_clock_property) from [<806aacbc>] (raspberrypi_fw_get_rate+0x4c/0x70) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629072] r5:00000000 r4:80e05008 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629080] [<806aac70>] (raspberrypi_fw_get_rate) from [<806a1618>] (clk_recalc+0x44/0x84) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629084] r4:817103c0 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629090] [<806a15d4>] (clk_recalc) from [<806a1908>] (clk_recalc_rates+0x30/0x94) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629096] r5:00000000 r4:817103c0 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629103] [<806a18d8>] (clk_recalc_rates) from [<806a19c4>] (clk_core_get_rate_recalc+0x58/0x5c) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629108] r7:00000000 r6:80e05008 r5:23c34600 r4:817103c0 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629116] [<806a196c>] (clk_core_get_rate_recalc) from [<806a19f0>] (clk_get_rate+0x28/0x38) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629120] r5:23c34600 r4:81e60780 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629128] [<806a19c8>] (clk_get_rate) from [<807ea920>] (dev_pm_opp_set_rate+0x70/0x588) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629133] r5:23c34600 r4:81e53600 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629141] [<807ea8b0>] (dev_pm_opp_set_rate) from [<807f5810>] (set_target+0x38/0x3c) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629148] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:80ff1e5c r5:80e05008 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629151] r4:81e53a00 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629159] [<807f57d8>] (set_target) from [<807f0514>] (cpufreq_driver_target+0x1bc/0x540) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629167] [<807f0358>] (cpufreq_driver_target) from [<807f38a4>] (od_dbs_update+0xc4/0x170) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629174] r10:af8e8640 r9:84284c80 r8:84d288c0 r7:84284b00 r6:84284c80 r5:84284b00 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629177] r4:81e53a00 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629186] [<807f37e0>] (od_dbs_update) from [<807f4b08>] (dbs_work_handler+0x3c/0x64) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629193] r9:00000000 r8:80f12bb4 r7:81e53a00 r6:84284b04 r5:00000000 r4:84284b38 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629204] [<807f4acc>] (dbs_work_handler) from [<8013b78c>] (process_one_work+0x254/0x584) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629210] r9:00000000 r8:af8eb900 r7:00000080 r6:af8e8640 r5:81650000 r4:84284b38 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629218] [<8013b538>] (process_one_work) from [<8013bb1c>] (worker_thread+0x60/0x5c4) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629225] r10:af8e8640 r9:80e03d00 r8:af8e8658 r7:00000008 r6:af8e8640 r5:81650014 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629229] r4:81650000 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629238] [<8013babc>] (worker_thread) from [<801435a4>] (kthread+0x170/0x174) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629245] r10:81565e74 r9:81650000 r8:8013babc r7:8168c000 r6:00000000 r5:8164d040 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629249] r4:8164d100 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629256] [<80143434>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629262] Exception stack(0x8168dfb0 to 0x8168dff8) Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629267] dfa0: 00000000 00000000 00000000 00000000 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629275] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629280] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629287] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143434 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629291] r4:8164d040 Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629296] ---[ end trace 38f990ef8c8483eb ]--- Feb 22 17:21:16 raspberrypi-scanner kernel: [ 172.629326] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 4294967186 (-34) Feb 22 17:21:17 raspberrypi-scanner kernel: [ 173.668493] hwmon hwmon1: Failed to get throttled (-110) Feb 22 17:21:18 raspberrypi-scanner kernel: [ 174.708449] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-arm frequency: -110
PART 3 -----------------------------------------------------------------------------------------------
sudo reboot now does not reboot machine; have to unplug and plug back in to unfreeze screen, etc.
Resetting GPU memory to 128MB returns back to PART 1 above.
Of side note: I was not having this problem on Pi Zero W a week ago. Only encountered when I moved over to Pi 3B+
ghost
commented
3 years ago PS to comment above: camera confirmed working via raspistill command.
ghost
commented
3 years ago PPS. I forgot to mention that the above occurs when I am remotely connecting to the Pi using VNC (with Direct Capture Enabled).
zt4
commented
3 years ago I've got the same issue... one Pi 4 with a camera, two Pi Zero W's with a camera. I run raspistill in a loop and take an image around 4/minute. All of them hang up after anywhere from a few hours to a day or two. On the Pi 4, I stopped the camera script that I was collecting images, and it does not crash. If I catch it soon enough, I can SSH in and reboot, although it typically hangs on reboot anyway. Otherwise it will eventually stop responding to ping or anything.
This all started somewhere around the 5.10 update.
I have a couple of other Pi's with cameras that do not hang up, and I don't know what would be different with them. They were all updated about the same day to the 5.10 update, but a 3B and another Zero W do not have any issues with the camera. I've updated the troubled Pi's with rpi-update to try to fix, but the updates haven't made any difference.
sferlix
commented
3 years ago what camera are you using ? thanks francesco
Il mar 23 feb 2021, 22:08 zt4 notifications@github.com ha scritto:
I've got the same issue... one Pi 4 with a camera, two Pi Zero W's with a camera. I run raspistill in a loop and take an image around 4/minute. All of them hang up after anywhere from a few hours to a day or two. On the Pi 4, I stopped the camera script that I was collecting images, and it does not crash. If I catch it soon enough, I can SSH in and reboot, although it typically hangs on reboot anyway. Otherwise it will eventually stop responding to ping or anything.
This all started somewhere around the 5.10 update.
I have a couple of other Pi's with cameras that do not hang up, and I don't know what would be different with them. They were all updated about the same day to the 5.10 update, but a 3B and another Zero W do not have any issues with the camera. I've updated the troubled Pi's with rpi-update to try to fix, but the updates haven't made any difference.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Hexxeh/rpi-firmware/issues/255#issuecomment-784513722, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWXGV4N3G7ZBET3WPHM6PTTAQKMNANCNFSM4XWIY56Q .
sferlix
commented
3 years ago I am running another test. on a new Pi4, new SD, i have installed a Raspberrian Lite (no desktop). the very same script is now running since 1,5 days with no issues, collecting images every 2 minutes. I will keep testing for more days.
important to know: I did not run any upgrade, while, in the former Pi4, I upgraded the firmware.
Yes, it's a different hardware and a different OS (no desktop). but I have the impression that the errors started right after the firmware upgrade...
who knows.. i hope to pass the tests... francesco
Il mar 23 feb 2021, 22:10 Francesco Sferlazza sferlazza@gmail.com ha scritto:
what camera are you using ? thanks francesco
Il mar 23 feb 2021, 22:08 zt4 notifications@github.com ha scritto:
I've got the same issue... one Pi 4 with a camera, two Pi Zero W's with a camera. I run raspistill in a loop and take an image around 4/minute. All of them hang up after anywhere from a few hours to a day or two. On the Pi 4, I stopped the camera script that I was collecting images, and it does not crash. If I catch it soon enough, I can SSH in and reboot, although it typically hangs on reboot anyway. Otherwise it will eventually stop responding to ping or anything.
This all started somewhere around the 5.10 update.
I have a couple of other Pi's with cameras that do not hang up, and I don't know what would be different with them. They were all updated about the same day to the 5.10 update, but a 3B and another Zero W do not have any issues with the camera. I've updated the troubled Pi's with rpi-update to try to fix, but the updates haven't made any difference.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Hexxeh/rpi-firmware/issues/255#issuecomment-784513722, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWXGV4N3G7ZBET3WPHM6PTTAQKMNANCNFSM4XWIY56Q .
zt4
commented
3 years ago I'm using:
Official camera v2 on the two Pi Zero's (locks up). Official camera v2 on two Pi 3B's (works fine). Official camera v2 on a Pi 3B+ (works fine). Waveshare fisheye camera (with I think are just v1 with a different lens) on a Pi4 (locks up). Waveshare fisheye camera on a Pi Zero (works fine).
sferlix
commented
3 years ago I have the same ìssue with V2 Camera and HQ Camera as well on the Pi4 (upgraded firmware and Raspbian desktop)
Now testing with HQ Camera, new Pi4 (no upgraded firmare and Raspbian Lite, same cables). As said, no issues.
thanks francesco
Il mar 23 feb 2021, 22:19 zt4 notifications@github.com ha scritto:
I'm using:
Official camera v2 on the two Pi Zero's (locks up). Official camera v2 on two Pi 3B's (works fine). Official camera v2 on a Pi 3B+ (works fine). Waveshare fisheye camera (with I think are just v1 with a different lens) on a Pi4 (locks up). Waveshare fisheye camera on a Pi Zero (works fine).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Hexxeh/rpi-firmware/issues/255#issuecomment-784519829, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWXGVYJZ4CFBJVKSMMMWHDTAQLVNANCNFSM4XWIY56Q .
sferlix
commented
3 years ago see last message
After some hours, randomly, the PI4 becomes unresponsive. local mouse and keyboard not responding. SSH and VNC no longer available. PING still responds.
All software and firmware updated. any help really appreciated
thanks frank
This is the log: