kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #44654
[Bug 1279699] [NEW] AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
Public bug reported:
Description: Ubuntu 13.10
Release: 13.10 (Ubuntu 3.11.0-15.25-generic 3.11.10)
On Ubuntu 3.11.0-15.25-generic 3.11.10 I am getting the following error:
[ 11.749109] bonding: bond0: Setting MII monitoring interval to 100.
[ 11.797258] bonding: bond1 is being created...
[ 11.797320] bonding: bond1 is being created...
[ 11.797322] bonding: bond1 is being created...
[ 11.797653] bonding: bond1 already exists.
[ 11.797658] bonding: bond1 already exists.
[ 11.808146] bonding: bond1: Setting MII monitoring interval to 100.
[ 11.824060] bonding: bond0: setting mode to 802.3ad (4).
[ 11.824063] bonding: bond1: setting mode to 802.3ad (4).
[ 11.825177] bonding: bond1: Setting LACP rate to fast (1).
[ 11.825259] bonding: bond0: Setting LACP rate to fast (1).
[ 11.825527] IPv6: ADDRCONF(NETDEV_UP): bond1: link is not ready
[ 11.825674] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[ 11.871240] bonding: bond0: Adding slave p2p1.
[ 12.124239] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 12.211592] init: avahi-cups-reload main process (823) terminated with status 1
[ 12.714726] bonding: bond0: enslaving p2p1 as a backup interface with a down link.
[ 12.715620] bonding: bond1: Adding slave p4p3.
[ 13.072966] bonding: bond1: enslaving p4p3 as a backup interface with a down link.
[ 13.072970] bonding: bond1: Adding slave p4p2.
[ 13.608930] bonding: bond1: enslaving p4p2 as a backup interface with a down link.
[ 13.608934] bonding: bond0: Adding slave p3p1.
[ 13.976911] netxen_nic: p4p2 NIC Link is up
[ 14.008903] netxen_nic: p4p3 NIC Link is up
[ 14.450454] bonding: bond0: enslaving p3p1 as a backup interface with a down link.
[ 14.450459] bonding: bond1: Adding slave p4p1.
[ 14.544862] bonding: bond1: enslaving p4p1 as a backup interface with a down link.
[ 14.544866] bonding: bond1: Adding slave p4p4.
[ 14.624820] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 14.677889] igb: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 14.824864] bonding: bond1: enslaving p4p4 as a backup interface with a down link.
[ 14.824871] IPv6: ADDRCONF(NETDEV_CHANGE): bond1: link becomes ready
[ 14.844792] bonding: bond0: link status down again after 0 ms for interface p2p1.
[ 14.862650] igb 0000:05:00.0: changing MTU from 1500 to 9000
[ 14.924798] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 14.938826] igb 0000:06:00.0: changing MTU from 1500 to 9000
[ 15.024843] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 15.148767] bonding: bond1: link status definitely up for interface p4p3, 1000 Mbps full duplex.
[ 15.148770] bonding: bond1: link status definitely up for interface p4p2, 1000 Mbps full duplex.
[ 15.940783] netxen_nic: p4p1 NIC Link is up
[ 15.948787] bonding: bond1: link status definitely up for interface p4p1, 0 Mbps full duplex.
[ 17.657721] igb: p3p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 17.724664] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 17.724676] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[ 17.748653] bonding: bond0: link status definitely up for interface p3p1, 1000 Mbps full duplex.
[ 18.201714] igb: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 18.248622] bonding: bond0: link status definitely up for interface p2p1, 1000 Mbps full duplex.
[ 41.932293] pcieport 0000:00:1c.4: AER: Multiple Corrected error received: id=00e4
[ 41.932337] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[ 41.937340] pcieport 0000:00:1c.4: device [8086:8c18] error status/mask=00000001/00002000
[ 41.942261] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
[ 538.342279] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 538.342306] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[ 538.342763] pcieport 0000:00:1c.4: device [8086:8c18] error status/mask=00000001/00002000
[ 538.343127] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
These are new Supermicro X10SL7-F motherboards with new HP NC375T in the
PCIE x8 (in x4) port.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/1279699/+attachment/3979418/+files/lspci-vnvn.log
** Summary changed:
- AER: Corrected error received: id=00e4
+ AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1279699
Title:
AER: Corrected error received: id=00e4 / PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e4
Status in “linux” package in Ubuntu:
New
Bug description:
Description: Ubuntu 13.10
Release: 13.10 (Ubuntu 3.11.0-15.25-generic 3.11.10)
On Ubuntu 3.11.0-15.25-generic 3.11.10 I am getting the following
error:
[ 11.749109] bonding: bond0: Setting MII monitoring interval to 100.
[ 11.797258] bonding: bond1 is being created...
[ 11.797320] bonding: bond1 is being created...
[ 11.797322] bonding: bond1 is being created...
[ 11.797653] bonding: bond1 already exists.
[ 11.797658] bonding: bond1 already exists.
[ 11.808146] bonding: bond1: Setting MII monitoring interval to 100.
[ 11.824060] bonding: bond0: setting mode to 802.3ad (4).
[ 11.824063] bonding: bond1: setting mode to 802.3ad (4).
[ 11.825177] bonding: bond1: Setting LACP rate to fast (1).
[ 11.825259] bonding: bond0: Setting LACP rate to fast (1).
[ 11.825527] IPv6: ADDRCONF(NETDEV_UP): bond1: link is not ready
[ 11.825674] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[ 11.871240] bonding: bond0: Adding slave p2p1.
[ 12.124239] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 12.211592] init: avahi-cups-reload main process (823) terminated with status 1
[ 12.714726] bonding: bond0: enslaving p2p1 as a backup interface with a down link.
[ 12.715620] bonding: bond1: Adding slave p4p3.
[ 13.072966] bonding: bond1: enslaving p4p3 as a backup interface with a down link.
[ 13.072970] bonding: bond1: Adding slave p4p2.
[ 13.608930] bonding: bond1: enslaving p4p2 as a backup interface with a down link.
[ 13.608934] bonding: bond0: Adding slave p3p1.
[ 13.976911] netxen_nic: p4p2 NIC Link is up
[ 14.008903] netxen_nic: p4p3 NIC Link is up
[ 14.450454] bonding: bond0: enslaving p3p1 as a backup interface with a down link.
[ 14.450459] bonding: bond1: Adding slave p4p1.
[ 14.544862] bonding: bond1: enslaving p4p1 as a backup interface with a down link.
[ 14.544866] bonding: bond1: Adding slave p4p4.
[ 14.624820] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 14.677889] igb: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 14.824864] bonding: bond1: enslaving p4p4 as a backup interface with a down link.
[ 14.824871] IPv6: ADDRCONF(NETDEV_CHANGE): bond1: link becomes ready
[ 14.844792] bonding: bond0: link status down again after 0 ms for interface p2p1.
[ 14.862650] igb 0000:05:00.0: changing MTU from 1500 to 9000
[ 14.924798] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 14.938826] igb 0000:06:00.0: changing MTU from 1500 to 9000
[ 15.024843] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 15.148767] bonding: bond1: link status definitely up for interface p4p3, 1000 Mbps full duplex.
[ 15.148770] bonding: bond1: link status definitely up for interface p4p2, 1000 Mbps full duplex.
[ 15.940783] netxen_nic: p4p1 NIC Link is up
[ 15.948787] bonding: bond1: link status definitely up for interface p4p1, 0 Mbps full duplex.
[ 17.657721] igb: p3p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 17.724664] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
[ 17.724676] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[ 17.748653] bonding: bond0: link status definitely up for interface p3p1, 1000 Mbps full duplex.
[ 18.201714] igb: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 18.248622] bonding: bond0: link status definitely up for interface p2p1, 1000 Mbps full duplex.
[ 41.932293] pcieport 0000:00:1c.4: AER: Multiple Corrected error received: id=00e4
[ 41.932337] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[ 41.937340] pcieport 0000:00:1c.4: device [8086:8c18] error status/mask=00000001/00002000
[ 41.942261] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
[ 538.342279] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 538.342306] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[ 538.342763] pcieport 0000:00:1c.4: device [8086:8c18] error status/mask=00000001/00002000
[ 538.343127] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
These are new Supermicro X10SL7-F motherboards with new HP NC375T in
the PCIE x8 (in x4) port.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279699/+subscriptions
Follow ups
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: JSE, 2014-03-25
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: JSE, 2014-03-17
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: JSE, 2014-03-10
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: JSE, 2014-02-24
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Jorren Schauwaert, 2014-02-14
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Jorren Schauwaert, 2014-02-14
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Jorren Schauwaert, 2014-02-14
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Joseph Salisbury, 2014-02-13
-
[Bug 1279699] WifiSyslog.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] UdevLog.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] UdevDb.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] ProcModules.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] ProcInterrupts.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] ProcCpuinfo.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] Lsusb.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] Lspci.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] IwConfig.txt
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Jorren Schauwaert, 2014-02-13
-
[Bug 1279699] Missing required logs.
From: Brad Figg, 2014-02-13
-
[Bug 1279699] [NEW] AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4
From: Jorren Schauwaert, 2014-02-13
References