From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
AceLan Kao <acelan@gmail.com>
Subject: Re: [bugzilla-daemon@bugzilla.kernel.org: [Bug 205119] New: It takes long time to wake up from s2idle on Dell XPS 7390 2-in-1]
Date: Wed, 9 Oct 2019 07:05:34 +0300 [thread overview]
Message-ID: <20191009040534.GL2819@lahna.fi.intel.com> (raw)
In-Reply-To: <20191008164232.GA173643@google.com>
Hi,
Most likely not a regression as Ice Lake support was just added in
v5.4-rc1.
@AceLan, I've seen similar issue before and that was fixed by a BIOS/FW
upgrade. Can you check if there is newer BIOS/FW for that system and see
if it helps?
Let's continue debugging on bugzilla.
On Tue, Oct 08, 2019 at 11:42:32AM -0500, Bjorn Helgaas wrote:
> AceLan, do you know if this is a regression and if so, when it was
> introduced?
>
> ----- Forwarded message from bugzilla-daemon@bugzilla.kernel.org -----
>
> Date: Tue, 08 Oct 2019 02:56:27 +0000
> From: bugzilla-daemon@bugzilla.kernel.org
> To: bjorn@helgaas.com
> Subject: [Bug 205119] New: It takes long time to wake up from s2idle on Dell
> XPS 7390 2-in-1
> Message-ID: <bug-205119-41252@https.bugzilla.kernel.org/>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=205119
>
> Bug ID: 205119
> Summary: It takes long time to wake up from s2idle on Dell XPS
> 7390 2-in-1
> Product: Drivers
> Version: 2.5
> Kernel Version: 5.4-rc2
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: PCI
> Assignee: drivers_pci@kernel-bugs.osdl.org
> Reporter: acelan@gmail.com
> Regression: No
>
> Created attachment 285395
> --> https://bugzilla.kernel.org/attachment.cgi?id=285395&action=edit
> dmesg log
>
> 1. Enter s2idle at 28.39s
> 2. Press power button at 246.10s
> 3. The machine stuck until 412.30s and spit out thunderbolt warning messages
> 4. thunderbolt port keeps working after s2idle, plug-in Dell WD19TB
> dock(472.45s), and the "boltctl list" shows the dock info correctly.
>
> BTW, I also found that there are 2 tbt ports on the machine, and if I plug in
> one TBT dock, and the wakeup time could be reduced by 80 seconds. And if I plug
> in 2 docks in both TBT ports, the machine wakes up from s2idle quick enough as
> the normal system.
>
> I believe the 2 lines are related.
> [ 330.388604] thunderbolt 0000:00:0d.3: failed to send driver ready to ICM
> [ 412.308083] thunderbolt 0000:00:0d.2: failed to send driver ready to ICM
>
> --
> You are receiving this mail because:
> You are watching the assignee of the bug.
>
> ----- End forwarded message -----
next prev parent reply other threads:[~2019-10-09 4:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 16:42 [bugzilla-daemon@bugzilla.kernel.org: [Bug 205119] New: It takes long time to wake up from s2idle on Dell XPS 7390 2-in-1] Bjorn Helgaas
2019-10-09 4:05 ` Mika Westerberg [this message]
2019-10-09 7:50 ` AceLan Kao
2019-10-09 7:56 ` Mika Westerberg
2019-10-10 8:09 ` Yehezkel Bernat
2019-10-14 5:54 ` AceLan Kao
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=20191009040534.GL2819@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=acelan@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael.jamet@intel.com \
/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.