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: Wed, 11 Jan 2023 12:45:31 +0200 [thread overview]
Message-ID: <Y76TS54PJpmseZs3@black.fi.intel.com> (raw)
In-Reply-To: <3ccb150b-dbd9-c9d0-0e8c-8c169f0d8faf@gmx.at>
On Wed, Jan 11, 2023 at 11:38:02AM +0100, Christian Schaubschläger wrote:
> Hi,
> > Okay thanks for checking. I'm discussing with our Windows folks if there
> > is something done differently in Windows side. They do similar reset in
> > certain flows but I'm not sure if it is exactly on "reboot" and it is
> > not clear whether Windows and Linux "reboot" in general is doing the
> > same thing either.
> >
> > In the meantime, did we try this already?
> >
> > 0. Drop all kernel changes
> > 1. Boot the system up, nothing connected
> > 2. Plug in the dock
> > 3. Check that it works (lspci etc.)
> > 4. Unload the Thunderbolt driver
> >
> > # rmmod thunderbolt
> >
> > 5. Reboot the system
>
> I think we did not try this one so far. But I did now -> same result...
Okay :(
> What I _did_ find out is this: if I disable ACPI on the kernel command
> line (acpi=off), things work fine. I can even boot with the dock
> unplugged, then plug it when linux is up, and it works in linux, and
> also after the reboot in the firmware!
>
> Of course switching off ACPI is not a real option... but maybe this
> brings some light into the dark...
It pretty much disables a lot of functionality so I don't think it helps
here, unfortunately.
next prev parent reply other threads:[~2023-01-11 10:45 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 [this message]
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
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=Y76TS54PJpmseZs3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).