All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 217664] Laptop doesnt wake up from suspend mode.
Date: Mon, 28 Aug 2023 19:13:04 +0000	[thread overview]
Message-ID: <bug-217664-2300-OBXHZ3Zbr2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217664-2300@https.bugzilla.kernel.org/>

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

--- Comment #41 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
Was that NVME something you added to the system or it came with it?

I am suspecting that your platform or the NVME doesn't end up activating a
feature needed for s2idle to work properly called DevSlp at all or at the right
timing.

Can you please share to me an acpidump?  I want to check if you have some _DSD
properties set up appropriately.  You can see more about this in
7c5f641a5914 ("ata: libahci: Adjust behavior when StorageD3Enable _DSD is set")

If it's a missing _DSD but the system and disk both support DevSlp we can
probably find a way to work around that in the kernel.

-- 
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-08-28 19:13 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  9:59 [Bug 217664] New: Laptop doesnt wake up from suspend mode bugzilla-daemon
2023-07-12 10:03 ` [Bug 217664] " bugzilla-daemon
2023-07-12 10:03 ` bugzilla-daemon
2023-07-14  2:24 ` bugzilla-daemon
2023-07-14  7:28 ` bugzilla-daemon
2023-07-15 14:16 ` bugzilla-daemon
2023-07-19 21:22 ` bugzilla-daemon
2023-08-02  7:35 ` bugzilla-daemon
2023-08-04 13:44 ` bugzilla-daemon
2023-08-16  6:52 ` bugzilla-daemon
2023-08-16  6:53 ` bugzilla-daemon
2023-08-16 12:29 ` bugzilla-daemon
2023-08-16 15:35 ` bugzilla-daemon
2023-08-16 15:38 ` bugzilla-daemon
2023-08-16 17:54 ` bugzilla-daemon
2023-08-16 18:12 ` bugzilla-daemon
2023-08-17  7:58 ` bugzilla-daemon
2023-08-17 16:40 ` bugzilla-daemon
2023-08-17 17:09 ` bugzilla-daemon
2023-08-17 17:09 ` bugzilla-daemon
2023-08-18  2:49 ` bugzilla-daemon
2023-08-18  2:51 ` bugzilla-daemon
2023-08-18 13:26 ` bugzilla-daemon
2023-08-19 17:04 ` bugzilla-daemon
2023-08-19 17:13 ` bugzilla-daemon
2023-08-23 12:51 ` bugzilla-daemon
2023-08-23 13:32 ` bugzilla-daemon
2023-08-23 22:09 ` bugzilla-daemon
2023-08-23 22:52 ` bugzilla-daemon
2023-08-24 10:13 ` bugzilla-daemon
2023-08-24 18:29 ` bugzilla-daemon
2023-08-25  6:06 ` bugzilla-daemon
2023-08-25  6:07 ` bugzilla-daemon
2023-08-25  6:07 ` bugzilla-daemon
2023-08-25  6:08 ` bugzilla-daemon
2023-08-25  6:21 ` bugzilla-daemon
2023-08-25  6:33 ` bugzilla-daemon
2023-08-25 19:07 ` bugzilla-daemon
2023-08-26 17:15 ` bugzilla-daemon
2023-08-27  4:11 ` bugzilla-daemon
2023-08-27  6:44 ` bugzilla-daemon
2023-08-28  1:15 ` bugzilla-daemon
2023-08-28 18:39 ` bugzilla-daemon
2023-08-28 19:13 ` bugzilla-daemon [this message]
2023-08-28 19:13 ` bugzilla-daemon
2023-08-28 21:14 ` bugzilla-daemon
2023-08-28 21:26 ` bugzilla-daemon
2023-08-28 21:38 ` bugzilla-daemon
2023-08-28 22:00 ` bugzilla-daemon
2023-08-28 22:02 ` bugzilla-daemon
2023-08-28 22:03 ` [Bug 217664] Medion AMD Laptop doesn't wake up from s2idle with SATA disk bugzilla-daemon
2023-08-28 22:03 ` 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-217664-2300-OBXHZ3Zbr2@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.