this post was submitted on 20 Jun 2026
8 points (100.0% liked)

Linux

65917 readers
577 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago
MODERATORS
8
Random reboot (piefed.blahaj.zone)
submitted 2 days ago* (last edited 1 day ago) by akunohana@piefed.blahaj.zone to c/linux@lemmy.ml
 
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. 😊

top 2 comments
sorted by: hot top controversial new old
[–] stuner@lemmy.world 3 points 1 day ago

the CPU is never taxed, albeit undervolted with minus 30 on all cores in PBO

In case of an unstable system, the first thing I would do is disable all overclocks (including PBO, EXPO, undervolt, ...)

[–] non_burglar@lemmy.world 1 points 1 day ago

Page faults are memory-related and random reboots are either CPU or memory related, typically. I would run a memtest.