PI 4 becomes unresponsive #255
Comments
|
What is typically running at the time? It looks like a camera app of some kind. You could try adding |
|
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:
is this normal ? |
|
Update:
any help ? |
|
That's just telling you that the firmware stopped responding - it's just an indication that something went wrong. As I said above:
|
|
sure ! I was lucky because the error now showed up quickly, after hard reboot, without having to wait for hours. please find it below. I also have this that sounds interesting (I hope): |
|
Is that with the camera attached? The firmware says it can't find it, which isn't a good sign. |
|
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).. Please note that when the Pi becomes unresponsive, I have to switch off. Could it be an issue with the board ? Maybe I could return the board, as I bought it on Amazon 1 week 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 |
|
system is powered by power cable (the one provided by the case manufacturer) sorry, it was gpu_mem = 512 thanks |
|
Ciao, while using the camera via command line (no crontab) to detect optimal parameters, I got into this: ERROR: <class 'picamera.exc.PiCameraRuntimeError'> **"No data recevied from sensor. Check all connections, "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 So it seems you are rigth. But cables are well connected. Issue happens with all cameras I have tried. thanks EDIT: |
|
Again after 20ish hours. Here are the logs (many of these messages) `7829.036: imx477_open: read id 1143 succes 0!����������������������������������������������������������������������������������������������� ����pi@raspberrypi:/var/log$ sudo vcdbg log assert������������������������������������������������������������������������������������������������� Looks the same... all of the sudden, the camera seems to disappear.. |
|
Is that the same Pi 4 or a different one? |
|
same Pi. |
|
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 Package Version cycler 0.10.0 (venv) $ cat test.py from picamera.array import PiRGBArray print("Code run started") camera = PiCamera() camera.start_preview() raw_capture = PiRGBArray(camera) print("Code run completed.") (venv) $ python test.py During handling of the above exception, another exception occurred: Traceback (most recent call last): 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 ]------------ 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+ |
|
PS to comment above: camera confirmed working via raspistill command. |
|
PPS. I forgot to mention that the above occurs when I am remotely connecting to the Pi using VNC (with Direct Capture Enabled). |
|
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. |
|
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
<#255 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWXGV4N3G7ZBET3WPHM6PTTAQKMNANCNFSM4XWIY56Q>
.
|
|
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 ***@***.***> 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
> <#255 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AKWXGV4N3G7ZBET3WPHM6PTTAQKMNANCNFSM4XWIY56Q>
> .
>
|
|
I'm using: Official camera v2 on the two Pi Zero's (locks up). |
|
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
<#255 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWXGVYJZ4CFBJVKSMMMWHDTAQLVNANCNFSM4XWIY56Q>
.
|
|
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:
The text was updated successfully, but these errors were encountered: