All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217915] System fails to resume correctly after Thunderbolt dock disconnected while sleeping
Date: Fri, 15 Sep 2023 23:23:53 +0000	[thread overview]
Message-ID: <bug-217915-208809-hnYpv0mQ4L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217915-208809@https.bugzilla.kernel.org/>

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

--- Comment #1 from Mark Blakeney (mark.blakeney@bullet-systems.net) ---
Mika, in bug #216728, you were concerned that I am using
"mem_sleep_default=deep" option but please note the very first thing I removed
(and have repeated a few times including today) to confirm that the problem
still occurs. I.e. that option is irrelevant to this issue. Note, I have used
that option for the 3 years I have had the laptop because if I don't then my
laptop battery will die overnight when simply suspending. I will remove it,
enable thunderbolt.dyndbg=+p, and then will capture a new dmesg output
(compared to what I did for bug #216728) to attach here.

Note that I use fwupd often to ensure my BIOS and dock etc are always running
the latest firmware. Dell updates both quite frequently and I am always running
the latest. It was mentioned in that email thread at
https://www.spinics.net/lists/linux-pci/msg142902.html that changing the BIOS
thunderbird setting to "No security" helps alleviate this issue but I don't
have any security options like that in my BIOS.

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

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

  reply	other threads:[~2023-09-15 23:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 23:11 [Bug 217915] New: System fails to resume correctly after Thunderbolt dock disconnected while sleeping bugzilla-daemon
2023-09-15 23:23 ` bugzilla-daemon [this message]
2023-09-15 23:29 ` [Bug 217915] " bugzilla-daemon
2023-09-15 23:40 ` bugzilla-daemon
2023-09-16  1:22 ` bugzilla-daemon
2023-09-16  1:23 ` bugzilla-daemon
2023-09-16 17:14 ` bugzilla-daemon
2023-09-16 22:07 ` bugzilla-daemon
2023-09-17  6:57 ` bugzilla-daemon
2023-09-17 11:26 ` bugzilla-daemon
2023-09-17 19:01 ` bugzilla-daemon
2023-09-18  5:36 ` bugzilla-daemon
2023-10-10 23:23 ` 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-217915-208809-hnYpv0mQ4L@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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.