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

Issue 593187 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 591871



Sign in to add a comment

Guado Celeron Kepler USB peripherals unresponsive after large hangout session

Project Member Reported by harpreet@chromium.org, Mar 9 2016

Issue description

Guado Celeron w/ kepler
Build: 7647.84.0 (Current prod stable)

2 jabra's and hangouts remote dongle connected using the lindy USB extensions. These extension are part of the large room bundle. 

USB peripherals became unresponsive some time after initiating a 25 participant hangout session. Both jabra's and remote stopped working. Rebooting the device did not help either. They only started working after unplugging/re-plugging both lindy USB extensions to which these peripherals are connected.

Basically anything connected via the USB extensions stops working after some time when the Guado is in a hangout session is large number of participants.


Device logs attached.


Jabra's not being in sync with mute/volume might be related to this as well. I'll try repro this without USB extensions.

Feedback report from a guado unit with out of sync jabra's
http://feedback/#/Report/6830274960
 
Cc: bkemler@chromium.org yungleem@chromium.org vidster@chromium.org mnilsson@chromium.org dtosic@chromium.org stevenh@chromium.org
Components: OS>Kernel
Labels: Proj-Hotrod OS-Chrome
Logs at the link below:

https://cloud.google.com/console/storage/chromiumos-test-logs/bugfiles/cr/593187/
Note - I tried connecting a mouse and keyboard via the lindy hub and they did not work either. But they worked when I connected them directly to the USB port on the device. Same with the hangout remote dongle which was initially connected via the lindy hub and had stopped working after the large hangout session but it worked fine in the same large session when i connected it directly to the USB port on the device.
Blocking: 591871
Owner: hychao@chromium.org
Status: Assigned (was: Untriaged)
This is related to crbug.com/593551
Status: Archived (was: Assigned)

Comment 6 by ketakid@google.com, Mar 18 2017

Labels: Pri-3
Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.

Comment 7 by dtosic@google.com, Aug 17 2017

Cc: -dtosic@chromium.org
Status: Assigned (was: Available)

Sign in to add a comment