Chrome Version:
9765.72.0 -- ChromeOS
Guado with Kepler running in meeting mode

What steps will reproduce the problem?
(0) Guado has both HDMI and DP connected to 2 monitors.
(1) Have mimo connected to Guado
(2) Have Mimo's HDMI cable connected to laptop
(3) Join meeting, and keep meeting on

What is the expected result?
No error

What happens instead?
Kernel reports "ERR kernel: [115400.475709] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)"

Please use labels and text to provide additional information.
=============================================================
localhost ~ # lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
03:00.0 Non-VGA unclassified device: Google, Inc. Device 001a (rev 01)
localhost ~ # gen                                                                                                                                                                                          
generate_logs  genl           
localhost ~ # generate_logs 
[1002/085917:INFO:generate_logs.cc(86)] Gathering logs, please wait
[1002/085919:INFO:generate_logs.cc(91)] Logs saved to /tmp/debug-logs_20171002-085917.tgz
localhost ~ #                                                                                                                                                                                              
localhost ~ # 
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.72.0
GOOGLE_RELEASE=9765.72.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=guado
CHROMEOS_RELEASE_BUILD_NUMBER=9765
CHROMEOS_RELEASE_BRANCH_NUMBER=72
CHROMEOS_RELEASE_CHROME_MILESTONE=61
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=9765.72.0 (Official Build) dev-channel guado test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=9765.72.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
localhost ~ # uptime                                                                                                                                                                                       
 08:59:27 up 1 day, 15:59,  0 users,  load average: 3.51, 3.49, 3.56
localhost ~ # tail /var/log/eventlog.txt                                                                                                                                                                   
190 | 2017-09-30 16:53:00 | Kernel Event | Clean Shutdown
191 | 2017-09-30 16:53:01 | System boot | 471
192 | 2017-09-30 16:53:01 | System Reset
193 | 2017-09-30 16:53:01 | Wake Source | GPIO | 27
194 | 2017-09-30 16:53:01 | Chrome OS Developer Mode
195 | 2017-09-30 16:59:49 | Kernel Event | Clean Shutdown
196 | 2017-09-30 16:59:50 | System boot | 472
197 | 2017-09-30 16:59:50 | System Reset
198 | 2017-09-30 16:59:50 | Wake Source | GPIO | 27
199 | 2017-09-30 16:59:51 | Chrome OS Developer Mode
localhost ~ # grep "PCIe Bus Error:" /var/log/messages                                                                                                                                                     
2017-10-02T01:02:09.638942-07:00 ERR kernel: [115400.475709] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
2017-10-02T01:05:02.057972-07:00 ERR kernel: [115573.033847] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
2017-10-02T01:07:25.200942-07:00 ERR kernel: [115716.293040] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Deleted: debug-logs_20171002-085917.tgz 9.0 MB

debug-logs_20171002-085917.tgz 9.0 MB Download