printf("%s", name);
@akunohana@piefed.blahaj.zone
Fëanor was a douchebag. The search for human connection doesn’t have a predefined conclusion. - pronell@lemmy.world Live in authenticity. Sharing is caring, censorship is lame. Praying for you 🕯️ O Great Mita 💝
piefed.blahaj.zone
Random reboot
Linux: Arch Linux 7.0.12
Graphical env: dwm on X
CPU: AMD Ryzen 7 5700G
MOBO: ASUS B550 TUF GAMING PRO
BIOS (at the time of unexpected reboot): 3634
Other than panic reboots (panic reboots are turned off) and reboots forced by the CPU on insufficient voltage (the CPU is never taxed, albeit undervolted with minus 30 on all cores in PBO), have you ever experienced random and unexpected reboots? The other day, I noticed that one of my servers - serving only torrent uploads, an i2p router, a Snowflake proxy and an sshfs connection for media consumption - had rebooted for seemingly no reason.
The journalctl logs show two messages just prior to the reboot in question that I do not understand, except for them being related to the NIC?
kernel: r8169 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE FAULT domain=0x000c address=0xa0fe1000]
kernel: r8169 0000:06:00.0 enp6s0: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out 5354 ms
Also, dmesg shows no logs - certainly no error related ones - around the time, or even in the days surrounding, the unexpected reboot.
My only guess is that there may have been some kind of firmware related instability - 3634 being a beta release and all - and since there is no communication between firmware and OS post boot (?), Linux reports no reboot related error and the journalctl messages above are actually unrelated to the reboot, or at most, just symptoms of the firmware induced failure. No idea… I have since upgraded the firmware to 3636.
Please advise. 😊
