New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 792501 link

Starred by 2 users
Status: Archived
Owner:
█ denniswu@chromium.org
Last visit > 30 days ago
Closed: Dec 13
Cc:
█ frankhu@chromium.org
█ cvintila@chromium.org
marcore@chromium.org
█ kotah@chromium.org
█ egemih@chromium.org
█ katierh@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Cfm client side issue: Camera/ Audio USB devices lose signal

Project Member Reported by marcore@chromium.org, Dec 6 2017 
ChromeOS version: 61.0.3163.124
Cfm device model: ASUS Chromebox CN62
Case#: 14334376
Customer info: https://drive.google.com/open?id=1EJYfwldrAw3P5-8qyC7JZyXDFgfNwsx7WOoxyEvq4NI

Description: the customer lost camera connection (Logitech PTZ via USB) mid-meeting, and upon investigation after the meeting ended, the audio connection (Biamp CR-1C processor via USB), was also not showing any sign on receiving a signal.
Time of incident: Appr. 12p this afternoon (11/30/17)


Steps to reproduce:
1) connect to a meeting via calendar

Current Behavior / Reproduction: 
lost video and audio
Expected Behavior: 
continue to have video and audio

Drive link to logs: https://drive.google.com/open?id=1-IqPJoo2xjj3RV3A9aCjwPu9LyKTQZOK

In /var/log/messages you can see the PTZ USB reset more than once, example:

2017-11-30T12:08:31.014969-08:00 ERR kernel: [34920.629558] hid-generic 0003:046D:0853.000D: can't reset device, 0000:00:14.0-5.3/input2, status -32
2017-11-30T12:08:31.346967-08:00 INFO kernel: [34920.960999] usb 1-5.3: USB disconnect, device number 13
2017-11-30T12:08:36.234971-08:00 INFO kernel: [34925.852966] usb 1-5.3: new high-speed USB device number 14 using xhci_hcd
2017-11-30T12:08:36.328587-08:00 INFO kernel: [34925.944986] usb 1-5.3: New USB device found, idVendor=046d, idProduct=0853
2017-11-30T12:08:36.328615-08:00 INFO kernel: [34925.945011] usb 1-5.3: New USB device strings: Mfr=0, Product=2, SerialNumber=1
2017-11-30T12:08:36.330345-08:00 INFO kernel: [34925.945028] usb 1-5.3: Product: PTZ Pro Camera
2017-11-30T12:08:36.330370-08:00 INFO kernel: [34925.945041] usb 1-5.3: SerialNumber: 21E93125

A little later in log "ERR kernel: [35741.591725] hub 1-5:1.0: port 3 disabled by hub (EMI?), re-enabling..."

Comment 1 by tovep@chromium.org, Dec 6 2017

Owner: denniswu@chromium.org
Status: Assigned (was: Untriaged)

Comment 2 by tovep@chromium.org, Dec 6 2017

Labels: -M-61 M-64

Comment 3 by mzhuo@chromium.org, Dec 7 2017 

Logitech PTZ is not stable. I have one logitech PTZ  directly connected to Guado+kepler  running the latest R64 image. After rebooting Guado it fails to be enumerated. 

log on Guado 100.123.174.2
ocalhost ~ # exit
/debug-logs_20171206-215442.tgz.100.123.174.2: No such file or directory
Cli to be executed: scp root@100.123.174.2:/tmp/debug-logs_20171206-215442.tgz  /debug-logs_20171206-215442.tgz.100.123.174.2 Cli to be executed: cat /etc/lsb-release  | grep CHROMEOS_RELEASE_BUILDER_PATH
localhost ~ # cat /etc/lsb-release  | grep CHROMEOS_RELEASE_BUILDER_PATH

cat /etc/lsb-release  | grep CHROMEOS_RELEASE_BUILDER_PATH
CHROMEOS_RELEASE_BUILDER_PATH=guado-release/R64-10176.5.0
localhost ~ # exit
Cli to be executed: lsusb -t
localhost ~ # lsusb -t

lsusb -t

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 2: Dev 8, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 8, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 8, If 2, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 8, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 8, If 4, Class=Application Specific Interface, Driver=, 12M
    |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 10, If 0, Class=Vendor Specific Class, Driver=udl, 480M
    |__ Port 4: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 4: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

Cli to be executed: ls -latr /var/spool/crash
localhost ~ # ls -latr /var/spool/crash

ls -latr /var/spool/crash
total 8
drwxr-xr-x 5 root root 4096 Nov 30 23:43 ..
drwxr-xr-t 2 root root 4096 Dec  6 17:27 .
localhost ~ # exit
localhost ~ # uptime -s
uptime -s
2017-12-06 15:17:22
localhost ~ # exit
Cli to be executed: awk '/2017-12-06T15:17/,0' /var/log/messages | grep -E 'USB disconnect|usb 2-|usb 1-|ERR kernel:|ERR video'
 localhost ~ # awk '/2017-12-06T15:17/,0' /var/log/messages | grep -E 'USB disconnect|usb 2-|usb 1-|ERR kernel:|ERR video'

nect|usb 2-|usb 1-|ERR kernel:|ERR video'ges | grep -E 'USB discon 

2017-12-06T15:17:25.261941-08:00 ERR kernel: [    1.394547] i8042: No controller found
2017-12-06T15:17:25.262032-08:00 ERR kernel: [    1.409314] Warning: unable to open an initial console.
2017-12-06T15:17:25.262091-08:00 ERR kernel: [    1.412228] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
2017-12-06T15:17:25.262103-08:00 INFO kernel: [    1.545973] usb 1-3: new high-speed USB device number 2 using xhci_hcd
2017-12-06T15:17:25.262107-08:00 INFO kernel: [    1.710326] usb 1-3: New USB device found, idVendor=058f, idProduct=6254
2017-12-06T15:17:25.262108-08:00 INFO kernel: [    1.710349] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2017-12-06T15:17:25.262119-08:00 INFO kernel: [    1.865220] usb 1-4: new full-speed USB device number 3 using xhci_hcd
2017-12-06T15:17:25.262128-08:00 INFO kernel: [    2.030196] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
2017-12-06T15:17:25.262129-08:00 INFO kernel: [    2.030209] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2017-12-06T15:17:25.262145-08:00 INFO kernel: [    2.183420] usb 1-5: new high-speed USB device number 4 using xhci_hcd
2017-12-06T15:17:40.326111-08:00 ERR kernel: [   17.348917] usb 1-5: device descriptor read/64, error -110
2017-12-06T15:17:40.427124-08:00 ERR kernel: [   17.449893] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
2017-12-06T15:17:40.580111-08:00 INFO kernel: [   17.603043] usb 1-5: new high-speed USB device number 5 using xhci_hcd
2017-12-06T15:17:55.733109-08:00 ERR kernel: [   32.768392] usb 1-5: device descriptor read/64, error -110
2017-12-06T15:17:55.834111-08:00 ERR kernel: [   32.869334] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
2017-12-06T15:17:55.987112-08:00 INFO kernel: [   33.022495] usb 1-5: new high-speed USB device number 6 using xhci_hcd
2017-12-06T15:18:01.000233-08:00 ERR kernel: [   38.040486] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-12-06T15:18:06.418087-08:00 ERR kernel: [   43.461836] usb 1-5: device not accepting address 6, error -62
2017-12-06T15:18:06.571110-08:00 INFO kernel: [   43.615042] usb 1-5: new high-speed USB device number 7 using xhci_hcd
2017-12-06T15:18:11.576210-08:00 ERR kernel: [   48.625007] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-12-06T15:18:16.994110-08:00 ERR kernel: [   54.046385] usb 1-5: device not accepting address 7, error -62
2017-12-06T15:18:16.994132-08:00 ERR kernel: [   54.046451] hub 1-0:1.0: unable to enumerate USB device on port 5
2017-12-06T15:18:17.251075-08:00 INFO kernel: [   54.303585] usb 1-2: new full-speed USB device number 8 using xhci_hcd
2017-12-06T15:18:17.415038-08:00 INFO kernel: [   54.468291] usb 1-2: not running at top speed; connect to a high speed hub
2017-12-06T15:18:17.417090-08:00 INFO kernel: [   54.470232] usb 1-2: New USB device found, idVendor=18d1, idProduct=8001
2017-12-06T15:18:17.417122-08:00 INFO kernel: [   54.470256] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2017-12-06T15:18:17.417127-08:00 INFO kernel: [   54.470274] usb 1-2: Product: Hangouts Meet speakermic
2017-12-06T15:18:17.417131-08:00 INFO kernel: [   54.470287] usb 1-2: Manufacturer: Google Inc.
2017-12-06T15:18:17.417134-08:00 INFO kernel: [   54.470299] usb 1-2: SerialNumber: GATRW17120016
2017-12-06T15:18:17.495114-08:00 INFO kernel: [   54.547847] usb 1-3.1: new full-speed USB device number 9 using xhci_hcd
2017-12-06T15:18:17.585017-08:00 INFO kernel: [   54.638315] usb 1-3.1: not running at top speed; connect to a high speed hub
2017-12-06T15:18:17.598028-08:00 INFO kernel: [   54.651703] usb 1-3.1: New USB device found, idVendor=266e, idProduct=0110
2017-12-06T15:18:17.598040-08:00 INFO kernel: [   54.651712] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2017-12-06T15:18:17.598041-08:00 INFO kernel: [   54.651719] usb 1-3.1: Product: SiS HID Touch Controller
2017-12-06T15:18:17.598042-08:00 INFO kernel: [   54.651724] usb 1-3.1: Manufacturer: USBest Technology
2017-12-06T15:18:17.675016-08:00 INFO kernel: [   54.727823] usb 1-3.3: new high-speed USB device number 10 using xhci_hcd
2017-12-06T15:18:17.761018-08:00 INFO kernel: [   54.813939] usb 1-3.3: New USB device found, idVendor=17e9, idProduct=016b
2017-12-06T15:18:17.761029-08:00 INFO kernel: [   54.813948] usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2017-12-06T15:18:17.761030-08:00 INFO kernel: [   54.813955] usb 1-3.3: Product: MIMO VUE HD
2017-12-06T15:18:17.761031-08:00 INFO kernel: [   54.813959] usb 1-3.3: Manufacturer: DisplayLink
2017-12-06T15:18:17.761031-08:00 INFO kernel: [   54.813963] usb 1-3.3: SerialNumber: MXACP17040006
2017-12-06T15:18:19.383084-08:00 ERR kernel: [   56.437841] hda-intel 0000:00:1b.0: Applying patch firmware 'guado_alsa.fw'
localhost ~ #

Comment 4 by mzhuo@chromium.org, Dec 7 2017 

More log for Logitech PTZ Pro. After it fails to be enumerated it wont' recover after rebooting Guado. 
------------------/var/log/messages.4:2017-12-02T00:43:56.240299-08:00 INFO kernel: [    2.286326] usb 1-5: new high-speed USB device number 4 using xhci_hcd
/var/log/messages.4:2017-12-02T00:43:56.240300-08:00 ERR kernel: [   17.451776] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T00:43:56.240303-08:00 INFO kernel: [   17.705910] usb 1-5: new high-speed USB device number 5 using xhci_hcd
/var/log/messages.4:2017-12-02T00:43:56.240304-08:00 ERR kernel: [   32.871262] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T00:43:56.240305-08:00 INFO kernel: [   33.125355] usb 1-5: new high-speed USB device number 6 using xhci_hcd
/var/log/messages.4:2017-12-02T00:43:56.240310-08:00 ERR kernel: [   43.557700] usb 1-5: device not accepting address 6, error -62
/var/log/messages.4:2017-12-02T00:43:56.240310-08:00 INFO kernel: [   43.710900] usb 1-5: new high-speed USB device number 7 using xhci_hcd
/var/log/messages.4:2017-12-02T00:43:56.240315-08:00 ERR kernel: [   54.142244] usb 1-5: device not accepting address 7, error -62
/var/log/messages.4:2017-12-02T01:23:52.225359-08:00 INFO kernel: [    2.271456] usb 1-5: new high-speed USB device number 4 using xhci_hcd
/var/log/messages.4:2017-12-02T01:23:52.225360-08:00 ERR kernel: [   17.436841] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T01:23:52.225363-08:00 INFO kernel: [   17.691042] usb 1-5: new high-speed USB device number 5 using xhci_hcd
/var/log/messages.4:2017-12-02T01:23:52.225364-08:00 ERR kernel: [   32.856285] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T01:23:52.225366-08:00 INFO kernel: [   33.110456] usb 1-5: new high-speed USB device number 6 using xhci_hcd
/var/log/messages.4:2017-12-02T01:23:52.225371-08:00 ERR kernel: [   43.541854] usb 1-5: device not accepting address 6, error -62
/var/log/messages.4:2017-12-02T01:23:52.225372-08:00 INFO kernel: [   43.694953] usb 1-5: new high-speed USB device number 7 using xhci_hcd
/var/log/messages.4:2017-12-02T01:23:52.225377-08:00 ERR kernel: [   54.126349] usb 1-5: device not accepting address 7, error -62
/var/log/messages.4:2017-12-02T01:26:40.065659-08:00 INFO kernel: [  222.380226] usb 1-5: new high-speed USB device number 12 using xhci_hcd
/var/log/messages.4:2017-12-02T01:26:55.218631-08:00 ERR kernel: [  237.545534] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T01:26:55.472647-08:00 INFO kernel: [  237.799678] usb 1-5: new high-speed USB device number 13 using xhci_hcd
/var/log/messages.4:2017-12-02T01:27:10.625645-08:00 ERR kernel: [  252.964990] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T01:27:10.879657-08:00 INFO kernel: [  253.219119] usb 1-5: new high-speed USB device number 14 using xhci_hcd
/var/log/messages.4:2017-12-02T01:27:21.307643-08:00 ERR kernel: [  263.655471] usb 1-5: device not accepting address 14, error -62
/var/log/messages.4:2017-12-02T01:27:21.460669-08:00 INFO kernel: [  263.808674] usb 1-5: new high-speed USB device number 15 using xhci_hcd
/var/log/messages.4:2017-12-02T01:27:31.883618-08:00 ERR kernel: [  274.240009] usb 1-5: device not accepting address 15, error -62
/var/log/messages.4:2017-12-02T15:14:58.069577-08:00 INFO kernel: [    2.286365] usb 1-5: new high-speed USB device number 4 using xhci_hcd
/var/log/messages.4:2017-12-02T15:14:58.069579-08:00 ERR kernel: [   17.451801] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T15:14:58.069582-08:00 INFO kernel: [   17.705929] usb 1-5: new high-speed USB device number 5 using xhci_hcd
/var/log/messages.4:2017-12-02T15:14:58.069583-08:00 ERR kernel: [   32.871250] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T15:14:58.069584-08:00 INFO kernel: [   33.125388] usb 1-5: new high-speed USB device number 6 using xhci_hcd
/var/log/messages.4:2017-12-02T15:14:58.069589-08:00 ERR kernel: [   43.557736] usb 1-5: device not accepting address 6, error -62
/var/log/messages.4:2017-12-02T15:14:58.069590-08:00 INFO kernel: [   43.710935] usb 1-5: new high-speed USB device number 7 using xhci_hcd
/var/log/messages.4:2017-12-02T15:14:58.069593-08:00 ERR kernel: [   54.142280] usb 1-5: device not accepting address 7, error -62
/var/log/messages.4:2017-12-02T15:17:37.197614-08:00 INFO kernel: [    2.185198] usb 1-5: new high-speed USB device number 4 using xhci_hcd
/var/log/messages.4:2017-12-02T15:17:37.197616-08:00 ERR kernel: [   17.350653] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T15:17:37.197619-08:00 INFO kernel: [   17.604791] usb 1-5: new high-speed USB device number 5 using xhci_hcd
/var/log/messages.4:2017-12-02T15:17:37.197620-08:00 ERR kernel: [   32.770103] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T15:17:37.197622-08:00 INFO kernel: [   33.024243] usb 1-5: new high-speed USB device number 6 using xhci_hcd
/var/log/messages.4:2017-12-02T15:17:37.197627-08:00 ERR kernel: [   43.461610] usb 1-5: device not accepting address 6, error -62
/var/log/messages.4:2017-12-02T15:17:37.197627-08:00 INFO kernel: [   43.614798] usb 1-5: new high-speed USB device number 7 using xhci_hcd
/var/log/messages.4:2017-12-02T15:17:37.197631-08:00 ERR kernel: [   54.046147] usb 1-5: device not accepting address 7, error -62
/var/log/messages.4:2017-12-02T20:49:58.428952-08:00 INFO kernel: [20012.140813] usb 1-5: new high-speed USB device number 12 using xhci_hcd
/var/log/messages.4:2017-12-02T20:50:13.581953-08:00 ERR kernel: [20027.306201] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T20:50:13.835953-08:00 INFO kernel: [20027.560226] usb 1-5: new high-speed USB device number 13 using xhci_hcd
/var/log/messages.4:2017-12-02T20:50:28.989011-08:00 ERR kernel: [20042.725475] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T20:50:29.242950-08:00 INFO kernel: [20042.979689] usb 1-5: new high-speed USB device number 14 using xhci_hcd
/var/log/messages.4:2017-12-02T20:50:39.667950-08:00 ERR kernel: [20053.413077] usb 1-5: device not accepting address 14, error -62
/var/log/messages.4:2017-12-02T20:50:39.821012-08:00 INFO kernel: [20053.566306] usb 1-5: new high-speed USB device number 15 using xhci_hcd
/var/log/messages.4:2017-12-02T20:50:50.243959-08:00 ERR kernel: [20063.997929] usb 1-5: device not accepting address 15, error -62
/var/log/messages.4:2017-12-02T20:53:29.876054-08:00 INFO kernel: [20223.758663] usb 1-5: new high-speed USB device number 21 using xhci_hcd
/var/log/messages.4:2017-12-02T20:53:45.028938-08:00 ERR kernel: [20238.923993] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T20:53:45.282963-08:00 INFO kernel: [20239.178124] usb 1-5: new high-speed USB device number 22 using xhci_hcd
/var/log/messages.4:2017-12-02T20:54:00.435949-08:00 ERR kernel: [20254.343407] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T20:54:00.689970-08:00 INFO kernel: [20254.597650] usb 1-5: new high-speed USB device number 23 using xhci_hcd
/var/log/messages.4:2017-12-02T20:54:11.107958-08:00 ERR kernel: [20265.023968] usb 1-5: device not accepting address 23, error -62
/var/log/messages.4:2017-12-02T20:54:11.260973-08:00 INFO kernel: [20265.177104] usb 1-5: new high-speed USB device number 24 using xhci_hcd
/var/log/messages.4:2017-12-02T20:54:21.684983-08:00 ERR kernel: [20275.609523] usb 1-5: device not accepting address 24, error -62
/var/log/messages.4:2017-12-02T21:48:25.431496-08:00 INFO kernel: [    2.181449] usb 1-5: new high-speed USB device number 4 using xhci_hcd
/var/log/messages.4:2017-12-02T21:48:40.325113-08:00 ERR kernel: [   17.346962] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T21:48:40.579114-08:00 INFO kernel: [   17.601092] usb 1-5: new high-speed USB device number 5 using xhci_hcd
/var/log/messages.4:2017-12-02T21:48:55.732105-08:00 ERR kernel: [   32.766406] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T21:48:55.986115-08:00 INFO kernel: [   33.020540] usb 1-5: new high-speed USB device number 6 using xhci_hcd
/var/log/messages.4:2017-12-02T21:49:06.418070-08:00 ERR kernel: [   43.460900] usb 1-5: device not accepting address 6, error -62
/var/log/messages.4:2017-12-02T21:49:06.571114-08:00 INFO kernel: [   43.614099] usb 1-5: new high-speed USB device number 7 using xhci_hcd
/var/log/messages.4:2017-12-02T21:49:16.994121-08:00 ERR kernel: [   54.045445] usb 1-5: device not accepting address 7, error -62
/var/log/messages.4:2017-12-02T23:07:45.858112-08:00 INFO kernel: [    2.184487] usb 1-5: new high-speed USB device number 4 using xhci_hcd
/var/log/messages.4:2017-12-02T23:07:45.858116-08:00 ERR kernel: [   17.349899] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T23:07:45.858118-08:00 INFO kernel: [   17.604037] usb 1-5: new high-speed USB device number 5 using xhci_hcd
/var/log/messages.4:2017-12-02T23:07:45.858119-08:00 ERR kernel: [   32.769388] usb 1-5: device descriptor read/64, error -110
/var/log/messages.4:2017-12-02T23:07:45.858121-08:00 INFO kernel: [   33.023510] usb 1-5: new high-speed USB device number 6 using xhci_hcd
/var/log/messages.4:2017-12-02T23:07:45.858126-08:00 ERR kernel: [   43.460832] usb 1-5: device not accepting address 6, error -62
/var/log/messages.4:2017-12-02T23:07:45.858127-08:00 INFO kernel: [   43.613985] usb 1-5: new high-speed USB device number 7 using xhci_hcd
/var/log/messages.4:2017-12-02T23:07:45.858131-08:00 ERR kernel: [   54.045411] usb 1-5: device not accepting address 7, error -62
/var/log/messages.5:2017-12-01T15:48:05.457465-08:00 INFO kernel: [ 1024.248304] usb 1-5: new high-speed USB device number 8 using xhci_hcd
/var/log/messages.5:2017-12-01T15:48:05.622623-08:00 INFO kernel: [ 1024.413911] usb 1-5: New USB device found, idVendor=046d, idProduct=0853
/var/log/messages.5:2017-12-01T15:48:05.622650-08:00 INFO kernel: [ 1024.413934] usb 1-5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
/var/log/messages.5:2017-12-01T15:48:05.622655-08:00 INFO kernel: [ 1024.413952] usb 1-5: Product: PTZ Pro Camera

Comment 5 by denniswu@chromium.org, Dec 8 2017 

This line happens everytime before disconnection
hid-generic 0003:046D:0853.000D: can't reset device, 0000:00:14.0-5.3/input2, status -32

After going through the kernel code for usb, status -32 is pointing toward a failed clear of the device. I believe this error happens when the host tries to send a control message to the device to clear the endpoint the clear didn't go through(act_len=32).

In function: hid_reset in https://cs.corp.google.com/chromeos_public/src/third_party/kernel/v3.14/drivers/hid/usbhid/hid-core.c?dr=C

Comment 6 by denniswu@chromium.org, Dec 8 2017

Cc: egemih@chromium.org

Comment 7 by denniswu@chromium.org, Dec 8 2017

Cc: frankhu@chromium.org

Comment 8 by annaloraine@google.com, Dec 18 2017 

Hi, any update on this bug please? If in case you will need more information from the customer for the investigation, please feel free to let me know so I can request it to them. Thank you.

Comment 9 by stepheng...@amplifiedit.com, Dec 19 2017 

meet.google.com seems to be broken on chrome 63 when users are signed into a managed profile as well.

Comment 10 by annaloraine@google.com, Jan 5 2018 

Hi, any update please? The Customer is requesting for the Root Cause Analysis once we have identified why the issue occur. Thanks!

Comment 11 by kotah@chromium.org, Jan 10 2018

Cc: katierh@chromium.org
@annaloraine How often does this issue occur for this customer?

Comment 12 by annaloraine@google.com, Jan 10 2018 

Hi @kotah, the customer never reported any occurrences of the issue after the day he created the case.

Comment 13 by tovep@chromium.org, Jan 10 2018

Labels: hotrod-platform-triaged

Comment 14 by kotah@chromium.org, Jan 12 2018 

@annaloraine, If the issue has only occurred once, then #c3-#c5 might be all we can provide with customer.

@mzhuo, Does #c3 mean you can reproduce the same issue in local environment in the latest version? If so we would need to continue investigation so the issue can be resolved, but if not, we can share #c3-#c5 as the customer's request is more about explanation on what happened.

Comment 15 by annaloraine@google.com, Jan 15 2018 

Thank you @Kotah. I sent the information from #c3 and #c5 to the customer, and ask them again if the issue happen again after 11/30/2017.

Comment 16 by tovep@chromium.org, Jan 16 2018

Labels: -M-64 M-65

Comment 17 by annaloraine@google.com, Apr 12 2018 

We received another support case related to this issue, CFM is running in version 64

Comment 18 by sylcat@google.com, Dec 7 

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Comment 19 by sylcat@google.com, Dec 13

Status: Archived (was: Assigned)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.
►

Sign in to add a comment