Error logs when pi stack

winterelf

Hi, i have
retropie 4.7.19
pi 4
pi booted form usb 3 Sandisk 480 GB SSD (https://www.ebay.com/itm/265387527916?hash=item3dca544eec:g:XwcAAOSwCAZhgLbz)

Pi keep stuck alternately, (once a day) or so. The thing is, it doesn't happened during a game, it just stack when i dont use it and after a couple of hours i come back to find out nothing is moving , it just happened in Dr station randomly stack and i must unplug the pi to reboot.

Any idea where can i find logs to give me a clue after i reboot ?

my config.txt is:

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
arm_freq=2000
over_voltage=6

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
"/boot/config.txt" [readonly] 68 lines, 898964 characters
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1

mitu

You mean your Pi is 'stuck' ?
First, please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.
Second, did you overclock your Pi ? If so, please remove the overclock settings and re-try to see if the issue still appears.

winterelf

@mitu hi, I updated my original post message

mitu

As I said, remove the overclock and see if you get a stable system.

winterelf

@mitu I tested the same image on two different pi4, and in both of them it gets stack although when I'm using different pi image that also overclocked the same way, it doesn't do any issue. :/

BTW the pi gets stack in Emulation station, not inside a game.

ByteThis

@winterelf Not every Pi board is the same. They differ in what they can handle for supersizing ( Overclock and performance).

BuZz

@winterelf then it sounds like your overclock is unstable. Another system/os may not have the same kernel, or tasks running.

Remove the overclock and test without.

winterelf

@buzz it's being days now without overclocking, seems like it is working fine. I guess the overclock is the issue.

should I use less values for: arm_freq and over_voltage?

dankcushions

@winterelf only you can establish that with your own tests. every pi is different.

although i would question the benefit of overclocking CPU for retropie emulation. the pi4's cpu is decent and almost never the bottleneck.

winterelf

@dankcushions I have dreamcast/3do/ps1. god of war for example can improve dramatically when overclocking. although it missed the point of retro