From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216917] hibernation regression since 6.0.18 (Ryzen-5650U incl. Radeon GPU)
Date: Wed, 11 Jan 2023 22:23:30 +0000 [thread overview]
Message-ID: <bug-216917-2300-LrdHsck1vf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216917-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216917
--- Comment #6 from kolAflash (kolAflash@kolahilft.de) ---
Created attachment 303585
--> https://bugzilla.kernel.org/attachment.cgi?id=303585&action=edit
6.1.4 dmesg after hibernation
(In reply to Mario Limonciello (AMD) from comment #4)
> [...]
> Is it 100% failure rate on 6.0.y?
Yes.
> Since you mentioned that you couldn't effectively use 6.1.y because of the
> MST issue, are you only finding it on 6.0.y when connected to a dock or
> anything else unique?
No.
Happens with dock, with simple USB-C power (no dock) and on battery.
> > Sadly I don't know how to provide helpful logs. After reboot there's
> nothing
> > helpful in /var/log/messages
>
> Can you check /var/lib/systemd/pstore? Perhaps there was a kernel crash
> that got saved into NVRAM and restored by systemd on the next boot.
Sadly that file doesn't exist.
There are some files in /sys/fs/pstore/. But nothing from today.
(In reply to Alex Deucher from comment #5)
> Can you attach your dmesg output?
I don't know how to get logs (including dmesg) when hibernation has failed.
As said, after reboot there's nothing new in /var/log/messages
Instead I attached dmesg after hibernation with v6.1.4. Is that helpful?
Another thing:
Is it important that my SWAP is a file /swap on an ext4 partition inside a LUKS
partition?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-01-11 22:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216917-2300@https.bugzilla.kernel.org/>
2023-01-11 21:37 ` [Bug 216917] hibernation regression since 6.0.18 (Ryzen-5650U incl. Radeon GPU) bugzilla-daemon
2023-01-11 21:45 ` bugzilla-daemon
2023-01-11 21:46 ` bugzilla-daemon
2023-01-11 22:23 ` bugzilla-daemon [this message]
2023-01-11 22:36 ` bugzilla-daemon
2023-01-11 23:19 ` bugzilla-daemon
2023-01-12 13:18 ` bugzilla-daemon
2023-01-12 17:24 ` bugzilla-daemon
2023-01-12 17:47 ` bugzilla-daemon
2023-01-13 9:16 ` bugzilla-daemon
2023-01-16 16:14 ` bugzilla-daemon
2023-01-16 16:15 ` bugzilla-daemon
2023-01-16 16:16 ` bugzilla-daemon
2023-01-16 16:16 ` bugzilla-daemon
2023-01-16 16:20 ` bugzilla-daemon
2023-01-16 16:21 ` bugzilla-daemon
2023-01-16 16:41 ` bugzilla-daemon
2023-01-16 17:02 ` bugzilla-daemon
2023-01-16 17:49 ` bugzilla-daemon
2023-01-16 18:12 ` bugzilla-daemon
2023-01-16 20:59 ` bugzilla-daemon
2023-01-16 21:02 ` bugzilla-daemon
2023-01-16 21:08 ` bugzilla-daemon
2023-01-17 7:43 ` bugzilla-daemon
2023-01-17 15:34 ` bugzilla-daemon
2023-01-17 15:46 ` bugzilla-daemon
2023-01-17 16:57 ` bugzilla-daemon
2023-01-11 18:04 [Bug 216917] New: " bugzilla-daemon
2023-01-11 18:50 ` [Bug 216917] " bugzilla-daemon
2023-01-11 19:18 ` bugzilla-daemon
2023-01-11 21:36 ` bugzilla-daemon
2023-01-11 21:37 ` bugzilla-daemon
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-216917-2300-LrdHsck1vf@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.