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

Issue 832922 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Teemo : PCie bus error continuously is reported on Teemo in meeting mode

Project Member Reported by mzhuo@chromium.org, Apr 13 2018

Issue description

Setup
=======
Teemo has Mimo, Atrus and Huddly directly connected.

ver
-------
R67-10575.0.0

Steps to reproduce the problem:
1. powerup Teemo in meeting mode


Reproduciable
==============
always

log
=====
2018-04-13T14:23:35.030843-07:00 ERR kernel: [ 6642.332508] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:24:36.705836-07:00 ERR kernel: [ 6704.009095] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:25:38.243145-07:00 ERR kernel: [ 6765.546851] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:26:19.002843-07:00 ERR kernel: [ 6806.307502] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:26:41.346811-07:00 ERR kernel: [ 6828.651089] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:27:43.057780-07:00 ERR kernel: [ 6890.363253] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:28:44.688887-07:00 ERR kernel: [ 6951.995100] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:29:46.277787-07:00 ERR kernel: [ 7013.585298] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:30:47.975778-07:00 ERR kernel: [ 7075.283751] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
localhost /var/spool/crash # cat /etc/lsb-release 
CHROMEOS_RELEASE_APPID={0C1E39B7-DAE6-4972-8004-E96F60D9342C}
CHROMEOS_BOARD_APPID={0C1E39B7-DAE6-4972-8004-E96F60D9342C}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOX
CHROMEOS_ARC_VERSION=4718253
CHROMEOS_ARC_ANDROID_SDK_VERSION=25
GOOGLE_RELEASE=10575.0.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BUILDER_PATH=fizz-release/R67-10575.0.0
CHROMEOS_RELEASE_UNIBUILD=1
CHROMEOS_RELEASE_BUILD_NUMBER=10575
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_CHROME_MILESTONE=67
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=10575.0.0 (Official Build) dev-channel fizz-unibuild (fizz kench sion teemo wukong) test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_BOARD=fizz
CHROMEOS_RELEASE_VERSION=10575.0.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
CHROMEOS_RELEASE_MODELS=fizz kench sion teemo wukong
localhost /var/spool/crash # grep 'PCIe Bus Error' /var/log/messages  | wc -l
101
localhost /var/spool/crash # uptime -s
2018-04-13 12:32:53
localhost /var/spool/crash # date
Fri Apr 13 14:35:42 PDT 2018
localhost /var/spool/crash # 


log file 
========
pls check log file attached in crbug.com/832916
 

Comment 1 by mzhuo@chromium.org, Apr 13 2018

Did fw update, the issue still exists.
=======================================
2018-04-13T14:59:15.478746-07:00 NOTICE kernel: [   37.557579] audit: type=1400 audit(1523656755.476:39): avc:  denied  { getattr } for  pid=3301 comm="df" path="/var/run/cras" dev="tmpfs" ino=15505 scontext=u:r:dumpstate:s0 tcontext=u:object_r:cras_socket:s0 tclass=dir permissive=0
2018-04-13T14:59:15.478747-07:00 NOTICE kernel: [   37.557610] audit: type=1400 audit(1523656755.476:40): avc:  denied  { getattr } for  pid=3301 comm="df" path="/var/run/inputbridge" dev="tmpfs" ino=18163 scontext=u:r:dumpstate:s0 tcontext=u:object_r:inputbridge:s0 tclass=dir permissive=0
2018-04-13T14:59:15.478748-07:00 NOTICE kernel: [   37.557680] audit: type=1400 audit(1523656755.476:41): avc:  denied  { getattr } for  pid=3301 comm="df" path="/var/run/camera" dev="tmpfs" ino=12364 scontext=u:r:dumpstate:s0 tcontext=u:object_r:camera_socket:s0 tclass=dir permissive=0
2018-04-13T14:59:17.000768-07:00 INFO kernel: [   39.079532] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
2018-04-13T14:59:17.000798-07:00 ERR kernel: [   39.079556] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T14:59:17.000802-07:00 ERR kernel: [   39.079565] pcieport 0000:00:1c.3:   device [8086:9d13] error status/mask=00000001/00002000
2018-04-13T14:59:17.000805-07:00 ERR kernel: [   39.079572] pcieport 0000:00:1c.3:    [ 0] Receiver Error        
2018-04-13T14:59:53.046909-07:00 INFO sshd[3489]: Accepted publickey for root from 127.0.0.1 port 40262 ssh2: RSA SHA256:Fp1qWjFLyK1cTpiI5rdk7iEJwoK9lcnYAgbQtGC3jzU
2018-04-13T14:59:53.946591-07:00 ERR chrome[965]: [965:965:0413/145953.946457:INFO:status_uploader.cc(222)] Starting status upload: have_device_status = 1
2018-04-13T14:59:54.296504-07:00 ERR chrome[965]: [965:965:0413/145954.296386:INFO:status_uploader.cc(235)] Status upload successful

^Z
[1]+  Stopped                 tail -f /var/log/messages
localhost ~ # bg
[1]+ tail -f /var/log/messages &
localhost ~ # crossystem | grep fwid
fwid                   = Google_Fizz.10139.113.0        # Active firmware ID
ro_fwid                = Google_Fizz.10139.113.0        # Read-only firmware ID

Cc: rajatja@chromium.org
maybe this is related to b/65570878

Comment 3 by rajatja@google.com, Apr 13 2018

Cc: nir.niss...@intel.corp-partner.google.com kirtika@chromium.org snanda@chromium.org
Yes, this is b/65570878. There is no work around, no fix. As per Intel, this is a Stonepeak issue we will have to live with. 

Comment 4 by rajatja@google.com, Apr 13 2018

Status: WontFix (was: Untriaged)

Comment 5 by mzhuo@chromium.org, Apr 14 2018

FYI, after disconnected all usb devices, then reboot Teemo, still have this type of error. mzhuo@minzhuo2:~/CFM/testlog/teemo$ ssh root@10.10.10.5
localhost ~ # tail -f /var/log/messages  &
[1] 2831
localhost ~ # 2018-04-13T17:22:44.737594-07:00 ERR chrome[851]: [851:851:0413/172244.737473:INFO:startup_app_launcher.cc(453)] 
.......
2018-04-13T17:22:56.702938-07:00 INFO kernel: [   38.985609] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
2018-04-13T17:22:56.702964-07:00 ERR kernel: [   38.985632] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
2018-04-13T17:22:56.702967-07:00 ERR kernel: [   38.985641] pcieport 0000:00:1c.3:   device [8086:9d13] error status/mask=00000001/00002000
2018-04-13T17:22:56.702969-07:00 ERR kernel: [   38.985649] pcieport 0000:00:1c.3:    [ 0] Receiver Error         (First)

localhost ~ # 
localhost ~ # 
localhost ~ # 
localhost ~ # 
localhost ~ # 
localhost ~ # lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 2, If 0, Class=, Driver=, 12M
    |__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
localhost ~ # 
localhost ~ # 
localhost ~ # 
localhost ~ # 2018-04-13T17:23:24.577133-07:00 WARNING mimo-monitor[1270]: Didn't find Displaylink or SiSMonitor

localhost ~ # 
localhost ~ # 
localhost ~ # 

Sign in to add a comment