All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Matt Turner <mattst88@gmail.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-usb@vger.kernel.org
Subject: Re: Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock
Date: Tue, 4 Aug 2020 14:47:17 +0300	[thread overview]
Message-ID: <20200804114717.GN1375436@lahna.fi.intel.com> (raw)
In-Reply-To: <CAEdQ38FRBg_ptDWVr7yRwC4GCd5DxWkBzH+HyTJXL56v2cL4+Q@mail.gmail.com>

On Mon, Aug 03, 2020 at 09:52:26AM -0700, Matt Turner wrote:
> On Mon, Aug 3, 2020 at 3:54 AM Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > Can you try the patch here?
> >
> >   https://lore.kernel.org/patchwork/patch/1257708/
> 
> Thanks.
> 
> It looks like that doesn't fix the problem. I hotplugged the dock
> about 25 times this morning and it was only successful once, very
> early in the testing. I didn't think it was going to be that rare, so
> I didn't capture the log and now I can't reproduce it :(
> 
> Any other ideas or patches I should try?

Can you try so that you boot without device connected. Then plug in the
dock, and wait a bit for it to enumerate (you can check thunderbolt
related messages in dmesg).

Then send me full dmesg and output of command 'sudo lspci -vv'.

I also sugged to file a bug in kernel bugzilla
(https://bugzilla.kernel.org/) and add these logs there as well.

  reply	other threads:[~2020-08-04 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31  3:36 Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock Matt Turner
2020-08-03 10:54 ` Mika Westerberg
2020-08-03 16:52   ` Matt Turner
2020-08-04 11:47     ` Mika Westerberg [this message]
2020-08-12 22:40       ` Matt Turner

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=20200804114717.GN1375436@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --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.