Linux

48051 readers

838 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Troubleshooting errorless system hang on kernel 6.7 (social.rocketsfall.net)

submitted 9 months ago* (last edited 9 months ago) by 0x0@social.rocketsfall.net to c/linux@lemmy.ml

11 comments fedilink hide all child comments

As of Linux 6.7 I'm getting hard freezes that require a power cut to reset (sysrq doesn't work.) Happens at both idle and load anywhere from 5 minutes in to an hour. Running journalctl --follow and dmesg -w (both as root) reveal nothing at the time of the crash. Kernel version 6.6 continues to be 100% stable.

System:

Distro/Kernel: Arch Linux 6.7.arch3-1
CPU: AMD Ryzen 5 2600X
GPU: AMD RX580 8GB via AMDGPU
RAM: Some configuration of 16GB at 2667 MT/s.
WM: SwayWM

I'm unsure how to go about properly reporting a bug if no errors are being generated.

Any advice?

I'm not alone on this apparently (warning, it's reddit.)

you are viewing a single comment's thread
view the rest of the comments

[–] SheeEttin@programming.dev 2 points 9 months ago (1 children)

Start eliminating hardware. Also try memtest86+.

[–] 0x0@social.rocketsfall.net 1 points 9 months ago

This will be my last resort mostly because I'm fairly certain it's a kernel issue, but yes, I've never ran an extended memtest on this build and should probably let it run overnight at some point just to make sure.