Crashing regularly after 10 mins

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
Ian
Posts: 11
Joined: Thu Feb 28, 2019 12:45 pm

Crashing regularly after 10 mins

Post by Ian »

Unfortunately for some reason my pi keeps crashing regularly.
I'm running on the latest version, a stable power supply and switched on option 2 in the logs, but as it crashes after 10 mins I take it that the logs won't get written to disk.

I had HTOP running to see if anything funny is going on, but there's not a lot info as to why it's crashing.

What else could I "switch on" to determine why it's crashing.

Thanks
Ian
Last edited by Ian on Sun Mar 31, 2019 9:16 pm, edited 1 time in total.
User avatar
MichaIng
Site Admin
Posts: 2336
Joined: Sat Nov 18, 2017 6:21 pm

Re: Crashing regularly after 10 mins

Post by MichaIng »

Many thanks for your report.

Please check: dmesg
Especially look for red lines indicating kernel errors and stuff about I/O errors or low voltage warnings. Do you have any USB device attached?

To have persistent logs I would choose logging mode "none" (so disable RAMlog) and then do: mkdir /var/log/journal
With this system logs are written persistent to disk. After crash you can access them via journalctl and inspect the logs around the time of the crash.
Ian
Posts: 11
Joined: Thu Feb 28, 2019 12:45 pm

Re: Crashing regularly after 10 mins

Post by Ian »

Thanks for your quick reply.

I've just got this from dmesg:

[ 5.108933] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 5.109185] usbcore: registered new interface driver brcmfmac
[ 5.367187] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[ 5.367945] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14
[ 5.456196] brcmfmac: power management disabled
[ 7.998974] brcmfmac: power management disabled
[ 8.283146] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 8.283308] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.339623] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8.339637] brcmfmac: power management disabled
[ 8.434882] FS-Cache: Netfs 'cifs' registered for caching
[ 8.437813] Key type cifs.spnego registered
[ 8.437850] Key type cifs.idmap registered
[ 8.466923] CIFS VFS: Error connecting to socket. Aborting operation.
[ 8.466951] CIFS VFS: cifs_mount failed w/return code = -101
[ 9.606304] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 10.391689] Under-voltage detected! (0x00050005)
[ 16.631600] Voltage normalised (0x00000000)
[ 39.241060] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
[ 135.468410] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 135.617031] NFSD: starting 90-second grace period (net 80c7acc0)
[ 139.699103] random: crng init done
[ 139.699113] random: 7 urandom warning(s) missed due to ratelimiting
[ 141.431767] Under-voltage detected! (0x00050005)
[ 151.831793] Voltage normalised (0x00000000)
[ 249.591600] Under-voltage detected! (0x00050005)
[ 255.831585] Voltage normalised (0x00000000)
[ 370.231587] Under-voltage detected! (0x00050005)
[ 374.391528] Voltage normalised (0x00000000)
[ 488.791655] Under-voltage detected! (0x00050005)
[ 495.031577] Voltage normalised (0x00000000)
[ 609.431639] Under-voltage detected! (0x00050005)
[ 615.671595] Voltage normalised (0x00000000)
[ 730.071605] Under-voltage detected! (0x00050005)
[ 734.231680] Voltage normalised (0x00000000)
[ 850.711624] Under-voltage detected! (0x00050005)
[ 854.871593] Voltage normalised (0x00000000)
[ 969.271568] Under-voltage detected! (0x00050005)
[ 975.511572] Voltage normalised (0x00000000)

Seems like there is an under voltage problem, it was running ok on the same source for some time.
Could there be a software instance causing this?

I don't have a USB device attached.

In the mean time I'll try a dedicated 5v source.
Ian
Posts: 11
Joined: Thu Feb 28, 2019 12:45 pm

Re: Crashing regularly after 10 mins

Post by Ian »

Here is also some warnings:

0.519239] Core Release: 2.80a
[ 0.519342] Setting default values for core params
[ 0.519508] Finished setting default values for core params
[ 0.719929] Using Buffer DMA mode
[ 0.720032] Periodic Transfer Interrupt Enhancement - disabled
[ 0.720195] Multiprocessor Interrupt Enhancement - disabled
[ 0.720351] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 0.720483] Dedicated Tx FIFOs mode
[ 0.720973] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbb904000 dma = 0xfb904000 len=9024
[ 0.721263] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[ 0.721920] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805ed94c
[ 0.722094] WARN::hcd_init_fiq:460: FIQ ASM at 0x805edcb4 length 36
[ 0.722275] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
[ 0.730352] Init: Port Power? op_state=1
[ 0.737734] Init: Power Port (0)
[ 1.017353] Indeed it is in host mode hprt0 = 00021501
[ 1.185840] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.194778] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.203623] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.213658] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.245613] Indeed it is in host mode hprt0 = 00001101
[ 1.373086] mmc0: host does not support reading read-only switch, assuming write-enable
[ 2.706470] systemd[1]: apt-daily.timer: Cannot add dependency job, ignoring: Unit apt-daily.timer is masked.
[ 2.715257] systemd[1]: apt-daily-upgrade.timer: Cannot add dependency job, ignoring: Unit apt-daily-upgrade.timer is masked.
[ 2.724995] systemd[1]: getty-static.service: Cannot add dependency job, ignoring: Unit getty-static.service is masked.
[ 4.283819] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
User avatar
MichaIng
Site Admin
Posts: 2336
Joined: Sat Nov 18, 2017 6:21 pm

Re: Crashing regularly after 10 mins

Post by MichaIng »

Some of the warnings in your second paste are expected when running the RPi (it's an RPi, right?) with 16M GPU memory as some video features of the chip are disabled then.

So indeed the under voltage is the problem. Do you use WiFi? Otherwise you could disable the internal WiFi device (via dietpi-config > Network Options: Adapters) to save power there.

But as long as you have no USB device attached, with a stable PSU there should be no voltage issues. Did you enable some overclocking profile? Software can just use the features of the board e.g. load the CPU but even with full load this should not lead to voltage issues.

What PSU do you use and which RPi version is it? RPi3 or RPi3+? Assure that the PSU delivers sufficient current (2.5A at least for RPi3(+)). Also the quality is important. E.g. some mobile phone charger will not work in some cases since it is not made to provide 100% reliable 5V but might have some ups and downs. Good quality PSUs made to power SBCs are made to deliver the voltage with less fluctuation.
Post Reply