From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Troubshooting AMD Radeon Vega system freeze
Date: Sun, 26 Jan 2025 20:18:57 -0000 (UTC) [thread overview]
Message-ID: <vn65bh$tbo$1@ciao.gmane.io> (raw)
In-Reply-To: 5014ced2-6981-4e52-adc5-ae552f88142b@gmail.com
On 2025-01-26, Daniel Frey <djqfrey@gmail.com> wrote:
> I had a problem with two of my Ryzen systems that exhibited this
> behaviour. One has a G processor, the other doesn't
>
> Apparently Ryzen processors have an idle bug that locks up the
> system in this way. The bugs manifests randomly when the CPU is
> idle. For me, if I left the PC on overnight it would always be hung
> up the next morning. It would also trigger if I started a long
> emerge and forgot about it - it would idle enough it would hang.
And that only hung user-space stuff?
I can still ping mine when it's frozen, and the SysRq key works
(except for commands to do with the framebuffer console). Ssh doesn't
work and Ctrl-Alt-Fx doesn't work.
> I had to update the BIOS on both machines, then change the "Power Supply
> Idle Control" to "Typical Current Idle". Any other setting and the bug
> manifests. Note this setting is for Asus motherboards; I would imagine
> other manufacturers have a similar setting but it may be named differently.
>
> I did test it, I left both my PCs on for over 48 hours and no lockup.
I don't think this is the same. My machine never locked up when idle.
It was always when doing something like resizing an X11 window. I
could let it sit idle for days (either at the console prompt or with
X11 screen-saver active and a blanked screen). I could do anything I
wanted remotely via ssh. It only seemed to lock up when I was doing
something in X11. It didn't have to be _much_ in X11 (didn't need to
be rendering video or 3D gaming). Just working with xemacs and xterms
seemed to be enough (though I probably had a Thunderbird window
sitting idle/iconified and a chrome window showing some
documentation).
Yesterday I downgraded mesa from 24.3.3 to 24.2.8, and it hasn't
frozen since -- though I also haven't been using it a lot since the
downgrade. If make it through a day of work tomorrow without a
lockup, then I'm going to blame mesa. During a normal work day last
week it would usually freeze a half-dozen times.
--
Grant
next prev parent reply other threads:[~2025-01-26 20:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 19:13 [gentoo-user] Troubshooting AMD Radeon Vega system freeze Grant Edwards
2025-01-25 19:39 ` [gentoo-user] " Grant Edwards
2025-01-25 21:16 ` Dale
2025-01-26 3:16 ` Grant Edwards
2025-01-26 4:25 ` Dale
2025-01-27 23:03 ` [gentoo-user] Re: Troubshooting AMD Radeon Vega system freeze [SOLVED] Grant Edwards
2025-01-27 23:29 ` Grant Edwards
2025-01-26 17:37 ` [gentoo-user] Troubshooting AMD Radeon Vega system freeze Daniel Frey
2025-01-26 20:18 ` Grant Edwards [this message]
2025-01-26 21:43 ` [gentoo-user] " Michael
2025-01-28 15:04 ` Daniel Frey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='vn65bh$tbo$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox