I believe this is fixed in Focal. Can you check if this is still an
issue for you with a current image from
http://cdimage.ubuntu.com/releases/20.04/release/?
After rebooting a Pi running a current Focal image I get (on the
connected host):
May 15 15:28:51 smeagol kernel: [ 3824.785702] usb 1-2: new high-speed USB
device number 28 using xhci_hcd
May 15 15:28:56 smeagol kernel: [ 3829.845566] xhci_hcd 0000:00:14.0: Timeout
while waiting for setup device command
May 15 15:29:02 smeagol kernel: [ 3835.221286] xhci_hcd 0000:00:14.0: Timeout
while waiting for setup device command
May 15 15:29:02 smeagol kernel: [ 3835.429202] usb 1-2: device not accepting
address 28, error -62
May 15 15:29:02 smeagol kernel: [ 3835.557210] usb 1-2: new high-speed USB
device number 29 using xhci_hcd
May 15 15:29:07 smeagol kernel: [ 3840.597042] xhci_hcd 0000:00:14.0: Timeout
while waiting for setup device command
May 15 15:29:12 smeagol kernel: [ 3845.972785] xhci_hcd 0000:00:14.0: Timeout
while waiting for setup device command
May 15 15:29:13 smeagol kernel: [ 3846.180713] usb 1-2: device not accepting
address 29, error -62
May 15 15:29:13 smeagol kernel: [ 3846.180894] usb usb1-port2: attempt power
cycle
May 15 15:29:13 smeagol kernel: [ 3846.832715] usb 1-2: new high-speed USB
device number 30 using xhci_hcd
May 15 15:29:18 smeagol kernel: [ 3851.988499] usb 1-2: device descriptor
read/64, error -110
May 15 15:29:34 smeagol kernel: [ 3867.603793] usb 1-2: device descriptor
read/64, error -110
May 15 15:29:34 smeagol kernel: [ 3867.839763] usb 1-2: new high-speed USB
device number 31 using xhci_hcd
May 15 15:29:39 smeagol kernel: [ 3872.979541] usb 1-2: device descriptor
read/64, error -110
And after loading g_{cdc,ether} on the Pi:
May 15 15:29:55 smeagol kernel: [ 3888.702904] usb usb1-port2: unable to
enumerate USB device
May 15 15:30:22 smeagol kernel: [ 3915.165600] usb 1-2: new high-speed USB
device number 32 using xhci_hcd
May 15 15:30:22 smeagol kernel: [ 3915.186797] usb 1-2: New USB device found,
idVendor=0525, idProduct=a4a2, bcdDevice= 5.04
May 15 15:30:22 smeagol kernel: [ 3915.186805] usb 1-2: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
May 15 15:30:22 smeagol kernel: [ 3915.186811] usb 1-2: Product: RNDIS/Ethernet
Gadget
May 15 15:30:22 smeagol kernel: [ 3915.186815] usb 1-2: Manufacturer: Linux
5.4.0-1010-raspi with fe980000.usb
May 15 15:30:22 smeagol kernel: [ 3915.192463] cdc_ether 1-2:1.0 usb0: register
'cdc_ether' at usb-0000:00:14.0-2, CDC Ethernet Device, a6:b3:33:a5:9e:5c
May 15 15:30:22 smeagol kernel: [ 3915.225267] cdc_ether 1-2:1.0
enxa6b333a59e5c: renamed from usb0
And the connected host reports:
$ lsusb
<SNIP>
Bus 001 Device 032: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB
Ethernet/RNDIS Gadget
<SNIP>
So from my POV this looks as good as it gets. Please confirm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871977
Title:
g_ether not working after reboot
Status in linux-raspi package in Ubuntu:
Incomplete
Status in linux-raspi2 package in Ubuntu:
Incomplete
Status in linux-raspi2 source package in Eoan:
New
Status in linux-raspi source package in Focal:
Confirmed
Bug description:
There is an issue with g_ether after warm reboot.
Hardware I used for testing:
Thinkpad L470 + Dock, Ubuntu 19.10
USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter
Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu
19.10
==============================
it seems like whenever I reboot my Pi, USB gadget port is not detected. How
to reproduce:
1) make sure g_ether works on Pi 4
2) make sure cdc_ether works on L470, as in dmesg it shows...
[112961.147030] usb 1-3.2: new high-speed USB device number 11 using xhci_hcd
[112961.237399] usb 1-3.2: New USB device found, idVendor=045e,
idProduct=0301, bcdDevice= 5.03
[112961.237406] usb 1-3.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[112961.237411] usb 1-3.2: Product: USB Adapter
[112961.237414] usb 1-3.2: Manufacturer: Raspberry Pi
[112961.237418] usb 1-3.2: SerialNumber: ***MASKED***
[112961.245067] cdc_ether 1-3.2:1.0 eth1: register 'cdc_ether' at
usb-0000:00:14.0-3.2, CDC Ethernet Device, ***MASKED***
3) verify IP connectivity works from L470 to Pi 4.
4) reboot Pi 4; on L470 it shows:
[113343.783925] usb 1-3.2: USB disconnect, device number 11
[113343.784164] cdc_ether 1-3.2:1.0 eth1: unregister 'cdc_ether'
usb-0000:00:14.0-3.2, CDC Ethernet Device
5) wait for Pi 4 to become available (I use wifi on Pi 4 + ssh on L470)
==============================
Expected: Pi4 should show up to L470 as USB ethernet gadget after warm reboot
Actual: g_ether is loaded on Pi4 but L470 does not detect it
Workaround: unplug Pi4 and plug in again, it will work; given that I am
using Y-cable, unplugging will not power down Pi 4.
Concern: lose connectivity that needs human intervention to correct, i.e.
cannot do it remotely.
Note: I remember it is detected okay before I file for bug #1861070,
not sure if it is related or not. using g_cdc should be the same, but
not separately tested.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1871977/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
