public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Troubshooting AMD Radeon Vega system freeze
Date: Sun, 26 Jan 2025 21:43:12 +0000	[thread overview]
Message-ID: <4628214.LvFx2qVVIh@rogueboard> (raw)
In-Reply-To: <vn65bh$tbo$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]

On Sunday 26 January 2025 20:18:57 Greenwich Mean Time Grant Edwards wrote:
> 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

I have an older AMD system running a wayland desktop, which locks up if I 
update mesa/xorg in the background and do not restart/reboot after it is done.  
It tends to lock up with Firefox when moving its window between monitors, or 
resizing windows in general.  It feels a bit random when it may decide to 
trigger a freeze, but only common denominator is mesa & xorg drivers updates 
which are not followed through with restarting the session or rebooting the 
system.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-01-26 21:44 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   ` [gentoo-user] " Grant Edwards
2025-01-26 21:43     ` Michael [this message]
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=4628214.LvFx2qVVIh@rogueboard \
    --to=confabulate@kintzios.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