Public bug reported:
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.
** Affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
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-raspi2 package in Ubuntu:
New
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-raspi2/+bug/1871977/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
