spontaneous reboots

mstrimel · 04-10-2022, 11:04 AM

I have a Fedora system on an AMD Ryzen 3 4350G with integrated graphics. I use the system for whole-house multimedia. Virtually since it was built the system does this thing where it spontaneously reboots, even while not being used (or while listening to music, for example). Also, when I wake it from sleep, it will immediately go back to sleep so that I have to log in twice to wake it up. Lazy computer!

I don't think the rebooting is a heat issue as I have a massive cooling tower and fan, and this happens during zero-demand activities. Neither behavior appears under Windows.

How should I begin troubleshooting these issues? My detailed specs are below.

Code:

mary@mythbox:~]$ sudo inxi --full
System:
  Host: mythbox Kernel: 5.16.18-100.fc34.x86_64 x86_64 bits: 64
    Desktop: Cinnamon 5.2.7 Distro: Fedora release 34 (Thirty Four)
Machine:
  Type: Desktop System: Gigabyte product: B550M DS3H AC v: N/A serial: N/A
  Mobo: Gigabyte model: B550M DS3H AC v: x.x serial: N/A
    BIOS: American Megatrends v: F10 date: 09/18/2020
CPU:
  Info: quad core model: AMD Ryzen 3 PRO 4350G with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 2 MiB
  Speed (MHz): avg: 2000 min/max: 1400/4104 cores: 1: 3800 2: 3800 3: 1400
    4: 1400 5: 1400 6: 1400 7: 1400 8: 1400
Graphics:
  Device-1: AMD Renoir driver: amdgpu v: kernel
  Display: server: X.Org v: 1.20.14 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1440x900~60Hz
  OpenGL:
    renderer: AMD RENOIR (DRM 3.44.0 5.16.18-100.fc34.x86_64 LLVM 12.0.1)
    v: 4.6 Mesa 21.1.8
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
  Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
  Device-3: ASUSTek Xonar SoundCard type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.16.18-100.fc34.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.40 running: yes
Network:
  Device-1: Intel Wireless-AC 9260 driver: iwlwifi
  IF: wlo1 state: up mac: 04:6c:59:b5:50:90
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp9s0 state: up speed: 100 Mbps duplex: full mac: 18:c0:4d:93:2e:67
  IF-ID-1: virbr0 state: down mac: 52:54:00:24:66:56
Bluetooth:
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb
  Report: bt-adapter ID: hci0 state: up address: 04:6C:59:B5:50:94
Drives:
  Local Storage: total: 2.27 TiB used: 904.4 GiB (38.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
    size: 465.76 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
    size: 931.51 GiB
  ID-3: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
Partition:
  ID-1: / size: 213.34 GiB used: 31.2 GiB (14.6%) fs: ext4
    dev: /dev/nvme0n1p7
  ID-2: /boot size: 1.73 GiB used: 301.4 MiB (17.0%) fs: ext4
    dev: /dev/nvme0n1p6
  ID-3: /home size: 483.34 GiB used: 88.45 GiB (18.3%) fs: ext4
    dev: /dev/nvme1n1p4
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 2 MiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 16.8 C mobo: N/A gpu: amdgpu temp: 29.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 402 Uptime: 21h 53m Memory: 15.09 GiB used: 4.52 GiB (30.0%)
  Shell: Bash inxi: 3.3.13

mrmazda · 04-10-2022, 06:29 PM

Random reboots are commonly hardware related, even if you can't replicate in Windows. Sometimes more RAM voltage is needed than is specified. Try in BIOS setup adding two increments increase of RAM voltage. If that works, good. If not, try another two steps. Just be aware that there's a limit.

Quote:

By default, DDR4 runs at 1.2v, while many memory module kits are rated to run at around 1.35v with XMP. Raise your voltage slowly until your system is stable; we recommend not going above 1.4v to be safe.

Source.

frankbell · 04-10-2022, 07:48 PM

Have you checked the log files?

It could that whatever triggers this happens too quickly to get logged, but it's certainly worth a look.

rclark · 04-10-2022, 09:14 PM

That bios is a little old (2020). Might want to check to see if there is a newer version out there. Sometimes just updating it will help too. Just a thought. This must be a store bought computer as I don't recall any 4350G's for sell at least at NewEgg. Hardware problems like this can be hard to find. Good luck.

mstrimel · 04-11-2022, 11:17 AM

Quote:

Originally Posted by mrmazda

Random reboots are commonly hardware related, even if you can't replicate in Windows. Sometimes more RAM voltage is needed than is specified. Try in BIOS setup adding two increments increase of RAM voltage. If that works, good. If not, try another two steps. Just be aware that there's a limit. Source.

I made this change in the BIOS, so i'm in a testing phase. So far no reboots.

Thanks everyone for your comments and suggestions. This was definitely a self-built machine; I got the CPU on e-bay (new in box). Thanks also for the tip about logs - I did not know that Fedora had a way to look at them in a GUI. I'm definitely going to check that out.

I'll need to research the BIOS upgrade. It took me a ton of time to set up the software on this machiine (I use MythTV as a personal DVR -- fun but labor intensive) so I want to make 100% sure not to break anything!

onebuck · 04-11-2022, 02:09 PM

Hi,

I really think a backup would be beneficial in case issues should arise. Recovery from problems can be troubles but when you have a backup then recovery is possible or even transition if needed. Your backup cycle will dictate how far back one might need to step. Even consider grandfathering a backup off site with a trusted person/vault so you can cycle through to that dated copy. You never know when a catastrophic event will occur.

Any time you make system changes a problem could stick it's head up!
Hope this helps.