From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218092] Laptop hanging on black screen, when suspended and woke up!
Date: Fri, 03 Nov 2023 13:58:58 +0000 [thread overview]
Message-ID: <bug-218092-215701-4uyY08A1Fc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218092-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218092
Bagas Sanjaya (bagasdotme@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bagasdotme@gmail.com
--- Comment #51 from Bagas Sanjaya (bagasdotme@gmail.com) ---
(In reply to Ertugrul Uyar from comment #50)
> (In reply to Mario Limonciello (AMD) from comment #49)
> > The patch doesn't work for your system this means.
> >
> > > ertugruluyar@ertugruluyar-pc:~$ sudo cat /sys/power/mem_sleep
> > [sudo] password for ertugruluyar:
> > s2idle [deep]
> >
> > From you above logs your system uses S3 by default, so it's not surprising
> > the patch doesn't work. It's only for systems that use s2idle.
> >
> > So there is some other problem than we have observed in the past.
>
> Okey, then, should I change to s2idle or remove the kernel that patched. I
> am on tuxedo's kernel by choose on grub menu. What do you suggest to me,
> should I just add amd_iommu=off to my grub config? Thank you for your helps
> by the way.
Try that!
--
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-11-03 13:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-218092-215701@https.bugzilla.kernel.org/>
2023-10-31 13:02 ` [Bug 218092] Laptop hanging on black screen, when suspended and woke up! bugzilla-daemon
2023-10-31 13:02 ` bugzilla-daemon
2023-10-31 15:49 ` bugzilla-daemon
2023-10-31 18:25 ` bugzilla-daemon
2023-10-31 18:35 ` bugzilla-daemon
2023-10-31 18:35 ` bugzilla-daemon
2023-10-31 18:38 ` bugzilla-daemon
2023-10-31 18:40 ` bugzilla-daemon
2023-10-31 18:40 ` bugzilla-daemon
2023-10-31 18:45 ` bugzilla-daemon
2023-10-31 19:25 ` bugzilla-daemon
2023-10-31 20:13 ` bugzilla-daemon
2023-10-31 20:48 ` bugzilla-daemon
2023-10-31 20:53 ` bugzilla-daemon
2023-11-01 9:11 ` bugzilla-daemon
2023-11-01 9:11 ` bugzilla-daemon
2023-11-01 17:08 ` bugzilla-daemon
2023-11-01 18:01 ` bugzilla-daemon
2023-11-01 18:02 ` bugzilla-daemon
2023-11-02 6:38 ` bugzilla-daemon
2023-11-02 6:52 ` bugzilla-daemon
2023-11-02 6:53 ` bugzilla-daemon
2023-11-02 7:08 ` bugzilla-daemon
2023-11-02 7:24 ` bugzilla-daemon
2023-11-02 13:27 ` bugzilla-daemon
2023-11-02 13:44 ` bugzilla-daemon
2023-11-02 13:46 ` bugzilla-daemon
2023-11-02 13:53 ` bugzilla-daemon
2023-11-02 13:58 ` bugzilla-daemon
2023-11-02 14:09 ` bugzilla-daemon
2023-11-02 14:11 ` bugzilla-daemon
2023-11-02 14:18 ` bugzilla-daemon
2023-11-02 14:25 ` bugzilla-daemon
2023-11-02 14:32 ` bugzilla-daemon
2023-11-02 14:46 ` bugzilla-daemon
2023-11-02 15:35 ` bugzilla-daemon
2023-11-02 15:42 ` bugzilla-daemon
2023-11-02 15:51 ` bugzilla-daemon
2023-11-02 16:29 ` bugzilla-daemon
2023-11-02 16:30 ` bugzilla-daemon
2023-11-02 16:48 ` bugzilla-daemon
2023-11-02 17:46 ` bugzilla-daemon
2023-11-02 18:04 ` bugzilla-daemon
2023-11-03 7:16 ` bugzilla-daemon
2023-11-03 9:19 ` Bagas Sanjaya
2023-11-03 9:19 ` bugzilla-daemon
2023-11-03 11:36 ` bugzilla-daemon
2023-11-03 11:42 ` bugzilla-daemon
2023-11-03 11:48 ` bugzilla-daemon
2023-11-03 12:01 ` bugzilla-daemon
2023-11-03 12:05 ` bugzilla-daemon
2023-11-03 13:36 ` bugzilla-daemon
2023-11-03 13:58 ` bugzilla-daemon [this message]
2023-11-03 14:04 ` bugzilla-daemon
2023-11-03 14:10 ` bugzilla-daemon
2023-11-03 14:55 ` bugzilla-daemon
2023-11-03 16:31 ` 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-218092-215701-4uyY08A1Fc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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