linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220016] USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work
Date: Fri, 18 Apr 2025 16:25:39 +0000	[thread overview]
Message-ID: <bug-220016-208809-TTNveuhjke@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220016-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220016

Ilpo Järvinen (ilpo.jarvinen@linux.intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ilpo.jarvinen@linux.intel.c
                   |                            |om

--- Comment #11 from Ilpo Järvinen (ilpo.jarvinen@linux.intel.com) ---
Does also 6.13 fail if pci=realloc is on the kernel command line? It's not
clear to me if PCI resource reallocation got enabled along with the kernel
upgrade, that is, if Fedora packaging e.g. decided to enable
CONFIG_PCI_REALLOC_ENABLE_AUTO in kernel's .config which is orthogonal to
kernel version changes.

Please provide /proc/iomem from both working and non-working configuration.
Preferrably with the otherwise identical kernel version, if you can't get it
from the non-working configuration at all due to lack of keyboard, I'll manage
with the log from working only (things can be inferred from dmesg but it's very
very tedious process).

Could you also clarify what you meant with this: "This issue also seems to be
present in 6.15.0 as well."? Kernel version 6.15 is not released yet, 6.15
cycle is only at -rc2 at this point.

I'll try to look more into this next week.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-04-18 16:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  0:25 [Bug 220016] New: USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work bugzilla-daemon
2025-04-16  0:26 ` [Bug 220016] " bugzilla-daemon
2025-04-16  7:21 ` bugzilla-daemon
2025-04-16  8:53 ` bugzilla-daemon
2025-04-16 17:20 ` bugzilla-daemon
2025-04-16 17:43 ` bugzilla-daemon
2025-04-16 17:43 ` bugzilla-daemon
2025-04-16 17:51 ` bugzilla-daemon
2025-04-16 21:38 ` bugzilla-daemon
2025-04-16 22:19 ` bugzilla-daemon
2025-04-17 13:22 ` bugzilla-daemon
2025-04-18 16:25 ` bugzilla-daemon [this message]
2025-04-18 17:37 ` bugzilla-daemon
2025-04-18 17:38 ` bugzilla-daemon
2025-04-18 17:38 ` bugzilla-daemon
2025-04-18 17:39 ` bugzilla-daemon
2025-04-18 17:45 ` bugzilla-daemon
2025-04-18 17:53 ` bugzilla-daemon
2025-04-18 18:05 ` bugzilla-daemon
2025-04-18 18:05 ` bugzilla-daemon
2025-04-18 18:06 ` bugzilla-daemon
2025-04-18 18:06 ` bugzilla-daemon
2025-04-18 18:09 ` bugzilla-daemon
2025-04-21 17:35 ` bugzilla-daemon
2025-04-25 16:05 ` bugzilla-daemon
2025-04-25 19:34 ` bugzilla-daemon
2025-04-25 19:35 ` bugzilla-daemon
2025-04-28 17:06 ` bugzilla-daemon
2025-04-28 19:00 ` bugzilla-daemon
2025-04-30 10:39 ` bugzilla-daemon
2025-04-30 10:44 ` bugzilla-daemon
2025-04-30 14:46 ` bugzilla-daemon
2025-04-30 14:46 ` bugzilla-daemon

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=bug-220016-208809-TTNveuhjke@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).