RB1: device not visible from adb after USB unplug/replug

[davegarthsimpson]

I am using an RB1 flashed with a WiFi & ADB image with qdl on Mac OS 15.0.1 arm.

When the RB1 starts up, plugged into power, and to the Mac via USB-C and Micro USB, it is not listed in the output of adb devices in Mac terminal.

Connecting to the RB1 shell via minicom, and running systemctl daemon-reload && systemctl restart adbd.service, resolves the problem, and subsequently the device is visible from Mac terminal with adb devices.

Unplugging and replugging the RB1, the problem re-presents.

Outside of flashing the device no other modifications have been made.

[lool]

I think I saw this too in the past, I tried today, but could only reproduce some problematic behavior today.

From macOS, I've flashed our latest daily using trixie + 6.15-rc6 on a RB1, logged in via serial, setup wifi. I should note I'm using an USB hub between the mac and the RB1, with a type-A to type-C cable, so it's probably helping with type-C negotiations.

I could then run adb shell, reboot, run adb shell, reboot, run adb shell – seems to work.

However, if I unplug, replug, I can't adb shell anymore. If I restart adbd (from the serial console), adb shell works again. If I unplug, replug, reboot, adb shell works too.

I don't see any kernel message when I unplug/replug the type-C port, however at the time of sudo systemctl restart adbd, I get:

[  207.463952] dwc3 4e00000.usb: request 00000000241a732f was not queued to ep0out
[  207.542482] ffs_data_put(): freeing
[  207.562227] unloading
[  207.692079] file system registered
[  207.805890] read descriptors
[  207.808954] bcdVersion must be 0x0100, stored in Little Endian order. Userspace driver should be fixed, accepting 0x0001 for compatibility.
[  207.821605] bcdVersion must be 0x0100, stored in Little Endian order. Userspace driver should be fixed, accepting 0x0001 for compatibility.
[  207.834215] read strings

so this might be an issue with USB link detection; I personally don't think I can debug this further.

[lool]

I tested again with:

• board fully off, nothing plugged
• plug power
• press power button
• plug type-A to type-C cable to board
• adb shell

And that worked, so I'll retitle the bug to only cover unplug/replug as an issue, but @davegarthsimpson please correct me if I'm wrong, perhaps you're hitting two separate issues.

[ndechesne]

@lumag , any thoughts/ideas?

[lumag]

@lool which image can I flash to reproduce the issue?

[lool]

@lool which image can I flash to reproduce the issue?

@lumag The daily should work fine:
https://github.com/qualcomm-linux/qcom-deb-images/actions/workflows/build-daily.yml
The build from yesterday (today still building):
https://quic-yocto-fileserver-1029608027416.us-central1.run.app/qualcomm-linux/qcom-deb-images/15132935812-1/

[loicpoulain]

Note that the same issue is not reproducible with Yocto based build. I will check the diff related to the adb daemon.