From: Evan Green <evgreen@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
gil.fine@intel.com, Rajmohan Mani <rajmohan.mani@intel.com>,
linux-usb@vger.kernel.org, Prashant Malani <pmalani@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: thunderbolt: Warning and 20 second delay in S4
Date: Mon, 12 Jul 2021 16:46:18 -0700 [thread overview]
Message-ID: <CAE=gft6pax+OB-TDDUEUabmc8p3x-p7CC-9ihNbjRKq0MgdisA@mail.gmail.com> (raw)
In-Reply-To: <YOk/dzmF9sRg4uBn@kroah.com>
On Fri, Jul 9, 2021 at 11:34 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Fri, Jul 09, 2021 at 02:31:35PM -0700, Evan Green wrote:
> > Hi Mika et al,
> >
> > I'm experimenting with suspending to disk (hibernate) on a Tigerlake
> > Chromebook running the chromeos-5.4 kernel. I don't have any USB4
> > peripherals plugged in. I'm getting this warning, along with a 20
> > second stall, both when going down for hibernate and coming back up.
>
> 5.4 is pretty old, especially for thunderbolt issues, can you try 5.13
> please?
Good idea. On 5.13.0-next-20210709, I see the warning and delay even
at boot when runtime pm kicks in. This should make for an easier repro
at least:
[ 18.832016] thunderbolt 0000:00:0d.2: 0: timeout reading config
space 2 from 0x6
[ 18.840309] ------------[ cut here ]------------
[ 18.845466] thunderbolt 0000:00:0d.2: interrupt for RX ring 0 is
already disabled
[ 18.853836] WARNING: CPU: 0 PID: 5 at drivers/thunderbolt/nhi.c:103
ring_interrupt_active+0x1b7/0x1da
...
[ 18.977736] CPU: 0 PID: 5 Comm: kworker/0:0 Tainted: G U
5.13.0-next-20210709 #18
[ 18.996804] Workqueue: pm pm_runtime_work
[ 19.001285] RIP: 0010:ring_interrupt_active+0x1b7/0x1da
...
[ 19.100302] Call Trace:
[ 19.103031] tb_ring_stop+0x9d/0x17d
[ 19.107022] tb_ctl_stop+0x33/0xa0
[ 19.110822] tb_domain_runtime_suspend+0x35/0x3a
[ 19.115979] nhi_runtime_suspend+0x1f/0x4c
[ 19.120557] pci_pm_runtime_suspend+0x5a/0x173
[ 19.125533] ? pci_pm_restore_noirq+0x73/0x73
[ 19.130411] __rpm_callback+0x8a/0x10d
[ 19.134595] rpm_callback+0x22/0x74
[ 19.138489] ? pci_pm_restore_noirq+0x73/0x73
[ 19.143355] rpm_suspend+0x21e/0x514
[ 19.147355] pm_runtime_work+0x8a/0xa5
[ 19.151554] process_one_work+0x1b7/0x368
[ 19.156027] worker_thread+0x213/0x372
[ 19.160217] kthread+0x147/0x15f
[ 19.163827] ? pr_cont_work+0x58/0x58
[ 19.167928] ? kthread_blkcg+0x31/0x31
[ 19.172113] ret_from_fork+0x1f/0x30
[ 19.176105] ---[ end trace 438b7f20f6b4049d ]---
next prev parent reply other threads:[~2021-07-12 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 21:31 thunderbolt: Warning and 20 second delay in S4 Evan Green
2021-07-10 6:34 ` Greg KH
2021-07-12 23:46 ` Evan Green [this message]
2021-07-13 0:16 ` Mani, Rajmohan
2021-07-13 20:50 ` Evan Green
2021-07-13 22:00 ` Mani, Rajmohan
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='CAE=gft6pax+OB-TDDUEUabmc8p3x-p7CC-9ihNbjRKq0MgdisA@mail.gmail.com' \
--to=evgreen@chromium.org \
--cc=gil.fine@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pmalani@google.com \
--cc=rajmohan.mani@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.