From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org,
Chunfeng Yun <chunfeng.yun@mediatek.com>
Subject: Re: earlyprintk=xdbc seems broken
Date: Mon, 24 Jan 2022 16:55:22 +0200 [thread overview]
Message-ID: <dfb311e3-1a83-31a2-3c82-fd982c0757f6@linux.intel.com> (raw)
In-Reply-To: <YeLxE3zQ7Vexk3gv@hirez.programming.kicks-ass.net>
> [ 0.000000] xhci_dbc:early_xdbc_parse_parameter: dbgp_num: 0
> [ 4.984106] xhci_dbc:xdbc_start: waiting for connection timed out, DCPORTSC:0xa0
> [ 9.946159] xhci_dbc:xdbc_start: waiting for connection timed out, DCPORTSC:0xa0
> [ 9.946163] xhci_dbc:early_xdbc_setup_hardware: failed to setup the connection to host
>
> [ 12.818364] xhci_hcd 0000:00:0d.0: xHCI Host Controller
> [ 12.818373] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 1
> [ 12.820360] xhci_hcd 0000:00:0d.0: xHCI Host Controller
> [ 12.820363] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 2
> [ 12.821036] xhci_hcd 0000:00:14.0: xHCI Host Controller
> [ 12.821040] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
> [ 12.823451] xhci_hcd 0000:00:14.0: xHCI Host Controller
> [ 12.823453] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
> [ 17.115089] usb usb4-port4: Cannot enable. Maybe the USB cable is bad?
> [ 17.115163] usb usb4-port4: config error
Ok, I see it now.
Your setup has two xhci controllers, earlypringk=dbc enables dbc on the first xhci
it finds, which would be at 0000:00:0d.0.
Your cable is connected to the second xhci host at 0000:00:14.0
does using "earlyprintk=xdbc1" work?
Thanks
-Mathias
next prev parent reply other threads:[~2022-01-24 14:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:22 Peter Zijlstra
2021-12-03 0:52 ` Lu Baolu
2021-12-03 14:31 ` Mathias Nyman
2021-12-03 15:22 ` Dave Hansen
2021-12-03 15:29 ` Greg KH
2021-12-17 11:01 ` Mathias Nyman
2021-12-17 13:55 ` Peter Zijlstra
2021-12-17 15:19 ` Greg KH
2021-12-20 14:40 ` Peter Zijlstra
2021-12-20 15:06 ` Greg KH
2021-12-20 17:01 ` Peter Zijlstra
2021-12-20 14:34 ` Mathias Nyman
2021-12-20 15:51 ` Peter Zijlstra
2021-12-21 9:40 ` Peter Zijlstra
2021-12-21 9:41 ` Peter Zijlstra
2022-01-14 8:47 ` Peter Zijlstra
2022-01-14 19:31 ` Mathias Nyman
2022-01-15 16:06 ` Peter Zijlstra
2022-01-24 14:55 ` Mathias Nyman [this message]
2022-01-24 16:39 ` Peter Zijlstra
2022-01-24 16:46 ` Peter Zijlstra
2022-01-25 8:51 ` Mathias Nyman
2022-01-25 10:47 ` Peter Zijlstra
2022-01-25 10:54 ` Peter Zijlstra
2022-01-25 12:45 ` Peter Zijlstra
2022-01-25 13:09 ` Sven Schnelle
2022-01-25 13:54 ` Peter Zijlstra
2022-01-25 14:01 ` Sven Schnelle
2022-01-25 17:13 ` Mathias Nyman
2022-01-25 16:24 ` Dave Hansen
2022-02-17 3:44 ` Randy Dunlap
2022-01-25 19:39 ` Rajaram R
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=dfb311e3-1a83-31a2-3c82-fd982c0757f6@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=chunfeng.yun@mediatek.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®