From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Troubshooting AMD Radeon Vega system freeze
Date: Sat, 25 Jan 2025 22:25:01 -0600 [thread overview]
Message-ID: <26584d9c-1858-0652-cdc3-7faaa3eb630e@gmail.com> (raw)
In-Reply-To: <vn49eq$16mb$1@ciao.gmane.io>
Grant Edwards wrote:
> On 2025-01-25, Dale <rdalek1967@gmail.com> wrote:
>> Grant Edwards wrote:
>>> On 2025-01-25, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>>>> Starting about a week ago, my AMD system (AMD Ryzen 5 3400G with
>>>> Radeon Vega Graphics) has been freezing up multiple times per day --
>>>> always when in active use with X11. Before that, it had been reliable
>>>> since assembled (about 5 years ago).
>>>>
>>>> Ctrl-Alt-Backspace does nothing
>>>> Ctrl-Alt-F1 does nothing
>> I've accidentally seen this ages ago and this may not be there anymore.
>> Isn't there some sort of output sent to ctrl alt F12? If so, that may
>> shed some sort of light. I think it is the same as messages or
>> something. I saw it once when scrolling through the consoles looking
>> for something else. I'm not real sure what I saw but looked like kernel
>> something.
> None of the other ctrl-alt-Fx keys work. I don't specifically remember
> trying ctrl-alt-F12, but I'll give that a go next time.
>
> I tried rolling back Xorg server, that didn't seem to help.
>
> Google has found reports of recent versions (24.3.x) of mesa being
> blamed for problems like this. I see in the logs that mesa got
> upgraded from 24.2.8 to 24.3.3 on the 20th. I've rolled that back, to
> see if that helps. I thought it started a little earlier than that,
> but my memory may be playing tricks on me: it's been a long week.
>
> I've been looking for a good document with some recommendations on how
> to use the various SysRq functions (in what sequence), but all I can
> ever find is just lists of the commands with very descriptions of
> each.
>
>
>
This is two links I found. Should help.
https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
https://linuxconfig.org/how-to-enable-all-sysrq-functions-on-linux
When I have a system to lock up and nothing else works, I remember it
this way. Reboot Even If System Utterly Broken. R - E - I - S - U -
B. Another trick, using the F option. If something is using a lot of
memory and making your system use swap which makes a system very slow,
just Alt Sysrq F to kill it. I've done that when Firefox gets really
hungry. I can't recall if you need to do the R option first for the F
option or not. It's been a while.
Dale
:-) :-)
next prev parent reply other threads:[~2025-01-26 4:26 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 [this message]
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
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=26584d9c-1858-0652-cdc3-7faaa3eb630e@gmail.com \
--to=rdalek1967@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