Since Raspbian Buster kernel in update 2020-02-05, many RPi4 users cannot reboot reliably & other stability issues #1333
Comments
carver7
changed the title
|
The rpi-update was to check if the following one was the issue for raspivid specifically, not a general solution. |
|
could be due to gpu_freq => 500, since only 500 MHz are allowed, with the entry hdmi_enable_4kp60 = 1 the frequency is increased to 550 MHz. In the past, 750 MHz was possible, which was also possible without problems with proper cooling. |
|
The apt firmware has been updated today. Can you test if it resolves your issues? |
|
-what exactly should I try? |
|
great work, runs again with arm_freq = 2147/2294 and also starts with the parameter gpu_freq = 750 MHz. I will observe the stability over the next few days and give a feedback again. |
|
Raspivid makes empty files since last apt-get upgrade. What happened? |
|
This should be fixed in the latest release. When did you last do an apt full-upgrade? |
In the beginning of February. I'll make it this evening. :) |
|
Thank you! |
|
Can one of the engineers explain what compromise means in f4b5869? Is there now a limit on how high or low it can go or is it just some internal safety for stock clocks? |
|
The limit is in the maximum frequency of PLLA, which is now capped at 3GHz (the value used before the recent overclock changes). |
|
Well, but what does that mean practically?No change to what can be set in config.txt? |
Just tried this and raspivid seem to work fine after an apt update/apt full-upgrade - can you make sure you are running the latest stuff please. |
|
I've fresh-installed Raspbian Desktop on 2 RPi4's using the Sep 2019 general installer image (not the Feb 2020 installer image) and updated to the present moment (using only the documentation's recommended method of sudo apt update && sudo apt full-upgrade). I copied the rootfs to a separately powered USB-HDD drive, which is plugged into one of the USB 2.0 ports (haven't tried the USB 3.0 ports) from which I'm booting, with No over_voltage=X added to /boot/config.txt This was done running headless over ssh locally. I no longer experience any of the issues that I originally inquired about, and the logs displayed by dmesg look normal too. I haven't tried Raspivid, so I don't know if that is considered resolved or not. But with respect to the issues I raised, these appear to be resolved (at least from my limited n=2 sample size view), so I'm good with the Raspberry Pi team closing this issue whenever it deems it best to do so. @profi200 do you have an update on Raspivid? |
|
Raspivid works allready. Thanks.
carver7 <notifications@github.com> ezt írta (időpont: 2020. febr. 22., Szo
3:31):
… I've fresh-installed Raspbian Desktop on 2 RPi4's using the Sep 2019
general installer image (not the Feb 2020 installer image) and updated to
the present moment (using only the documentation's recommended method of
sudo apt update && sudo apt full-upgrade).
I copied the rootfs to a separately powered USB-HDD drive, which is
plugged into one of the USB 2.0 ports (haven't tried the USB 3.0 ports)
from which I'm booting, with No over_voltage=X added to /boot/config.txt
I did add rootdelay=5 to the /root/cmdline.txt as a precaution (this did
not fix the rebooting issues I was experiencing before though), but that's
it.
This was done running headless over ssh locally.
I no longer experience any of the issues that I originally inquired about,
and the logs displayed by dmesg look normal too.
I haven't tried Raspivid, so I don't know if that is considered resolved
or not. But with respect to the issues I raised, these appear to be
resolved (at least from my limited n=2 sample size view), so I'm good with
the Raspberry Pi team closing this issue whenever it deems it best to do so.
@profi200 <https://github.com/profi200> do you have an update on Raspivid?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1333?email_source=notifications&email_token=AD4UT6XV5NXVI4HXXNNUL7DRECFBDA5CNFSM4KSXX6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMUUS4I#issuecomment-589908337>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4UT6S2RGBN6SGNKJUK7WTRECFBDANCNFSM4KSXX6QQ>
.
|
|
@carver7 |
|
My thoughts are that this issue has now been fixed, so this issue will be closed within 30 days unless further interactions are posted. If you wish this issue to remain open, please add a comment. A closed issue may be reopened if requested. |
JamesH65
added
the
Close within 30 days
|
My raspivid works now. Thanks! Regards Zoltan
James Hughes <notifications@github.com> ezt írta (időpont: 2020. febr. 24.,
H, 16:36):
… My thoughts are that this issue has now been fixed, so this issue will be
closed within 30 days unless further interactions are posted. If you wish
this issue to remain open, please add a comment. A closed issue may be
reopened if requested.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1333?email_source=notifications&email_token=AD4UT6S4OFZM4MUP6RVLDOLREPSQPA5CNFSM4KSXX6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMYJZAA#issuecomment-590388352>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4UT6QW6LENWFM4PGPBMS3REPSQPANCNFSM4KSXX6QQ>
.
|
|
Hi! I did nothing before. Regards, |
|
I am having the reboot problem if I have a USB 3.0 hub attached lsusb A recent update broke reboot with attached USB 3.0 hub - disconnect the hub it works. Power observations |
|
Other details |
|
I'm seeing previously reported issue with raspivid - but not sure what information you need. RPi4 with 4GB Using powered USB-3.0 4-port hub (NXT Tech from Staples) If I run command $raspivid -cd MJPEG -w 1920 -h 1080 -fps 30 -o output.mjpg I cannot output to ffmpeg using stdout "-o -" either - same messages and nothing gets sent Didn't think I'd need the emergency update with latest stable $ vcgencmd version $uname -a $ sudo rpi-eeprom-update |
|
What happens if you set the output file to be H264 rather than MJPEG? |
Please confirm you are using the standard 32bit Raspberry Pi OS. MMAL is not currently supported on the 64bit OS |
|
I'm using Raspbian 64bit OS - does that mean raspivid will not work? Or can I avoid raspivid and try streaming directly from ffmpeg using H264? |
Correct. |
|
Okay thanks. I'll look at V4L2 in meantime - or are you saying I would need a USB webcam? Pi Camera is out of question for now? |
|
I see this is marked to be closed soon, but I figured I'd give it a bump with some info I have on these issues. The main gist is that attempting to use the HQ camera module in 1080p mode to make the Pi 4B appear as a UVC webcam causes issues described in this issue, such as not being able t shut down the device properly. The other issues also include either not getting any output from the camera module at all, or getting output for a brief period of time (1 to 5 minutes) before the camera output crashes despite the app that is used reporting that everything is fine. |
Please investigate the growing number of reports written by mostly RPi4 users that relate to a number of consistently reported issues.
Particularly, since Raspbian Buster kernel in updated in release 2020-02-05, variations of reboot commands lead to shutdowns instead.
Instability of RPi4s has been increasing with each incremental update released and this has accelerated since general release 2020-02-05
There are also problems being reported with the simple use of 'sudo' or being logged in as root user for using raspi-config
Problem 7 led act raspberry pi4 with sudo reboot
RPi4 shutdown -r not restarting up
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=196778&p=1609435#p1609681
From https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=196778&p=1609435#p1609681 :
It appears there are several problems with the 2020-02-05 Raspbian Buster images (and the updates issued just prior to these images).
Until the Raspberry Pi folks sort it all out, the solution is to simply run:
sudo rpi-update 993f475The text was updated successfully, but these errors were encountered: