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: Fri, 24 Oct 2025 18:36:17 +0300 [thread overview]
Message-ID: <8fe27842-8155-44db-b262-a148b5ce5436@linux.intel.com> (raw)
In-Reply-To: <CAAcb1K-o7DY3Kvqdr+=MN8OsgRZr+g43-zC6YSLG0hbNxEQUeg@mail.gmail.com>
On 10/20/25 09:43, Milan Oravec wrote:
> Thank you, is there any workaround for this to get DbC working for me?
I just wrote a quick hack that bluntly retries early_ioremap() with a smaller
size, and then checks if we are lucky and DbC capability in xhci mmio space
is withing this new range.
It will still trigger the same "WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:139"
messages, possible several, but would be interesting to see if it works.
Thanks
-Mathias
next prev parent reply other threads:[~2025-10-24 15:36 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 [this message]
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
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=8fe27842-8155-44db-b262-a148b5ce5436@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