"Not enough bandwidth for new device state" |
|||||||||||||||
Issue descriptionChrome Version: 61.0.3163.38 OS: CrOS x86_64 9765.21.0 Device: Guado - Kernel 3.14 When reproducing b/64737545 the following message was found in /var/log/messages: "Not enough bandwidth for new device state" Googling on the message indicates that a common work around is to disable xhci and revert to ehci which hints at a bug in xhci: - https://superuser.com/questions/731751/not-enough-host-controller-resources-for-new-device-state - https://stackoverflow.com/questions/32574939/usb-bandwidth-host-controller-issues-linux This page goes into some more detail and links to some other deeper discussions of the problem: https://github.com/Nuand/bladeRF/issues/95 Anyone who recognize this problem?
,
Aug 30 2017
got it reproduced on 100.123.173.71 running R61-9765.45.0.
Setup:
======================
0. Mimo and huddly are connected to 2 USB ports on back. Atrus is connected to usb port on front. No extension cable, no usb hub.
1. Guado is in meeting. Select plankton video as video source, and plankton as microphone.
2. connect mimo green cable to Chromebook.
3. disconnect green cable from chromebook and connect it to Mac.
4. Huddly, Atrus and Plankton Captured HDMI Audio show no valid interface. "/var/log/messages" shows "no enough bandwidth" for new devices.
localhost ~ # usb-devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=11
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=03.14
S: Manufacturer=Linux 3.14.0 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:00:14.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 27 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18d1 ProdID=8001 Rev=01.00
S: Manufacturer=Google Inc.
S: Product=Hangouts Meet speakermic
S: SerialNumber=GATRB17130010
C: #Ifs= 0 Cfg#= 0 Atr= MxPwr=
cat: '/sys/bus/usb/devices/usb1/1-2/1-*:?.*/bInterfaceNumber': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-2/1-*:?.*/bAlternateSetting': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-2/1-*:?.*/bNumEndpoints': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-2/1-*:?.*/bInterfaceClass': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-2/1-*:?.*/bInterfaceSubClass': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-2/1-*:?.*/bInterfaceProtocol': No such file or directory
/usr/bin/usb-devices: line 79: printf: (none): invalid number
I: If#= 0 Alt= 0 #EPs= 0 Cls=() Sub= Prot= Driver=
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=07dc Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=03 Dev#= 12 Spd=480 MxCh= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=058f ProdID=6254 Rev=01.00
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
T: Bus=01 Lev=02 Prnt=12 Port=00 Cnt=01 Dev#= 13 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=266e ProdID=0110 Rev=03.00
S: Manufacturer=USBest Technology
S: Product=SiS HID Touch Controller
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=98mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
T: Bus=01 Lev=02 Prnt=12 Port=02 Cnt=02 Dev#= 18 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=17e9 ProdID=016b Rev=06.74
S: Manufacturer=DisplayLink
S: Product=MIMO VUE HD
S: SerialNumber=MXACP17040006
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=udl
T: Bus=01 Lev=02 Prnt=12 Port=03 Cnt=03 Dev#= 28 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=18d1 ProdID=5021 Rev=01.03
S: Manufacturer=C-Media Electronics Inc.
S: Product=Plankton Captured HDMI Audio
C: #Ifs= 0 Cfg#= 0 Atr= MxPwr=
cat: '/sys/bus/usb/devices/usb1/1-6/1-6.4/1-*:?.*/bInterfaceNumber': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-6/1-6.4/1-*:?.*/bAlternateSetting': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-6/1-6.4/1-*:?.*/bNumEndpoints': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-6/1-6.4/1-*:?.*/bInterfaceClass': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-6/1-6.4/1-*:?.*/bInterfaceSubClass': No such file or directory
cat: '/sys/bus/usb/devices/usb1/1-6/1-6.4/1-*:?.*/bInterfaceProtocol': No such file or directory
/usr/bin/usb-devices: line 79: printf: (none): invalid number
I: If#= 0 Alt= 0 #EPs= 0 Cls=() Sub= Prot= Driver=
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4
D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev=03.14
S: Manufacturer=Linux 3.14.0 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:00:14.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 14 Spd=5000 MxCh= 0
D: Ver= 3.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs= 1
P: Vendor=18d1 ProdID=501e Rev=00.01
S: Manufacturer=Generic
S: Product=Plankton Captured HDMI Video
S: SerialNumber=200901010001
C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=800mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I: If#= 1 Alt=12 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
localhost ~ # usb-devices ^C
localhost ~ # grep "not enough" /var/log/messages
localhost ~ # grep "not enough" /var/log/messages.1
grep: /var/log/messages.1: No such file or directory
localhost ~ # ls -altr /var/log
total 3820
-rw-r--r-- 1 root root 560 Aug 29 16:33 clobber.log
drwxrwxrwt 2 root root 4096 Aug 29 17:18 asan
lrwxrwxrwx 1 root root 58 Aug 29 17:18 vpd_2.0.txt -> /mnt/stateful_partition/unencrypted/cache/vpd/filtered.txt
drwxr-xr-x 2 root root 4096 Aug 29 17:18 recover_duts
-rw-r--r-- 1 root root 2742 Aug 29 23:52 shutdown_force_kill_processes
drwxr-xr-x 20 chronos chronos 4096 Aug 29 23:52 metrics
drwxr-xr-x 9 root root 4096 Aug 29 23:53 ..
-rw-r--r-- 1 root root 1237 Aug 29 23:53 mount_options.log
-rw-r--r-- 1 syslog root 0 Aug 29 23:53 boot.log
-rw-r--r-- 1 syslog root 0 Aug 29 23:53 laptopmode.log
-rw-r--r-- 1 syslog root 0 Aug 29 23:53 authpolicy.log
-rw-r--r-- 1 root root 839 Aug 29 23:53 mount-encrypted.log
-rw-r--r-- 1 root root 0 Aug 29 23:53 powerd.out
drwxr-xr-x 2 power power 4096 Aug 29 23:53 power_manager
drwxr-xr-x 2 root root 4096 Aug 29 23:53 ui
drwxr-xr-x 3 chronos chronos 4096 Aug 29 23:53 chrome
lrwxrwxrwx 1 root root 52 Aug 29 23:53 update_engine.log -> /var/log/update_engine/update_engine.20170829-235344
drwxr-xr-x 2 root root 4096 Aug 29 23:53 update_engine
drwxr-xr-x 2 root root 4096 Aug 29 23:53 vmlog
-rw-r--r-- 1 root root 6383 Aug 29 23:53 bios_info.txt
-rw-r--r-- 1 root root 1741 Aug 29 23:53 bios_times.txt
-rw-r--r-- 1 root root 11711 Aug 29 23:53 eventlog.txt
drwxrwxr-t 11 root syslog 4096 Aug 29 23:53 .
-rw-r--r-- 1 root root 10462 Aug 29 23:53 storage_info.txt
-rw-r--r-- 1 root root 850 Aug 29 23:53 memory_spd_info.txt
-rw-r--r-- 1 root root 95 Aug 29 23:53 platform_info.txt
-rw-r--r-- 1 syslog root 132077 Aug 29 23:54 tlsdate.log
-rw-r--r-- 1 root root 38775 Aug 29 23:54 debug_vboot_noisy.log
drwxr-xr-x 2 dlm dlm 4096 Aug 30 13:30 displaylink
-rw-r--r-- 1 syslog syslog 90977 Aug 30 13:56 atrus.log
-rw-r--r-- 1 root root 737 Aug 30 13:58 multimedia_xmlrpc_server.log
-rw-r--r-- 1 syslog root 16677 Aug 30 14:03 secure
-rw-r--r-- 1 root root 292 Aug 30 14:03 lastlog
-rw-r--r-- 1 syslog root 649654 Aug 30 14:06 net.log
-rw-r--r-- 1 syslog root 2833708 Aug 30 14:07 messages
localhost ~ # grep "bandwidth" /var/log/messages.1
grep: /var/log/messages.1: No such file or directory
localhost ~ # grep "bandwidth" /var/log/messages
2017-08-30T00:18:13.038323+00:00 INFO kernel: [ 13.056578] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-30T00:18:19.107080+00:00 INFO kernel: [ 19.130602] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T17:24:46.555033-07:00 INFO kernel: [ 2.566386] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T17:24:56.162033-07:00 INFO kernel: [ 12.180525] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:07:17.507029-07:00 INFO kernel: [ 2.518150] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:07:27.146032-07:00 INFO kernel: [ 12.164688] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:10:10.565227-07:00 INFO kernel: [ 2.576039] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:10:20.168030-07:00 INFO kernel: [ 12.186565] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:13:04.549035-07:00 INFO kernel: [ 2.558688] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:13:14.034035-07:00 INFO kernel: [ 12.051623] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:15:57.527058-07:00 INFO kernel: [ 2.536836] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:16:07.166103-07:00 INFO kernel: [ 12.184033] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:18:51.564044-07:00 INFO kernel: [ 2.574128] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:19:01.168033-07:00 INFO kernel: [ 12.186319] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:21:44.579030-07:00 INFO kernel: [ 2.589878] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:21:54.186033-07:00 INFO kernel: [ 12.205326] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:24:38.468037-07:00 INFO kernel: [ 2.479132] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:24:48.137035-07:00 INFO kernel: [ 12.156253] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:27:32.644037-07:00 INFO kernel: [ 2.654123] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:27:42.026337-07:00 INFO kernel: [ 12.043466] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:30:25.529027-07:00 INFO kernel: [ 2.538818] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:30:35.051035-07:00 INFO kernel: [ 12.068581] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:33:19.622034-07:00 INFO kernel: [ 2.633550] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:33:29.076026-07:00 INFO kernel: [ 12.095010] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:36:12.519036-07:00 INFO kernel: [ 2.529844] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:36:22.095018-07:00 INFO kernel: [ 12.113380] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:39:05.612038-07:00 INFO kernel: [ 2.621867] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:39:15.168033-07:00 INFO kernel: [ 12.186153] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:41:59.504031-07:00 INFO kernel: [ 2.514125] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:42:09.180032-07:00 INFO kernel: [ 12.198248] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:44:53.549207-07:00 INFO kernel: [ 2.560674] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:45:03.060032-07:00 INFO kernel: [ 12.079039] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:47:46.296025-07:00 INFO kernel: [ 2.306015] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:47:47.427285-07:00 INFO kernel: [ 3.437307] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:50:40.581028-07:00 INFO kernel: [ 2.592032] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:50:50.069049-07:00 INFO kernel: [ 12.087533] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:53:34.572047-07:00 INFO kernel: [ 2.582445] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-29T23:53:44.064032-07:00 INFO kernel: [ 12.081821] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
2017-08-30T13:47:51.355855-07:00 WARNING kernel: [50099.909784] usb 1-2: Not enough bandwidth for new device state.
2017-08-30T13:47:51.355872-07:00 INFO kernel: [50099.909802] usb 1-2: Not enough bandwidth for altsetting 0
2017-08-30T13:47:51.406877-07:00 WARNING kernel: [50099.960732] usb 1-6.4: Not enough bandwidth for new device state.
2017-08-30T13:47:51.406883-07:00 INFO kernel: [50099.960745] usb 1-6.4: Not enough bandwidth for altsetting 1
2017-08-30T13:47:51.406886-07:00 WARNING kernel: [50099.961410] usb 1-6.4: Not enough bandwidth for new device state.
2017-08-30T13:47:51.406887-07:00 INFO kernel: [50099.961422] usb 1-6.4: Not enough bandwidth for altsetting 1
2017-08-30T13:47:52.407851-07:00 WARNING kernel: [50100.963120] usb 1-6.4: Not enough bandwidth for new device state.
2017-08-30T13:47:52.407866-07:00 INFO kernel: [50100.963136] usb 1-6.4: Not enough bandwidth for altsetting 1
2017-08-30T13:56:39.737867-07:00 WARNING kernel: [50628.718915] usb 1-2: Not enough bandwidth for new device state.
2017-08-30T13:57:08.743843-07:00 WARNING kernel: [50657.748280] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:57:20.258853-07:00 WARNING kernel: [50669.272982] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:57:45.541315-07:00 WARNING kernel: [50694.575927] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:58:10.139944-07:00 WARNING kernel: [50719.194504] usb 1-6.4: Not enough bandwidth for new device state.
2017-08-30T13:58:10.726852-07:00 WARNING kernel: [50719.781500] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:58:36.014876-07:00 WARNING kernel: [50745.090413] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:59:01.294840-07:00 WARNING kernel: [50770.390132] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:59:26.579942-07:00 WARNING kernel: [50795.695700] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T13:59:51.758876-07:00 WARNING kernel: [50820.895039] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:00:17.043863-07:00 WARNING kernel: [50846.200481] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:00:42.328849-07:00 WARNING kernel: [50871.506402] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:01:07.512253-07:00 WARNING kernel: [50896.709940] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:01:32.799207-07:00 WARNING kernel: [50922.016941] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:01:58.078867-07:00 WARNING kernel: [50947.317133] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:02:23.361853-07:00 WARNING kernel: [50972.620211] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:02:48.542699-07:00 WARNING kernel: [50997.821658] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:03:13.826846-07:00 WARNING kernel: [51023.125914] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:03:39.112852-07:00 WARNING kernel: [51048.432600] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:04:04.294850-07:00 WARNING kernel: [51073.635385] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:04:29.582862-07:00 WARNING kernel: [51098.943673] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:04:54.863838-07:00 WARNING kernel: [51124.244464] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:05:20.148889-07:00 WARNING kernel: [51149.549973] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:05:45.336865-07:00 WARNING kernel: [51174.758740] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:06:10.624861-07:00 WARNING kernel: [51200.066818] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:06:35.911856-07:00 WARNING kernel: [51225.374390] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:07:01.096877-07:00 WARNING kernel: [51250.580203] usb 2-3: Not enough bandwidth for new device state.
2017-08-30T14:07:26.379859-07:00 WARNING kernel: [51275.882968] usb 2-3: Not enough bandwidth for new device state.
localhost ~ # date
Wed Aug 30 14:07:30 PDT 2017
localhost ~ # cat /etc/lsb-release
CHROMEOS_RELEASE_APPID={8AA6D9AC-6EBC-4288-A615-171F56F66B4E}
CHROMEOS_BOARD_APPID={8AA6D9AC-6EBC-4288-A615-171F56F66B4E}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOX
CHROMEOS_RELEASE_BUILDER_PATH=guado-release/R61-9765.45.0
GOOGLE_RELEASE=9765.45.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=guado
CHROMEOS_RELEASE_BUILD_NUMBER=9765
CHROMEOS_RELEASE_BRANCH_NUMBER=45
CHROMEOS_RELEASE_CHROME_MILESTONE=61
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=9765.45.0 (Official Build) dev-channel guado test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=9765.45.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
,
Aug 30 2017
This is expected, the quirks are not yet submitted.
,
Aug 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/38e8aa79d12c3b8a6a923dfb0b0c297f3ba28d96 commit 38e8aa79d12c3b8a6a923dfb0b0c297f3ba28d96 Author: Alan Stern <stern@rowland.harvard.edu> Date: Thu Aug 31 07:24:07 2017 BACKPORT: USB: add quirk for devices with broken LPM Some USB device / host controller combinations seem to have problems with Link Power Management. For example, Steinar found that his xHCI controller wouldn't handle bandwidth calculations correctly for two video cards simultaneously when LPM was enabled, even though the bus had plenty of bandwidth available. This patch introduces a new quirk flag for devices that should remain disabled for LPM, and creates quirk entries for Steinar's devices. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Reported-by: Steinar H. Gunderson <sgunderson@bigfoot.com> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit ad87e03213b552a5c33d5e1e7a19a73768397010) Signed-off-by: Stephen Barber <smbarber@chromium.org> Conflicts: drivers/usb/core/quirks.c (Trivial conflict in quirks list) BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: I556e6d8ca12c67034b6e77930f343cb334506814 Reviewed-on: https://chromium-review.googlesource.com/639693 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/38e8aa79d12c3b8a6a923dfb0b0c297f3ba28d96/drivers/usb/core/quirks.c [modify] https://crrev.com/38e8aa79d12c3b8a6a923dfb0b0c297f3ba28d96/include/linux/usb/quirks.h [modify] https://crrev.com/38e8aa79d12c3b8a6a923dfb0b0c297f3ba28d96/drivers/usb/core/hub.c
,
Aug 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/8ed608fa2acb8f2730e5ea316859cc8c45747896 commit 8ed608fa2acb8f2730e5ea316859cc8c45747896 Author: Stephen Barber <smbarber@chromium.org> Date: Thu Aug 31 07:24:08 2017 CHROMIUM: usb: quirks: add NO_LPM quirk for plankton LPM on plankton appears to cause xHCI host controllers to claim that there isn't enough bandwidth to support additional devices. BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: Ibfcf68720b17c6b6cda107692fcf1bba36516121 Signed-off-by: Stephen Barber <smbarber@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/639694 Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/8ed608fa2acb8f2730e5ea316859cc8c45747896/drivers/usb/core/quirks.c
,
Aug 31 2017
,
Aug 31 2017
This bug requires manual review: We are only 4 days from stable. Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 31 2017
Since we agreed that the patches above were a temporary, CHROMIUM-specific workaround, shouldn't this bug stay open for the continuing root cause investigation?
,
Aug 31 2017
We have a separate bug for that: b/65034294
,
Aug 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a48d588e9e5094f74aca868a41000d6c22ae1333 commit a48d588e9e5094f74aca868a41000d6c22ae1333 Author: Stephen Barber <smbarber@chromium.org> Date: Thu Aug 31 21:20:02 2017 CHROMIUM: usb: quirks: add NO_LPM quirk for plankton LPM on plankton appears to cause xHCI host controllers to claim that there isn't enough bandwidth to support additional devices. BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: Ibfcf68720b17c6b6cda107692fcf1bba36516121 Signed-off-by: Stephen Barber <smbarber@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/639327 Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/a48d588e9e5094f74aca868a41000d6c22ae1333/drivers/usb/core/quirks.c
,
Aug 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9f4bd6c52881a0eb53b4cb998a739cc6a9504510 commit 9f4bd6c52881a0eb53b4cb998a739cc6a9504510 Author: Alan Stern <stern@rowland.harvard.edu> Date: Thu Aug 31 21:20:01 2017 BACKPORT: USB: add quirk for devices with broken LPM Some USB device / host controller combinations seem to have problems with Link Power Management. For example, Steinar found that his xHCI controller wouldn't handle bandwidth calculations correctly for two video cards simultaneously when LPM was enabled, even though the bus had plenty of bandwidth available. This patch introduces a new quirk flag for devices that should remain disabled for LPM, and creates quirk entries for Steinar's devices. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Reported-by: Steinar H. Gunderson <sgunderson@bigfoot.com> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit ad87e03213b552a5c33d5e1e7a19a73768397010) Signed-off-by: Stephen Barber <smbarber@chromium.org> Conflicts: drivers/usb/core/quirks.c (Trivial conflict in quirks list) BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: I87f7368426b92b7adfe4a61e83dd796266196bc0 Reviewed-on: https://chromium-review.googlesource.com/639759 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/9f4bd6c52881a0eb53b4cb998a739cc6a9504510/drivers/usb/core/quirks.c [modify] https://crrev.com/9f4bd6c52881a0eb53b4cb998a739cc6a9504510/include/linux/usb/quirks.h [modify] https://crrev.com/9f4bd6c52881a0eb53b4cb998a739cc6a9504510/drivers/usb/core/hub.c
,
Sep 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2644da09535f90bfc50b7b3f267f6db7f326b19a commit 2644da09535f90bfc50b7b3f267f6db7f326b19a Author: Stephen Barber <smbarber@chromium.org> Date: Fri Sep 01 01:05:49 2017 CHROMIUM: usb: quirks: add NO_LPM quirk for plankton LPM on plankton appears to cause xHCI host controllers to claim that there isn't enough bandwidth to support additional devices. BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: Ibfcf68720b17c6b6cda107692fcf1bba36516121 Signed-off-by: Stephen Barber <smbarber@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/639760 [modify] https://crrev.com/2644da09535f90bfc50b7b3f267f6db7f326b19a/drivers/usb/core/quirks.c
,
Sep 5 2017
Approving merge for M61 and M62.
,
Sep 5 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/5315765542621dfb95f54ac7e6346c31a4bfb6a7 commit 5315765542621dfb95f54ac7e6346c31a4bfb6a7 Author: Alan Stern <stern@rowland.harvard.edu> Date: Tue Sep 05 20:49:21 2017 BACKPORT: USB: add quirk for devices with broken LPM Some USB device / host controller combinations seem to have problems with Link Power Management. For example, Steinar found that his xHCI controller wouldn't handle bandwidth calculations correctly for two video cards simultaneously when LPM was enabled, even though the bus had plenty of bandwidth available. This patch introduces a new quirk flag for devices that should remain disabled for LPM, and creates quirk entries for Steinar's devices. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Reported-by: Steinar H. Gunderson <sgunderson@bigfoot.com> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit ad87e03213b552a5c33d5e1e7a19a73768397010) Signed-off-by: Stephen Barber <smbarber@chromium.org> Conflicts: drivers/usb/core/quirks.c (Trivial conflict in quirks list) BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: I556e6d8ca12c67034b6e77930f343cb334506814 Reviewed-on: https://chromium-review.googlesource.com/639693 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> (cherry picked from commit 38e8aa79d12c3b8a6a923dfb0b0c297f3ba28d96) Reviewed-on: https://chromium-review.googlesource.com/651307 Reviewed-by: Stephen Barber <smbarber@chromium.org> Commit-Queue: Stephen Barber <smbarber@chromium.org> [modify] https://crrev.com/5315765542621dfb95f54ac7e6346c31a4bfb6a7/drivers/usb/core/quirks.c [modify] https://crrev.com/5315765542621dfb95f54ac7e6346c31a4bfb6a7/include/linux/usb/quirks.h [modify] https://crrev.com/5315765542621dfb95f54ac7e6346c31a4bfb6a7/drivers/usb/core/hub.c
,
Sep 5 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/c51c6fd3d023a61af1787f7530ea645a2c8c9ec3 commit c51c6fd3d023a61af1787f7530ea645a2c8c9ec3 Author: Stephen Barber <smbarber@chromium.org> Date: Tue Sep 05 20:49:26 2017 CHROMIUM: usb: quirks: add NO_LPM quirk for plankton LPM on plankton appears to cause xHCI host controllers to claim that there isn't enough bandwidth to support additional devices. BUG=b:65034294, chromium:758293 TEST=while using plankton capture, plug in USB speaker and make sure there are no bandwidth errors in dmesg Change-Id: Ibfcf68720b17c6b6cda107692fcf1bba36516121 Signed-off-by: Stephen Barber <smbarber@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/639694 Reviewed-by: Julius Werner <jwerner@chromium.org> (cherry picked from commit 8ed608fa2acb8f2730e5ea316859cc8c45747896) Reviewed-on: https://chromium-review.googlesource.com/651308 [modify] https://crrev.com/c51c6fd3d023a61af1787f7530ea645a2c8c9ec3/drivers/usb/core/quirks.c
,
Sep 5 2017
Made it into 62 just before the cutoff, so just merged to 61.
,
Jan 22 2018
,
Jan 23 2018
|
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by smbar...@chromium.org
, Aug 24 2017