Raspberry Pi 4 - USB Bus not detecting any devices

[Andrew Davis]

Pi 4 new install. System boots up but USB bus is not working.

Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk.

output of $lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)

output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report.

Not the only one experiencing bug. Another user created a post on the ubuntu forums:
https://ubuntuforums.org/showthread.php?t=2429396&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=13898142#post13898142

64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10-preinstalled-server-arm64+raspi3.img.xz

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1848703/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alexander Agnarson (alexander-agnarson)]

More discussion and users with same problem here:
https://www.raspberrypi.org/forums/viewtopic.php?p=1553904#p1553904

[Chris Fisher (chris-jupiterbroadcasting)]

I can reproduce this on my 4GB Pi4 with the 64bit image.

This does not seem to be an issue with the 32bit image in my quick testing. With the 32 bit image, both the keyboard and external storage are detected and working.

As you can see here with my USB keyboard and thumb drive attached, they are detected when running the 32bit image:

ubuntu@ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04d9:0006 Holtek Semiconductor, Inc. USB2.0 Hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 006: ID 0781:5575 SanDisk Corp. Cruzer Glide
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Akshay (akshaynakra)]

I can reproduce this on my 4GB Pi4 with the 64bit image as well. There are no devices detected -

ubuntu@ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Alexander Agnarson (alexander-agnarson)]

Reported/Confirmed/Assigned here: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790

[Ken Howe (leggazoid)]

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/view ... 6&start=25

The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/view ... 0#p1517839

and the kernel patch was this one:
https://github.com/raspberrypi/linux/is ... -520269280

[Ken Howe (leggazoid)]

Fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/v...46766&start=25

The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/v...rt=50#p1517839

and the kernel patch was this one:
https://github.com/raspberrypi/linux...ment-520269280

[Ken Howe (leggazoid)]

Fixed links
User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=25[/url]

The issue was solved by a kernel patch:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=50#p1517839[/url]

and the kernel patch was this one:
[url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url]

[Adam T (tiermann)]

Setting total_mem=2048 or 3072 in /boot/firmware/usercfg.txt allowed me to boot Pi4 4GB with 19.10 64bit with working USB. Of course I have less RAM now, but working USB.

Likely the above patch will fix it.

[Hui Wang (hui.wang)]

Please refer to this bug (the same bug as this one) #1848790

And I will submit the fixing patch to ubuntu kernel.

thx.

[Hui Wang (hui.wang)]

I built a testing kernel, not only includes the fix for USB host, but also includes all new patches from https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107 patches).

I tested both arm64 and armhf kernels on Pi4 without HDMI monitor, everything works well.

Could anybody help test these two kernels on Pi4 with HDMI monitor, Pi3 and Pi2 if you have any of them?

After verifying the kernel will not introduce regression on Pi4/3/2, I will submit the patches to UBUNTU kernel.

The new kernel could be downloaded: https://people.canonical.com/~hwang4/rpiv2/

To install and test the kernel:
copy arm64 or armhf folders to rootfs of Pi, sudo dpkg -i linux-modules-xxxx.deb; sudo dpkg -i linux-image-xxx.deb;sudo reboot

thx

[Mikael Glandberger (glandberger)]

The new patch is working fine connected to my HDMI monitor/TV. I also removed the temp patch using only 3GB ram, rebooted and all my memory is now available (Pi4 4GB). Will future updates break the patch or is all good? Thanks you so much!

[Anthony Bush (distributedfog)]

I can confirm as well - verified that the new patch from @hui.wang is working correctly on my Pi 4 4GB.

[Ricardo (ricardo.zzz)]

I'm a noob, can anyone tell me how to use the petch

[Scott van Looy (scottbert)]

It works for me, but no Bluetooth. However, I'm not sure if that's related/caused by this patch or a known issue.

[Hui Wang (hui.wang)]

@Ricardo,

just download the deb (https://people.canonical.com/~hwang4/rpiv2/arm64/) to your pi's rootfs

Then run:
sudo dpkg -i linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo dpkg -i linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo reboot

[Hui Wang (hui.wang)]

@Scott,

We haven't tested the bluetooth both under old kernel and under patched kernel, do you know how to verify the bluetooth on the pi? And we are going to look at bluetooth after fixing the usb host issue.

[Hui Wang (hui.wang)]

@Scott,

About the bluetooth, this is a comment from Dave Jones:

And one thing which isn't a bug:

    Bluetooth: we don't support bluetooth out of the box. Ubuntu on Pi is primarily a server distro and thus a stable serial console was prioritized over out-of-the-box Bluetooth support (note: I don't work on Ubuntu MATE; that's something separate).

    Bluetooth can be enabled by installing the "pi-bluetooth" package and switching a line in "syscfg.txt" on the boot partition from "include nobtcfg.txt" to "include "btcfg.txt". A tool to manage the hardware configuration on the Pi (including Bluetooth) is being developed, but I didn't have time to finish it for Eoan.

[Ricardo (ricardo.zzz)]

@Hui Wang,
But if I can't use the keyborad by USB, how can I type in those cmd?

[Hui Wang (hui.wang)]

@reply #21,

The simplest workaround is to plug the sd card into a cardreader and connect the cardreader to computer, then edit $mount_folder/system-boot/config.txt

Add total_mem=3072 in the section [pi4], just like below:

[pi4]
kernel=uboot_rpi_4.bin
max_framebuffers=2
total_mem=3072

Then reboot, you could you the usb keyboard now, after installing the testing kernel, you could remove total_mem=3072.

And another way to login is to use ssh.

[Hui Wang (hui.wang)]

And for me, I run commands through serial console, and if you have the uart->usb converter, you could use serial console too.

[Hui Wang (hui.wang)]

And this bug will be fixed with https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623

[Ricardo (ricardo.zzz)]

@Hui Wang,

My pi is all good now, deeply applicate！

[Mark Dunn (mdunn-home)]

I have a PI 4 (4GB)

I loaded and installed the arm64 eoan
USB didn't work, ssh did

I set total_mem=1024
USB worked

I set total_mem=3072
USB failed

I set total_mem=1024 and loaded the linux image:
wget https://people.canonical.com/~hwang4/rpiv2/arm64/linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
wget https://people.canonical.com/~hwang4/rpiv2/arm64/linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb

sudo dpkg -i linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo dpkg -i linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo reboot

USB Worked

I commented out the total_mem=3072
USB failed

I believe the following will help:

In the raspberry pi git (4.19.y)
https://github.com/raspberrypi/linux/issues/3093

hitmoon commented on 12 Aug
    "I've created a trivial patch to add bounce buffers on ARM64 for pcie-bcrmstb.
    pcie-brcmstb-bounce64.patch.zip

    I tried this patch, it works for me!
    All 4G memory is alive now, COOL !! :-)
    Thanks @yaroslavros !

This fixed my linux image for my home rolled 19.04 ubuntu so I hope it fixes yours

[Hui Wang (hui.wang)]

reply Mark Dunn,

The kernel you wget and installed already included the patch for 3093, so in theory, after installed the new kernel, the usb should work with 4G ram.

Please verify the kernel you are running is the new kernel, please upload the output of 'uname -a' and dmesg.

[Mark Dunn (mdunn-home)]

Sorry, my mistake I missed this:

Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.3.0-1009-raspi2)
/etc/kernel/postinst.d/zz-flash-kernel:

I have proposed in my sources.list so it ignored your older version, I will retry from scratch

[Mark Dunn (mdunn-home)]

hmm, not what I expected...

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1008-raspi2 #9-Ubuntu SMP Fri Oct 18 13:26:35 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

total_mem=3072 still fixes it

[Hui Wang (hui.wang)]

If you install the modules and kernel in the #26 successfully, the 'uname -a' will show newupdate.

But I can't find the "newupdate" from the output of yours.

And those patches are not merged to ubuntu kernel yet, so if you install the kernel from ubuntu sources, the usb host issue is not fixed.

[Mark Dunn (mdunn-home)]

Thanks.

ubuntu@ubuntu:~$ sudo dpkg -i linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
(Reading database ... 97816 files and directories currently installed.)
Preparing to unpack linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb ...
Unpacking linux-image-5.3.0-1008-raspi2 (5.3.0-1008.9+newupdate) over (5.3.0-1008.9+newupdate) ...
Setting up linux-image-5.3.0-1008-raspi2 (5.3.0-1008.9+newupdate) ...
Processing triggers for linux-image-5.3.0-1008-raspi2 (5.3.0-1008.9+newupdate) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.3.0-1008-raspi2
Using DTB: bcm2711-rpi-4-b.dtb
Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/broadcom/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.
Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/broadcom/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.
flash-kernel: deferring update (trigger activated)
/etc/kernel/postinst.d/zz-flash-kernel:
Using DTB: bcm2711-rpi-4-b.dtb
Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/broadcom/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.
Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/broadcom/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.
flash-kernel: deferring update (trigger activated)
Processing triggers for flash-kernel (3.98ubuntu5) ...
Using DTB: bcm2711-rpi-4-b.dtb
Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/broadcom/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.
flash-kernel: installing version 5.3.0-1008-raspi2
Taking backup of vmlinuz.
Installing new vmlinuz.
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.
Taking backup of initrd.img.
Installing new initrd.img.
Generating boot script u-boot image... done.
Taking backup of boot.scr.
Installing new boot.scr.
Taking backup of bcm2711-rpi-4-b.dtb.
Installing new bcm2711-rpi-4-b.dtb.

ubuntu@ubuntu:~$ sudo dpkg -i linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
(Reading database ... 97816 files and directories currently installed.)
Preparing to unpack linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb ...
Unpacking linux-modules-5.3.0-1008-raspi2 (5.3.0-1008.9+newupdate) over (5.3.0-1008.9+newupdate) ...
Setting up linux-modules-5.3.0-1008-raspi2 (5.3.0-1008.9+newupdate) ...
Processing triggers for linux-image-5.3.0-1008-raspi2 (5.3.0-1008.9+newupdate) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.3.0-1008-raspi2
Using DTB: bcm2711-rpi-4-b.dtb
Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/broadcom/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb
Taking backup of bcm2711-rpi-4-b....

[Mark Dunn (mdunn-home)]

OK, with your new "roll up" things are looking quite good, however your config.txt contains
    dtoverlay=vc4-fkms-v3d
I can also see the matching device tree binary object
    vc4-fkms-v3d.dtbo
In
    /boot/firmware/overlays

I can see
    /lib/modules/5.3.0-1008-raspi2/kernel/drivers/gpu/drm/vc4/vc4.ko
But I cannot see
    /lib/modules/5.3.0-1008-raspi2/kernel/drivers/gpu/drm/v3d/v3d.ko

This is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster.

Have I failed to load your linux-modules properly or is it missing?

I think the
    .../linux/arch/arm64/boot/dts/overlays/vc4-fkms-v3d-overlay.dts
is worth checking.

[Hui Wang (hui.wang)]

With the newupdate kernel, you could delete or comment out the "dtoverlay=vc4-fkms-v3d" on rpi4/3/2, then the system will use the fb driver of bcm2708_fb, this will not load the vc4 drm driver.

And to install the newupdate kernel,
you should install linux-modules-xxx.deb first
then install linux-images-xxx.deb.

[Mark Dunn (mdunn-home)]

Thank you for your help so far...

I want (and I have got)
    dtoverlay=vc4-fkms-v3d
I want (and I have got) the vm4 drm driver
     /lib/modules/5.3.0-1008-raspi2/kernel/drivers/gpu/drm/vc4/vc4.ko

I want (but I do not have)
    /lib/modules/5.3.0-1008-raspi2/kernel/drivers/gpu/drm/v3d/v3d.ko

Please could you ensure this file is included in the
    linux-modules-xxx.deb ?

[Hui Wang (hui.wang)]

OK, got it, will enable the module of v3d.ko in the kernel of next release.

[Mark Dunn (mdunn-home)]

I have tried the v3d.ko with latest stable version of mesa
    19.2
Which works well. glxinfo is the application to show everything is working and it produces
     ...Accelerated: yes
for a fast graphical interface

However Chromium 78.0.3904.70 snap fails for some reason
I am using a workaround until it is fixed
   chromium -use-gl=egl

The chromium-browser 76.0.3809.100 (from ubuntu 19.04) worked OK

[Hui Wang (hui.wang)]

We have a bug to track the enabling of v3d.ko

https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876

[Adam Mierzwiak (adamvm)]

When will be available fix in packages from regular distribution - applied with apt update/upgrade?

[Avio (aviopene)]

I'm testing this new 5.3.0-1008-raspi2 kernel, USB works as expected but I get a lot of

> mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe

in dmesg and /dev/mmcblk0p1 and /dev/mmcblk0p2 don't show up after booting. Any workarounds for this? Thanks.

[Hui Wang (hui.wang)]

@Avio,

I could see "mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe" too, but didn't meet your problem.

After the system boot up, it will mount the mmcblk0p2 as rootfs and mount mmcblk0p1 as /boot/firmware. I don't know why you couldn't see mmcblk0p1/2. Could you use ethernent, if yes, you could upgrade the kernel to 1012, to do so:
sudo apt-get update
sudo apt install linux-image-5.3.0-1012-raspi2
sudo reboot

If you still can't see mmcblk0p1/p2, could you please upload the complete dmesg to lp?

thx.

[Avio (aviopene)]

Hi @hui.wang,

the RPi4 boots off the sdcard normally but then I use a USB3 enclosure with disks to assemble a RAID1 BTRFS device to be used as rootfs. At the end of the boot, there is no /dev/mmcblk0* device:

#> ls -ld /dev/m*
drwxr-xr-x 2 root root 80 Nov 30 15:42 /dev/mapper
crw------- 1 root root 10, 227 Nov 30 15:42 /dev/mcelog
crw-r----- 1 root kmem 1, 1 Nov 30 15:42 /dev/mem
crw------- 1 root root 10, 56 Nov 30 15:42 /dev/memory_bandwidth
drwxrwxrwt 2 root root 40 Nov 30 15:41 /dev/mqueue

Anyway, this is just "an annoyance" that makes just a bit harder to switch kernel, the real problem is this one:

Nov 29 10:36:05 raspippa kernel: [39364.240711] xhci_hcd 0000:01:00.0: WARN Cannot submit Set TR Deq Ptr
Nov 29 10:36:05 raspippa kernel: [39364.240725] xhci_hcd 0000:01:00.0: A Set TR Deq Ptr command is pending.
Nov 29 10:36:05 raspippa kernel: [39364.373694] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov 29 10:36:05 raspippa kernel: [39364.396405] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 29 10:36:35 raspippa kernel: [39394.961204] xhci_hcd 0000:01:00.0: WARN Cannot submit Set TR Deq Ptr
Nov 29 10:36:35 raspippa kernel: [39394.961218] xhci_hcd 0000:01:00.0: A Set TR Deq Ptr command is pending.
Nov 29 10:36:36 raspippa kernel: [39395.324521] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov 29 10:36:36 raspippa kernel: [39395.344764] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Nov 29 10:36:36 raspippa kernel: [39395.344789] sd 0:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 01 e1 20 4d 00 00 00 04 00 00 00
Nov 29 10:36:36 raspippa kernel: [39395.344813] blk_update_request: I/O error, dev sda, sector 8071957760 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0

According to this thread (https://bugzilla.kernel.org/show_bug.cgi?id=202541) every kernel >= 4.20 is affected and there's still no patch in 5.3. I'll try to go back to some 4.19.y kernel, I'm even prepared to lower the memory to 1 Gb, cause so far this raspberry hasn't had more than a day of consecutive uptime.

[Hui Wang (hui.wang)]

About the problem of "there is no /dev/mmcblk0* device", I checked your dmesg, there are two places are weird

the 1st one is about the raspberrypi-firmware, on my board, the dmesg will show:
[ 0.100540] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-08-15 12:03, variant start
[ 0.110122] raspberrypi-firmware soc:firmware: Firmware hash is 9f8431fb7839c7f00f52b81f5822ddab2b31d0db

And there are not errors about firmware, but your dmesg is different.

the 2nd one is about mmc-bcm2835 driver, your kernel always report: mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe

That is different from my board, on my board, it only reports that message once, Then the driver could get the clk successfully.

[Avio (aviopene)]

I'm now running a 2019-09-26-raspbian-buster-lite.img with 4.19.75-v7l+ kernel and /dev/mmcblk0* are correctly populated.

pi@raspberrypi:~ $ dmesg | grep firmware
[ 0.090391] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-09-24 17:34, variant start
[ 0.100110] raspberrypi-firmware soc:firmware: Firmware hash is cd3add54955f8fa065b414d8fc07c525e7ddffc8
[ 4.322157] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])

But I've also set total_mem=1024 to be on the safe side, so it may be related. I'll try to build an initramfs with BTRFS for this kernel and switch back to Ubuntu.

[Pete Heist (peteheist)]

I just wanted to report that USB is working for me with the 5.3.0-1014-raspi2 aarch64 kernel, but neither the keyboard not the mouse works at boot time when I have my mouse (a Microsoft Basic Optical Mouse v2.0) plugged in via my Apple USB keyboard's built-in USB hub.

I must disconnect the mouse from the keyboard and plug it straight into an open USB port on the Pi. Afterwards, I can then plug it back into the keyboard, and the keyboard and mouse both work fine until reboot.

That was confusing me into thinking that I was seeing this issue, when it's probably a little different. I don't have another hub to test to see if the same happens with all USB hubs.

[Hui Wang (hui.wang)]

I don't have the usb hub which is integrated into the keyboard, I just have two normal usb hubs.

I plugged both the keyboard and the mouse into the hub and plug the hub into a rpi4's usb port, power up, both keyboard and mouse could work with 1014 aarch64 kernel, I could not reproduce your problem.

[Hui Wang (hui.wang)]

@Pete,

Looks like someone else met the same issue, and already opened a bug in the upstream, let's track the upstream bug, after it is fixed by upstream, we will integrate the fix in the ubuntu kernel.

https://github.com/raspberrypi/linux/issues/3334

thx.