From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Milan Oravec <migo.oravec@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, linux-usb@vger.kernel.org
Subject: Re: Fwd: USB DBC hang during earlyprintk initialization
Date: Tue, 28 Oct 2025 19:19:02 +0200 [thread overview]
Message-ID: <9dc78bbb-b9db-4ab3-8cd9-bac40e0c8653@linux.intel.com> (raw)
In-Reply-To: <CAAcb1K9X+ZgigmiQ9btvV5vs+1UmxyZC39RCnS0tVZZUuYjToQ@mail.gmail.com>
On 10/28/25 15:29, Milan Oravec wrote:
> Hello Mathias, here is dmesg output after applying additional patch:
>
> [Ut okt 28 14:07:39 2025] Linux version 6.17.5-dirty (migo@migoG17)
> (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #59 SMP
> PREEMPT_DYNAMIC Tue Oct 28 11:54:08 CET
> 2025
> [Ut okt 28 14:07:39 2025] Command line: BOOT_IMAGE=/vmlinuz
> root=UUID=584262b6-b020-4e4f-95a3-1db754e28b6c earlyprintk=keep,xdbc1
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_map_pci_mmio: Failed to
> ioremap xhci-dbc with size 0x100000
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_map_pci_mmio: Retry xhci-dbc
> ioremap with reduced size 0x80000
> [Ut okt 28 14:07:39 2025] ------------[ cut here ]------------
> [Ut okt 28 14:07:39 2025] WARNING: CPU: 0 PID: 0 at
...> [Ut okt 28 14:07:39 2025] ---[ end trace 0000000000000000 ]---
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_map_pci_mmio: Failed to
> ioremap xhci-dbc with size 0x80000
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_map_pci_mmio: Retry xhci-dbc
> ioremap with reduced size 0x40000
> [Ut okt 28 14:07:39 2025] xhci_dbc:early_xdbc_parse_parameter: Looking
> for DbC capability at offset 0x480
> [Ut okt 28 14:07:39 2025] xhci_dbc:early_xdbc_parse_parameter: Looking
> for DbC capability at offset 0x490
> [Ut okt 28 14:07:39 2025] xhci_dbc:early_xdbc_parse_parameter: Looking
> for DbC capability at offset 0x4a0
> [Ut okt 28 14:07:39 2025] xhci_dbc:early_xdbc_parse_parameter: Looking
> for DbC capability at offset 0x4c0
> [Ut okt 28 14:07:39 2025] xhci_dbc:early_xdbc_parse_parameter: Looking
> for DbC capability at offset 0x4e0
> [Ut okt 28 14:07:39 2025] xhci_dbc:early_xdbc_parse_parameter: DbC
> capability found at offset 0x4e0
...> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_early_setup: DCE successfully cleared
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_early_setup: Successfully got
> xdbc table_dma page
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_early_setup: Successfully got
> xdbc out_dma page
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_early_setup: Successfully
> allocated event ring
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_early_setup: Successfully
> allocated in ring
> [Ut okt 28 14:07:39 2025] xhci_dbc:xdbc_early_setup: Successfully
> allocated out ring
> [Ut okt 28 14:07:44 2025] xhci_dbc:xdbc_start: waiting for connection timed out
This is promising, looks like code successfully interacts with hardware.
> [Ut okt 28 14:07:44 2025] xhci_dbc:xdbc_early_setup: Failed to start
> xdbc ret: -110
> [Ut okt 28 14:07:44 2025] xhci_dbc:early_xdbc_setup_hardware: failed
> to setup the connection to host
> [Ut okt 28 14:07:44 2025] Zone ranges:
> [Ut okt 28 14:07:44 2025] DMA [mem 0x0000000000001000-0x0000000000ffffff]
> [Ut okt 28 14:07:44 2025] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
> [Ut okt 28 14:07:44 2025] Normal [mem 0x0000000100000000-0x000000085de7ffff]
> [Ut okt 28 14:07:44 2025] Device empty
> [Ut okt 28 14:07:44 2025] Movable zone start for each node
> [Ut okt 28 14:07:44 2025] Early memory node ranges
>
> I've tested cable afterwards:
>
> echo enable > /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/dbc
>
> [Ut okt 28 14:12:28 2025] xhci_hcd 0000:09:00.4: DbC connected
> [Ut okt 28 14:12:29 2025] xhci_hcd 0000:09:00.4: DbC configured
>
> so cable is not the problem here...
>
> Thank you!
your lspci listed four xHCI controllers:
07:00.0 USB controller: ASMedia Technology Inc. Device 242c (rev 01)
(prog-if 30 [XHCI])
Region 0: Memory at fc600000 (64-bit, non-prefetchable) [size=32K]
09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD]
Raphael/Granite Ridge USB 3.1 xHCI (prog-if 30 [XHCI])
Region 0: Memory at fc300000 (64-bit, non-prefetchable) [size=1M]
09:00.4 USB controller: Advanced Micro Devices, Inc. [AMD]
Raphael/Granite Ridge USB 3.1 xHCI (prog-if 30 [XHCI])
Region 0: Memory at fc200000 (64-bit, non-prefetchable) [size=1M]
0a:00.0 USB controller: Advanced Micro Devices, Inc. [AMD]
Raphael/Granite Ridge USB 2.0 xHCI (prog-if 30 [XHCI])
Region 0: Memory at fca00000 (64-bit, non-prefetchable) [size=1M]
Could it be that the cable is connected to xHCI at 09:00.4 while
earlyprintk=keep,xdbc1 refers to different xHCI? possibly the one at 09:00.3?
Does earlyprintk=keep,xdbc2 work? or trying a different usb port?
Thanks
Mathias
next prev parent reply other threads:[~2025-10-28 17:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAcb1K_MJKWz+BYJmx0FDgrBOzzXm71-M7sgHDUOmBRppXWNzA@mail.gmail.com>
2025-10-15 7:43 ` Fwd: USB DBC hang during earlyprintk initialization Milan Oravec
2025-10-15 9:13 ` Greg KH
2025-10-15 19:11 ` Milan Oravec
2025-10-16 13:42 ` Mathias Nyman
2025-10-16 14:31 ` Milan Oravec
2025-10-16 20:49 ` Mathias Nyman
2025-10-20 6:43 ` Milan Oravec
2025-10-24 15:36 ` Mathias Nyman
2025-10-24 15:41 ` [RFT PATCH] usb: early: xhci-dbc: Try smaller early_ioremap size if original size fails Mathias Nyman
2025-10-26 2:32 ` kernel test robot
2025-10-24 18:48 ` Fwd: USB DBC hang during earlyprintk initialization Milan Oravec
2025-10-27 9:34 ` Mathias Nyman
2025-10-28 10:13 ` Mathias Nyman
2025-10-28 13:29 ` Milan Oravec
2025-10-28 17:19 ` Mathias Nyman [this message]
2025-10-28 18:10 ` Milan Oravec
2025-10-31 13:15 ` Milan Oravec
2025-12-04 20:46 ` Mathias Nyman
2025-12-05 7:18 ` Milan Oravec
2025-12-05 18:49 ` Milan Oravec
2025-12-17 9:20 ` Mathias Nyman
2025-12-18 20:03 ` Milan Oravec
2026-01-19 8:18 ` Milan Oravec
2026-01-19 11:01 ` Milan Oravec
2026-04-01 15:58 ` Milan Oravec
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=9dc78bbb-b9db-4ab3-8cd9-bac40e0c8653@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=migo.oravec@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox