-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Under-voltage detected on Raspberry Pi 3 #1142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It's far more likely that you have a marginal power supply - one that has either drifted in output voltage or a slight increase in current consumption on the Pi has caused the output voltage to droop. |
I am using the Stontronics psu for this. It is a 2.5A 5.1V psu and the same
is able to power another RPi3 with a different SD card at the throttled
voltages. No errors or warnings appearing there. I have tried removing all
deviations from standard yet the same behavior with this board + sd
combination. This happened after an rpi-update and I used
never_over_voltage=1 when I was trying something out. Unable to see why
this should brick the wifi proc.
Thanks for your help.
…On Tue, May 21, 2019, 6:02 PM P33M ***@***.***> wrote:
It's far more likely that you have a marginal power supply - one that has
either drifted in output voltage or a slight increase in current
consumption on the Pi has caused the output voltage to droop.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1142?email_source=notifications&email_token=AGD5LNGXN4HSSWOBURDCY73PWPCBPA5CNFSM4HOD57F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV3NBAQ#issuecomment-494325890>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGD5LNBR4J76CCXRRWE2SULPWPCBPANCNFSM4HOD57FQ>
.
|
If you think this coincided with an rpi-update, then can you revert to an earlier version of firmware and see if issue disappears? See: If you click on each commit the end of the url contains a git hash. Run |
Thanks for the suggestion @popcornmix. I reverted back to FW level corresponding to kernel 4.9.35 and as I suspected, the voltage warnings are gone and WIFI is back working. The SD (16GB SDHC) continues to be set to 25Mhz, despite the revised parameters and old FW, which was earlier able to operate at 100Mhz after throttling, prior to rpi-update. Will incrementally up the FW level and share the FW that breaks. |
That said, rpi-update to the latest FW on another RPi3 running with same psu has not introduced the under-voltage warnings or impacted WiFi proc the way it did on this board. And not sure how and why a hitherto working mSD at 100Mhz would downgrade to 25Mhz - not even run at the base HS of 50Mhz (default). Strange mentions in dmesg which were not reported earlier (prior to rpi-update, but now even after reverting to old FW, still being reported) [ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait Will report more as I find more. |
If you can identify the first firmware commit with the issue it may shed some light. |
Given there are over two years of FW upgrades available from our current level of 4.9.35, I binary folded and tried. Looks like the WIFI issue cropped from 4.19.23 onwards. The last recent stable version that I could run with WIFI not failing is 4.14.98. For the under-voltage issue, the under-voltage alerts in dmesg are not wrong - it appears only when I switch to 1A supply, goes away when I use 2.5A. So, this is a non-issue. For the WIFI issue, I initially thought the WIFI issue was related to an alert in red for brc43430 in dmesg, but that seems incorrect - there does not seem to be a correlation since the alert is present in 4.14.98 too but WIFI seems to be working, unlike the 4.19.23 where it did not work. I am finding it difficult to believe that no one else has hit this so far - no one upgraded to 4.19.23 (Feb 2019) and tried using WiFi on the RPi3 - that's very unlikely. For the mSD card issue - I'm still getting "[ 2.183115] mmc0: Problem switching card into high-speed mode!" after downgrading the FW for one 16GB SDHC card (Strontium UHS1) and consistently for all, even brand new, 64GB SDXC cards (Strontium UHS1) which was previously being recognized as high-speed and able to throttle to 100Mhz. Now, even after downgrading FW back to 4.9.35, it throws up this note in dmesg and able to start at basic speed and frequency of 25Mhz. Surprisingly, other 16/32GB SDHC cards and 128/256GB SDXC cards are able to throttle to 100Mhz and 90Mhz respectively. I can understand that something is gone in the one 16GB card unable to get throttled - may have just coincided with rpi-update, but all the brand new 64GB cards also not being recognized as high-speed on this one box which was FW upgraded is a cause of worry. For now, keeping all our boxes at 4.9.35 - as that has been stable for a long time. |
Guys, I'm also having what looks like low power issues. Updated everything, checked the cables, USB power supply output, new SD card but all I see is a sea of red. Primary issue is failure to recognise the USB ports even prior to booting the OS with screen error for all four USB ports. usb 1-1: device descriptor read/64, error -71 Finally managed to SSH and VNC into it as a head end. I think I need to revert back the RPI to an earlier vervion, but need some guidance there if this is the case. This is the mess I'm trying to decipher: pi@raspberrypi:~ $ dmesg Any advice appreciated or you think the HW is just screwed? Cheers. Ben. |
Closing this issue are original bug was due to an insufficient power supply. |
Recently I noticed the following in the startup log of my RPi3. It has coincided with rpi-update on it - hence, I am unsure as to what may have been the root cause of WiFi stopping to work, and under voltage warnings being reported, and SD card coming up at only 25Mhz.
(with following params in config.txt)
total_mem=1024
gpu_mem=64
arm_freq=1350
gpu_freq=500
core_freq=500
sdram_freq=500
sdram_schmoo=0x02000020
over_voltage=4
sdram_over_voltage=2
dtparam=sd_overclock=100
dmesg output lists the following
[ 149.911657] Under-voltage detected! (0x00050005)
[ 160.311690] Voltage normalised (0x00000000)
[ 166.551633] Under-voltage detected! (0x00050005)
[ 170.711658] Voltage normalised (0x00000000)
[ 310.071465] rpi_firmware_get_throttled: 6 callbacks suppressed
[ 310.071472] Under-voltage detected! (0x00050005)
[ 328.791509] Under-voltage detected! (0x00050005)
[ 343.351410] Under-voltage detected! (0x00050005)
[ 428.631334] rpi_firmware_get_throttled: 14 callbacks suppressed
[ 428.631341] Voltage normalised (0x00000000)
[ 457.751265] Voltage normalised (0x00000000)
[ 482.711234] Voltage normalised (0x00000000)
[ 611.671143] rpi_firmware_get_throttled: 16 callbacks suppressed
[ 611.671150] Under-voltage detected! (0x00050005)
[ 619.991053] Under-voltage detected! (0x00050005)
[ 628.311152] Under-voltage detected! (0x00050005)
[ 730.230915] rpi_firmware_get_throttled: 14 callbacks suppressed
[ 730.230921] Voltage normalised (0x00000000)
But more importantly, the WiFi proc is seeming to have trouble. Hostapd is failing to start.
[ 4.675790] usbcore: registered new interface driver uas
[ 4.725432] scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0016 PQ: 0 ANSI: 4
[ 4.727282] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[ 4.727299] sd 0:0:0:0: [sda] 0-byte physical blocks
[ 4.728139] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[ 4.728941] sd 0:0:0:0: [sda] Asking for cache data failed
[ 4.728957] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 4.736961] sd 0:0:0:0: [sda] Attached SCSI disk
[ 4.889297] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 4.913910] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 4.965735] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 4.979833] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 4.979864] cfg80211: failed to load regulatory.db
[ 5.052221] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 5.057618] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 5.057926] usbcore: registered new interface driver brcmfmac
[ 5.245972] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 5.245985] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 5.249556] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 5.249568] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 5.252283] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 5.252385] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 5.253142] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 5.253842] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 5.253850] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 5.593679] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
Could setting never_over_voltage=1 may have caused an irreversible change of this nature?
Any pointers appreciated. Thx.
Rohit
The text was updated successfully, but these errors were encountered: