Unitek Y-3470B USB dongle is not detected when removed/inserted again |
|||||||||||
Issue descriptionChrome Version: 68 / 10718.63.0 / 68.0.3440.76 (Test Image) OS: Chrome OS DUT: Astronaut (Coral uni-build) Ethernet to USB Dongle: 0bda:8153 (RTL8153B) What steps will reproduce the problem? (1) Recover the dut with 10718.63.0 (2) Plug ethernet to usb dongle (while ethernet cable is connected to dongle) (3) Ethernet interface is not detected. What is the expected result? Ethernet interface should get detected. What happens instead? Ethernet interface is not detected. Dongle does not get power (leds don't blink). Note: Verified for loose contacts and there is none. When un-plugged and plugged back it gets detected. Two out of three times, this issue can be reproduced.
,
Jul 24
,
Jul 24
,
Jul 24
Sorry, I'm going to shorten the title so it's easier to read.
This sounds more like a problem with USB host controller than USB ethernet dongle.
Can I get:
1) the corresponding /var/log/messages starting with the kernel booting and ending with the dongle being detected?
2) "lsusb -v -d 0bda:8153" output for the offending dongle
I've appended (2) for an RTL8153B (Unitek Y-3470B) dongle.
localhost ~ # lsusb -v -d 0bda:8153
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x8153
bcdDevice 31.00
iManufacturer 1 UNITEK
iProduct 2 UNITEK Y-3470B
iSerial 6 001000001
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 57
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 72mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 8
bMaxBurst 0
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 98
bNumInterfaces 2
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 72mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Communications Control
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 3 00E04CF00043
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 8
bMaxBurst 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x02
Latency Tolerance Messages (LTM) Supported
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 2
Lowest fully-functional device speed is High Speed (480Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0010
(Bus Powered)
Latency Tolerance Messaging (LTM) Enabled
,
Jul 24
Please find attached logs for your reference. [ 8468.632191] r8152 2-5:1.0 eth0: v1.09.9 [ 8468.653846] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8470.901563] r8152 2-5:1.0 eth0: Stop submitting intr, status -71 [ 8471.598177] xhci_hcd 0000:00:15.0: Cannot set link state. [ 8471.598211] usb usb2-port5: cannot disable (err = -32) [ 8471.598224] usb 2-5: USB disconnect, device number 11 [ 8475.036270] usb 2-5: new SuperSpeed USB device number 12 using xhci_hcd [ 8475.047552] usb 2-5: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00 [ 8475.047572] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 8475.047582] usb 2-5: Product: UNITEK Y-3470B [ 8475.047590] usb 2-5: Manufacturer: UNITEK [ 8475.047597] usb 2-5: SerialNumber: 001000001 [ 8475.160548] usb 2-5: reset SuperSpeed USB device number 12 using xhci_hcd [ 8475.204452] r8152 2-5:1.0 eth0: v1.09.9 [ 8475.232705] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8477.237401] r8152 2-5:1.0 eth0: Stop submitting intr, status -71 [ 8477.936217] xhci_hcd 0000:00:15.0: Cannot set link state. [ 8477.936251] usb usb2-port5: cannot disable (err = -32) [ 8477.936265] usb 2-5: USB disconnect, device number 12 [ 8481.417109] usb 2-5: new SuperSpeed USB device number 13 using xhci_hcd [ 8481.428376] usb 2-5: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00 [ 8481.428396] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 8641.508201] usb 2-2: Manufacturer: Fibocom [ 8641.508208] usb 2-2: SerialNumber: 004999010640000 [ 8641.568165] cdc_mbim 2-2:1.0: setting rx_max = 16384 [ 8641.570485] cdc_mbim 2-2:1.0: cdc-wdm0: USB WDM device [ 8641.574817] cdc_mbim 2-2:1.0 wwan0: register 'cdc_mbim' at usb-0000:00:15.0-2, CDC MBIM, 32:69:be:96:a8:35 [ 8641.582413] cdc_acm 2-2:1.2: ttyACM0: USB ACM device [ 8641.593630] cdc_acm 2-2:1.4: ttyACM1: USB ACM device [ 8641.601587] cdc_acm 2-2:1.6: ttyACM2: USB ACM device [ 8708.413448] usb 2-5: new SuperSpeed USB device number 16 using xhci_hcd [ 8708.424880] usb 2-5: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00 [ 8708.424900] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 8708.424910] usb 2-5: Product: UNITEK Y-3470B [ 8708.424918] usb 2-5: Manufacturer: UNITEK [ 8708.424926] usb 2-5: SerialNumber: 001000001 [ 8708.538741] usb 2-5: reset SuperSpeed USB device number 16 using xhci_hcd [ 8708.583773] r8152 2-5:1.0 eth0: v1.09.9 [ 8708.608485] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8711.612418] r8152 2-5:1.0 eth0: carrier on [ 8711.612504] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready /var/log/messages: 2018-07-24T14:10:30.664123-07:00 NOTICE kernel: [ 0.000000] Linux version 4.4.132-14159-g1212a1a7013c (chrome-bot@cros-beefy110-c2) (Chromium OS 7.0_pre328903_p20180425-r5 clang version 7.0.0 (/var/cache/chromeos-cache/distfiles/host/egit-src/clang.git e7408fe366bb18923fa360b069b4e4566203f34f) (/var/cache/chromeos-cache/distfiles/host/egit-src/llvm.git 95561668f063fbcb8195bde05ecede721ece4ba4) (based on LLVM 7.0.0svn)) #1 SMP PREEMPT Mon Jul 23 22:27:35 PDT 2018 2018-07-24T14:10:30.664125-07:00 INFO kernel: [ 0.000000] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3737600 verity payload=PARTUUID=83c9130a-5586-a441-be7f-64aa8ca832b0/PARTNROFF=1 hashtree=PARTUUID=83c9130a-5586-a441-be7f-64aa8ca832b0/PARTNROFF=1 hashstart=3737600 alg=sha1 root_hexdigest=16257ad2a48b19768900e45a069963b4d57b3f0a salt=db75dcec248ff5c5bcafc234db978cc45c075e1cc3405cb5d5a25b62b40c33d6" noinitrd cros_debug vt.global_cursor_default=0 kern_guid=83c9130a-5586-a441-be7f-64aa8ca832b0 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic i915.preliminary_hw_support=1
,
Jul 25
Joyce, Who at Techtop or Unitech can help debug this? I personally tested and reproduced this failure - this is the 3rd or 4th Y-3470B unit where different people have reproduced this behavior: unplug the device and no notification/event occurs when plugging it back in shortly after. Wait a minute (or a day), plug the same dongle in and the dongle is recognized like normal. I would like to blame this on the Intel ApolloLake USB host controller but: o only reproducible with Y-3470B dongle.[1] o reproduced on "fizz" (kabyLake-U/R chromebox)[2] [1] Other RTL8153 dongles don't exhibit this behavior. I've repeated the same test on the same "astronaut" chromebook with an RTL8153B prototype board sent by Realtek (in 2015) and an Anker A7611 (RTL8153) dongle. Neither of these dongles could reproduce the problem. We tried 5-6 times and Y-3470B will reproduce in 2-3 attempts. [2] "astronaut" == "Acer Chromebook 11 (C732, C732T, C732L & C732LT)" which is an Intel ApolloLake chipset.
,
Jul 25
Sorry, in comment #6 [2] was supposed to be a bug that I currently can't find. However, I am NOT able to reproduce with the "sample unitek" dongles TechTop sent me in December 2017. I tested on the same chromebook as before. Joyce, what is different between unitek samples (manufactured before December 22 2017) and the Y-3470B units shipped to Google around May 27, 2018?
,
Jul 25
Just in case it's different, here is "lsusb -v" output for sample unit shipped to Google on Dec 22, 2017.
localhost ~ # lsusb -v -d 0bda:8153
Bus 002 Device 005: ID 0bda:8153 Realtek Semiconductor Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x8153
bcdDevice 31.00
iManufacturer 1 Realtek
iProduct 2 USB 10/100/1000 LAN
iSerial 6 001000001
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 57
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 72mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 8
bMaxBurst 0
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 98
bNumInterfaces 2
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 72mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Communications Control
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 3 00E04C30AA0C
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 8
bMaxBurst 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 3
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x02
Latency Tolerance Messages (LTM) Supported
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 2
Lowest fully-functional device speed is High Speed (480Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0010
(Bus Powered)
Latency Tolerance Messaging (LTM) Enabled
,
Jul 25
grundler@ - should we hold off on replacing old ethernet dongles in the lab with the new RTL8153B dongles? Effort is tracked here b/111653827
,
Jul 26
Harpeet, no, I don't have evidence lab use is affected by this issue. Or are dongles being routinely removed/inserted in the test lab?
,
Aug 2
I've started inspecting devices (5 so far: 2 bad, 3 good) and don't see anything (under a microscope) obviously wrong with the "bad" devices. The only common factor is Z1816 mfg date code is on both bad units. All three good units had different date codes (Z1745 or Z1809). Sorry - Photos are google-internal access only: https://drive.google.com/drive/folders/17VpKYCSpzmyBxwSPZX7PSg17OqknoVgJ?usp=sharing
,
Aug 3
Dinesh just gave me two Y-3470B units which "FAILED" in the Chrome OS test lab: (a) MAC 00:E0:4C:F0:04:66 (b) MAC 00:E0:4C:F0:00:03 I plugged (a) into a production chell (HP Chromebook 13 G1) several times: 1) nothing detected by the chell. I double checked that the dongle was correctly and fully inserted. Removed - no events detected again. 2) dmesg output was normal: [ 202.799513] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd [ 202.810884] usb 2-3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00 [ 202.810899] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 202.810909] usb 2-3: Product: UNITEK Y-3470B [ 202.810916] usb 2-3: Manufacturer: UNITEK [ 202.810923] usb 2-3: SerialNumber: 001000001 [ 202.853779] usbcore: registered new interface driver r8152 [ 202.857740] usbcore: registered new interface driver cdc_ether [ 202.861656] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 202.956823] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd [ 202.998296] r8152 2-3:1.0 eth0: v1.09.9 [ 203.052403] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 203.129350] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 203.148985] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 204.488398] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 206.085270] r8152 2-3:1.0 eth0: carrier on [ 206.085293] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 210.193564] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 252.199521] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 291.688258] r8152 2-3:1.0 eth0: Stop submitting intr, status -71 [ 291.779051] usb 2-3: USB disconnect, device number 2 3) Nothing again for both insertion and removal 4) dmesg for 4th insertion: [ 338.307324] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd [ 338.318931] usb 2-3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00 [ 338.318995] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 338.319030] usb 2-3: Product: UNITEK Y-3470B [ 338.319054] usb 2-3: Manufacturer: UNITEK [ 338.319075] usb 2-3: SerialNumber: 001000001 [ 338.424771] usb 2-3: reset SuperSpeed USB device number 3 using xhci_hcd [ 338.469800] r8152 2-3:1.0 eth0: v1.09.9 [ 338.513991] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 338.552235] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 338.565404] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 341.521863] r8152 2-3:1.0 eth0: carrier on [ 341.521891] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready (and still inserted now) Seems like on the chell, it's alternating between "normal" and "nothing". I have no idea what might cause that.
,
Aug 4
Issue 863235 has been merged into this issue.
,
Aug 23
The lab is also running into the same issues...
,
Aug 23
Issue 877261 has been merged into this issue. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by dsunk...@chromium.org
, Jul 24