From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Christian Schaubschläger" <christian.schaubschlaeger@gmx.at>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>, linux-usb@vger.kernel.org
Subject: Re: USB issue on a TB4 controller?
Date: Tue, 30 May 2023 15:17:56 +0300 [thread overview]
Message-ID: <20230530121756.GG45886@black.fi.intel.com> (raw)
In-Reply-To: <d6e7e0d5-0b30-d66c-2ee8-4f0c0caef0b9@gmx.at>
On Tue, May 30, 2023 at 02:11:21PM +0200, Christian Schaubschläger wrote:
>
> >> Can I enable this on the command line? Because I guess I need traces from startup when the dock is connected already.
> > I think you can add "trace_event=xhci-hcd" in the kernel command line to
> > get it enabled boot time. See:
> >
> > https://docs.kernel.org/trace/events.html#boot-option
>
> Hm,
>
> [ 0.029711] Kernel command line: bzImage.efi thunderbolt.dyndbg=+p trace_event=xhci-hcd root=PARTUUID=1761F245-C668-41F5-90E4-5BBF2224097A rootwait nomodeset ima_appraise=off
> [ 0.063715] Failed to enable trace event: xhci-hcd
Could be that it expects the driver to be built-in in that case.
next prev parent reply other threads:[~2023-05-30 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 11:15 USB issue on a TB4 controller? Christian Schaubschläger
2023-05-26 12:36 ` Mika Westerberg
2023-05-29 10:59 ` Mathias Nyman
2023-05-30 10:13 ` Christian Schaubschläger
2023-05-30 10:50 ` Mika Westerberg
2023-05-30 12:11 ` Christian Schaubschläger
2023-05-30 12:17 ` Mika Westerberg [this message]
[not found] ` <a22f8874-c2b3-92a5-e858-b877872e5284@gmx.at>
[not found] ` <894ba559-9233-4428-69e7-7c0bf5c7556e@gmx.at>
2023-05-31 10:51 ` Mathias Nyman
2023-05-31 11:56 ` Christian Schaubschläger
2023-06-01 13:54 ` Mathias Nyman
2023-06-07 6:57 ` Christian Schaubschläger
2023-07-04 13:38 ` Christian Schaubschläger
2023-07-06 13:35 ` Mathias Nyman
2023-08-16 7:13 ` Christian Schaubschläger
2023-09-04 9:31 ` Christian Schaubschläger
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=20230530121756.GG45886@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=christian.schaubschlaeger@gmx.at \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.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.