From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Christian Schaubschläger" <christian.schaubschlaeger@gmx.at>
Cc: linux-usb@vger.kernel.org,
"michael.simon@cpsd.at" <michael.simon@cpsd.at>
Subject: Re: Possible problem with thunderbolt 4
Date: Mon, 6 Mar 2023 13:52:36 +0200 [thread overview]
Message-ID: <20230306115236.GE62143@black.fi.intel.com> (raw)
In-Reply-To: <Y9fPxIKIOrkHmjHS@black.fi.intel.com>
Hi Christian,
On Mon, Jan 30, 2023 at 04:10:12PM +0200, Mika Westerberg wrote:
> Hi,
>
> On Mon, Jan 30, 2023 at 11:52:59AM +0100, Christian Schaubschläger wrote:
> > Hi,
> >
> > Am 27.01.23 um 13:27 schrieb Mika Westerberg:
> > > Yeah, I just got report from the folks and unfortunately we were not
> > > able to reproduce the issue in the lab. The PCIe tunnel stays up (or
> > > gets re-created) after reboot from Linux and is visible in the UEFI
> > > shell (so in the BIOS).
> > >
> > > So at the moment I'm out of ideas why this happens since Windows flows
> > > should be the same. And we have no means to repro it locally to
> > > investigate further :/
> >
> > Ok. I try to get access to some more TB4 devices. Currently I have two
> > (HP, Lenovo) that show the issue when the software connection manager
> > is used.
>
> We should be getting one HP EliteBook 630 G9 soon (I guess this is one
> of the systems you see the issue). Once we get it we will try to repro
> and investigate further.
We are able to reproduce the issue and it was root caused to be missing
UNSET_INBOUND_SBTX port operation during retimer enumeration. I posted a
series of fixes few minutes ago (with you Cc'd) and one of them should
fix this issue:
https://lore.kernel.org/linux-usb/20230306113605.46137-3-mika.westerberg@linux.intel.com/
next prev parent reply other threads:[~2023-03-06 11:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:24 Possible problem with thunderbolt 4 Christian Schaubschläger
2022-12-27 14:28 ` Mika Westerberg
2022-12-30 7:57 ` Christian Schaubschläger
2022-12-30 9:28 ` Mika Westerberg
2022-12-30 11:38 ` Christian Schaubschläger
2022-12-30 11:55 ` Mika Westerberg
2022-12-30 12:08 ` Christian Schaubschläger
2022-12-30 12:21 ` Mika Westerberg
2023-01-02 8:56 ` Christian Schaubschläger
2023-01-02 11:11 ` Mika Westerberg
2023-01-02 11:45 ` Christian Schaubschläger
2023-01-02 16:23 ` Mika Westerberg
2023-01-03 9:08 ` Christian Schaubschläger
2023-01-03 11:08 ` Mika Westerberg
2023-01-03 12:14 ` Christian Schaubschläger
2023-01-03 16:07 ` Mika Westerberg
2023-01-03 17:50 ` Christian Schaubschläger
2023-01-04 8:04 ` Mika Westerberg
2023-01-09 12:17 ` Christian Schaubschläger
2023-01-09 12:50 ` Mika Westerberg
2023-01-09 14:21 ` Christian Schaubschläger
2023-01-10 15:12 ` Mika Westerberg
2023-01-11 10:38 ` Christian Schaubschläger
2023-01-11 10:45 ` Mika Westerberg
2023-01-19 9:41 ` Christian Schaubschläger
2023-01-19 10:10 ` Mika Westerberg
2023-01-19 14:37 ` Christian Schaubschläger
2023-01-20 10:14 ` Mika Westerberg
2023-01-20 11:19 ` Christian Schaubschläger
2023-01-20 11:36 ` Mika Westerberg
2023-01-27 12:07 ` Christian Schaubschläger
2023-01-27 12:27 ` Mika Westerberg
2023-01-30 10:52 ` Christian Schaubschläger
2023-01-30 14:10 ` Mika Westerberg
2023-03-06 11:52 ` Mika Westerberg [this message]
2023-03-06 12:27 ` Christian Schaubschläger
2023-05-23 8:22 ` Christian Schaubschläger
2023-05-23 8:55 ` Mika Westerberg
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=20230306115236.GE62143@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=christian.schaubschlaeger@gmx.at \
--cc=linux-usb@vger.kernel.org \
--cc=michael.simon@cpsd.at \
/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.