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 12:01:42 +0000 [thread overview]
Message-ID: <bug-218092-215701-kl4xqvuIkl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218092-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218092
--- Comment #48 from Ertugrul Uyar (ertugruluyar.personal@gmail.com) ---
Before trying to sleep, I want to share some conf:
ertugruluyar@ertugruluyar-pc:~$ uname -a
Linux ertugruluyar-pc 6.6.0 #6 SMP PREEMPT_DYNAMIC Fri Nov 3 09:49:44 +03 2023
x86_64 x86_64 x86_64 GNU/Linux
ertugruluyar@ertugruluyar-pc:~$ sudo cat /sys/power/mem_sleep
[sudo] password for ertugruluyar:
s2idle [deep]
ertugruluyar@ertugruluyar-pc:~$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Suspend result:
I tried both sleep button that KDE's app menu and closed my laptop lid (which
is set to suspend). The result is issue happening like before. My laptop toke a
bit more time to open, but not too much.
Should I try hibernate etc. options?
Is the issue related with this?:
ertugruluyar@ertugruluyar-pc:~$ sudo cat /sys/power/mem_sleep
[sudo] password for ertugruluyar:
s2idle [deep]
--
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 12:01 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 [this message]
2023-11-03 12:05 ` bugzilla-daemon
2023-11-03 13:36 ` bugzilla-daemon
2023-11-03 13:58 ` bugzilla-daemon
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-kl4xqvuIkl@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 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.