From: Steven J Abner <pheonix.sja@att.net>
To: linux-kernel@vger.kernel.org
Cc: Ilkka Prusi <ilkka.prusi@pp.inet.fi>
Subject: Re: amd apu crashes
Date: Wed, 09 Feb 2022 06:30:37 -0500 [thread overview]
Message-ID: <1644406237.27630.0@smtp.mail.att.net> (raw)
In-Reply-To: 1644406237.27630.0.ref@smtp.mail.att.net
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On several crashes, it goes black, no log, than screen as was, no
computer activity(no keyboard, nor mouse, but power to keyboard
lighting), just allowed reset or power button. The triple threat was
total blackout, and on destroyed drive, I think only power button,
maybe reset didn't work??? So no kernel panic screen or efi shell if
that's the question? I do have a snapshot of a case that didn't blink
out monitor, and possibly no freeze but restarted out of what might be
next. Note: was kernel 5.15 kernel, during picture, and the destruction
of drive. Prior non-issue kernel I'm thinking was 5.10? I assumed first
triple threat was btrfs, 3 blinks for destroying drive data and its
backups, and when I took this shot was reconstruction of older projects
and data, but felt wasn't kernel but questioning gtk incorrect use of
graphics. I also can't recall ever an issue under 5.10, It just ran!
(minor annoyances with some programs). Possibly related, now that I
think about but not looked into, Kodi crashes more frequently and was
running on a couple kernel freezes.
Steve
[-- Attachment #2: Screenshot from 2021-12-04 06.41.19.png --]
[-- Type: image/png, Size: 58388 bytes --]
next parent reply other threads:[~2022-02-09 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1644406237.27630.0.ref@smtp.mail.att.net>
2022-02-09 11:30 ` Steven J Abner [this message]
[not found] <1644355058.23272.0.ref@smtp.mail.att.net>
2022-02-08 21:17 ` amd apu crashes Steven J Abner
2022-02-09 8:31 ` Ilkka Prusi
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=1644406237.27630.0@smtp.mail.att.net \
--to=pheonix.sja@att.net \
--cc=ilkka.prusi@pp.inet.fi \
--cc=linux-kernel@vger.kernel.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