All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204241] amdgpu fails to resume from suspend
Date: Thu, 13 Apr 2023 20:11:20 +0000	[thread overview]
Message-ID: <bug-204241-2300-wSVAbJklHX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204241-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204241

TheRinger (tyrell.rutledge@icloud.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tyrell.rutledge@icloud.com

--- Comment #78 from TheRinger (tyrell.rutledge@icloud.com) ---
After this happened to me on Debian I started digging to find the source as it
came with a payload which ultimately flashed my bios after flashing my wireless
card’s firmware. I found two files that were modified from the original
installation which may have been injected as the source hash is different.
Researching further I’ve found some interesting comments about how this is done
by manipulating Systemd after resuming from hibernation, and pulling memory
back from the swap that was modified. The rabbit hole goes further as it then
returns from sleeping after modifying the library’s that control fonts and
their storage. You browse Google and your search’s contain websites with web
fonts. In These fonts there is strange emojis and and symbols which at first
seem like poorly designed icons and graphic s but actually contain raw code
that is downloaded to your cache. At some point there is another part that goes
in and assembles these code blocks to copy your .home/user/.ssh files because
of weak user land file and directory attributes. Anyway this goes into on as
you can imagine how this only continues to work. When this happens or after you
restart because the computer doesn’t return from sleep. You end up with
modifications to your bios, graphics, hard drive, firmware and anything else
that it can possibly find to stay present. Your gparted code will contain code
blocks that that swap out code from the end of your hard drive to the start.
You will need to start from scratch by clearing cmos then uploading new
firmware and zeroing out hard drives. It’s a huge headache. It may only get so
far and so you may never end up downloading the cached fonts or some other step
it needs and will think it’s just a glitch. Check your known hosts folder in
your ssh directory also compare hashes to original source code . I switched to
Slackware despite enjoying the simplicity of package management years ago as
its appeal to me was it didn’t contain Systemd, recently I decided to try a
mainline distro again only to discover this gem. 

The library files among others but notable only because the were in the
original initramfs were libfribidi.o and libgraphite2.so

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2023-04-13 20:11 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20  9:50 [Bug 204241] New: amdgpu fails to resume from suspend bugzilla-daemon
2019-07-20  9:50 ` [Bug 204241] " bugzilla-daemon
2019-08-08 20:13 ` bugzilla-daemon
2019-08-08 20:22 ` bugzilla-daemon
2019-08-08 21:02 ` bugzilla-daemon
2019-08-14 19:29 ` bugzilla-daemon
2019-08-14 19:38 ` bugzilla-daemon
2019-08-14 19:39 ` bugzilla-daemon
2019-08-14 19:39 ` bugzilla-daemon
2019-08-14 21:04 ` bugzilla-daemon
2019-08-15 20:55 ` bugzilla-daemon
2019-08-19 13:35 ` bugzilla-daemon
2019-09-03 18:56 ` bugzilla-daemon
2019-09-21 18:31 ` bugzilla-daemon
2019-10-05  0:08 ` bugzilla-daemon
2019-10-05 10:35 ` bugzilla-daemon
2019-10-07 10:13 ` bugzilla-daemon
2019-10-07 18:10 ` bugzilla-daemon
2019-10-08  7:56 ` bugzilla-daemon
2019-10-08  9:40 ` bugzilla-daemon
2019-10-11 18:33 ` bugzilla-daemon
2019-10-11 18:37 ` bugzilla-daemon
2019-10-11 20:47 ` bugzilla-daemon
2019-10-11 20:48 ` bugzilla-daemon
2019-10-12 10:37 ` bugzilla-daemon
2019-10-12 16:25 ` bugzilla-daemon
2019-10-12 18:35 ` bugzilla-daemon
2019-10-12 20:47 ` bugzilla-daemon
2019-10-13 10:47 ` bugzilla-daemon
2019-10-15 22:11 ` bugzilla-daemon
2019-10-15 22:12 ` bugzilla-daemon
2019-10-15 22:12 ` bugzilla-daemon
2019-10-16 14:27 ` bugzilla-daemon
2019-10-16 14:29 ` bugzilla-daemon
2019-10-16 17:29 ` bugzilla-daemon
2019-10-16 22:03 ` bugzilla-daemon
2019-10-20 20:06 ` bugzilla-daemon
2019-10-23 16:46 ` bugzilla-daemon
2019-10-28 20:16 ` bugzilla-daemon
2019-11-30 18:24 ` bugzilla-daemon
2019-12-07 10:28 ` bugzilla-daemon
2019-12-07 23:50 ` bugzilla-daemon
2019-12-07 23:55 ` bugzilla-daemon
2019-12-11  0:37 ` bugzilla-daemon
2019-12-11  0:39 ` bugzilla-daemon
2019-12-12  5:00 ` bugzilla-daemon
2019-12-12 14:37 ` bugzilla-daemon
2019-12-13 10:38 ` bugzilla-daemon
2019-12-16  4:40 ` bugzilla-daemon
2019-12-16 13:40 ` bugzilla-daemon
2019-12-20 22:17 ` bugzilla-daemon
2020-02-25  1:22 ` bugzilla-daemon
2020-02-25  2:00 ` bugzilla-daemon
2020-02-25  3:06 ` bugzilla-daemon
2020-02-25 17:26 ` bugzilla-daemon
2020-02-25 21:26 ` bugzilla-daemon
2020-02-26  9:54 ` bugzilla-daemon
2020-04-10 21:16 ` bugzilla-daemon
2020-04-15 19:43 ` bugzilla-daemon
2020-04-15 19:50 ` bugzilla-daemon
2020-05-13 20:45 ` bugzilla-daemon
2020-05-17 20:40 ` bugzilla-daemon
2020-06-24 19:15 ` bugzilla-daemon
2020-07-27 16:02 ` bugzilla-daemon
2020-07-27 16:03 ` bugzilla-daemon
2020-09-25  7:31 ` bugzilla-daemon
2020-09-25  7:34 ` bugzilla-daemon
2020-09-30  9:22 ` bugzilla-daemon
2020-09-30 16:31 ` bugzilla-daemon
2020-09-30 19:23 ` bugzilla-daemon
2020-09-30 20:03 ` bugzilla-daemon
2020-10-01 14:59 ` bugzilla-daemon
2020-10-01 17:21 ` bugzilla-daemon
2020-10-01 17:27 ` bugzilla-daemon
2020-10-01 17:55 ` bugzilla-daemon
2021-02-08 22:00 ` bugzilla-daemon
2021-02-08 22:13 ` bugzilla-daemon
2021-02-08 22:15 ` bugzilla-daemon
2023-04-13 20:11 ` bugzilla-daemon [this message]

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=bug-204241-2300-wSVAbJklHX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.