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 17:45:56 +0000 [thread overview]
Message-ID: <bug-220016-208809-4L6HNo5u7M@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220016-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220016
--- Comment #16 from Steven A. Falco (stevenfalco@gmail.com) ---
I ran the tests you requested. I attached /proc/iomem for 6.13.10 both with
realloc=off and realloc=on. I repeated the tests with 6.14.2.
For both kernel versions, realloc=on results in a non-functional USB keyboard.
For both kernels, realloc=off works properly.
I had been running Fedora 41 with their 6.13 kernel. It was compiled with
realloc=off.
I then upgraded to Fedora 42 with their 6.14 kernel. It was compiled with
realloc=on.
Therefore, this is not a new problem with 6.14; it is just that the kernel
option was changed in Fedora 42.
I cannot comment about 6.15 but I think Joe was the one who tried it. Perhaps
he can comment on that. However, since both 6.13 and 6.14 don't work if
realloc=on, it probably doesn't matter.
Please let me know if there is any other data you need.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-04-18 17:45 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
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 [this message]
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-4L6HNo5u7M@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 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.