system work bad with PCI-Express Device Error

[varogami]

Since I installed the Intrepid (deleting completely hardy), I often the following errors (not always) in dmesg

[ 16.485051] +------ PCI-Express Device Error ------+
[ 16.497188] Error Severity : Uncorrected (Fatal)
[ 16.503316] PCIE Bus Error type : Transaction Layer
[ 16.509402] Flow Control Protocol : First
[ 16.515408] Receiver ID : 0010
[ 16.521283] VendorID=1106h, DeviceID=a238h, Bus=00h, Device=02h, Function=00h
[ 16.527340] pcieport-driver 0000:00:02.0: broadcast error_detected message
[ 16.527357] pci 0000:06:00.0: device has no driver
[ 16.527359] pci 0000:06:00.1: device has no driver
[ 16.553857] kjournald starting. Commit interval 5 seconds
[ 16.554438] EXT3 FS on sda3, internal journal
[ 16.554444] EXT3-fs: mounted filesystem with ordered data mode.
[ 16.728018] pcieport-driver 0000:00:02.0: Root Port link has been reset
[ 16.728029] pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
[ 16.728033] pcieport-driver 0000:00:02.0: broadcast resume message
[ 16.728045] pcieport-driver 0000:00:02.0: AER driver successfully recovered
[ 16.728054] +------ PCI-Express Device Error ------+
[ 16.728056] Error Severity : Corrected
[ 16.728058] PCIE Bus Error type : Data Link Layer
[ 16.728060] RELAY_NUM Rollover : Multiple
[ 16.728062] Transmitter ID : 0010
[ 16.728065] VendorID=1106h, DeviceID=a238h, Bus=00h, Device=02h, Function=00h

[ 1633.767810] +------ PCI-Express Device Error ------+
[ 1633.767823] Error Severity : Uncorrected (Fatal)
[ 1633.767825] PCIE Bus Error type : Data Link Layer
[ 1633.767828] Data Link Protocol : First
[ 1633.767830] Receiver ID : 0010
[ 1633.767832] VendorID=1106h, DeviceID=a238h, Bus=00h, Device=02h, Function=00h
[ 1633.767836] pcieport-driver 0000:00:02.0: broadcast error_detected message
[ 1633.768797] pci 0000:06:00.0: device has no driver
[ 1633.768802] pci 0000:06:00.1: device has no driver
[ 1633.972030] pcieport-driver 0000:00:02.0: Root Port link has been reset
[ 1633.972047] pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
[ 1633.972529] pcieport-driver 0000:00:02.0: broadcast resume message
[ 1633.972724] pcieport-driver 0000:00:02.0: AER driver successfully recovered

Alongside this error some programs do not work (X crashes sometimes blocking the screen and the keyboard failing to enter the terminal with CTRL + ALT + F1 and becomes unkillable, but accessing via ssh other processes appear to work). I tried all the kernel of intrepid and I have the same problem with hardy has never happened.

I attach my xorg.conf if it can be useful.
My hardware

AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
motherboard:
        asrock alivesata2-glan
 sata II
 1GB RAM
 pci express
graphic card:
       asus eax1300pro (ati radeon x1300pro)
 lspci -> ATI Technologies Inc RV515 PRO [Radeon X1300/X1550 Series]
2 HD SATA II
2 HD IDE
linux is on primary sataII

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: fglrx
Package: linux-image-2.6.27-9-generic 2.6.27-9.19
ProcCmdLine: root=UUID=150dfb97-1711-4bcb-b2e6-3229e809915d ro vga=791
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-9.19-generic
SourcePackage: linux

[varogami (varogami)]

I attach new dmesg with all errors

[Leann Ogasawara (leannogasawara)]

Hi varogami,

Would you be willing to test the latest pre-release of Jaunty (currently Alpha3) -
http://cdimage.ubuntu.com/releases/jaunty/ . It contains a newer 2.6.28 based kernel so it would be nice to know if this issue remains. Thanks.

[varogami (varogami)]

I tried the live cd of jaunty and worked well but also live the intrepid gave no errors, then I tried to install only the kernel of the jaunty, but gives me the same error:
The packages I installed are:

dkms_2.0.21.0-0ubuntu1_all.deb
fglrx-amdcccle_8.561-0ubuntu1_i386.deb
fglrx-installer_8.561-0ubuntu1_i386.changes
fglrx-kernel-source_8.561-0ubuntu1_i386.deb
fglrx-modaliases_8.561-0ubuntu1_i386.deb
libamdxvba1_8.561-0ubuntu1_i386.deb
libxrandr2_1.2.99.4-1_i386.deb
linux-backports-modules-2.6.28-6-generic_2.6.28-6.3_i386.deb
linux-headers-2.6.28-6_2.6.28-6.17_all.deb
linux-image-2.6.28-6-generic_2.6.28-6.17_i386.deb
linux-restricted-modules-2.6.28-6-generic_2.6.28-6.6_i386.deb
linux-restricted-modules-common_2.6.28-6.6_all.deb
linux-source-2.6.28_2.6.28-6.17_all.deb
xorg-driver-fglrx_8.561-0ubuntu1_i386.deb

I attach new dmesg log

[DarkJavi (darkjavi)]

I have the same "PCI-Express Device Error" on jaunty rc(updated 5 minutes ago) in a "asrock alive sata2 glan" motherboard with updated bios,and ATI Technologies Inc Radeon X550/X700 Series (RV410).

This is what dmesg says

[ 1.460297] +------ PCI-Express Device Error ------+
[ 1.460352] Error Severity : Uncorrected (Non-Fatal)
[ 1.460403] PCIE Bus Error type : Transaction Layer
[ 1.460454] Flow Control Protocol : First
[ 1.460505] Receiver ID : 001b
[ 1.460555] VendorID=1106h, DeviceID=f238h, Bus=00h, Device=03h, Function=03h
[ 1.460609] pcieport-driver 0000:00:03.3: broadcast error_detected message

Is there any other info can I provide for help?

[lanroth (1-launchpad-net-lanroth-com)]

I'd just like to add my voice to this. This is the error I get:

+------ PCI-Express Device Error ------+
Error Severity : Uncorrected (Non-Fatal)
PCIE Bus Error type : Transaction Layer
Flow Control Protocol : First
Receiver ID : 0018
VendorID=1106h, DeviceID=c238h, Bus=00h, Device=03h, Function=00h
Broadcast error_detected message
Broadcast mmio_enabled message
Broadcast resume message
AER driver successfully recovered

it repeats many times a second when there is heavy disk access going on but doesn't destabilise the machine.

 I ALSO have an "ASRock Alive Sata2 GLan" motherboard. The problem started when I attached a pci-express SATA controller. The chip used on said controller is "SiI3132 - PCI Express (1x) to 2 Port SATA300" http://www.siliconimage.com/products/product.aspx?pid=32

I have the problem on every kernel I've tried: 2.6.25.20, 2.6.27.21 and a couple of others whose version I forget.

I'm using opensuse (ver 11.0 and 11.1), not Ubuntu.

[KeithR (keith-richardson)]

Just like to add that I am getting exactly the same error on initial boot:

4.539150] +------ PCI-Express Device Error ------+
[ 4.539151] Error Severity : Uncorrected (Non-Fatal)
[ 4.539152] PCIE Bus Error type : Transaction Layer
[ 4.539154] Flow Control Protocol : First
[ 4.539155] Receiver ID : 0010
[ 4.539156] VendorID=1106h, DeviceID=a238h, Bus=00h, Device=02h, Function=00h
[ 4.539158] pcieport-driver 0000:00:02.0: broadcast error_detected message
[ 4.539160] pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
[ 4.539161] pcieport-driver 0000:00:02.0: broadcast resume message
[ 4.539184] pcieport-driver 0000:00:02.0: AER driver successfully recovered

I also have an AsRock Alive Sata2 GLan motherboard with an NVidia 9400GT video card. I was also previously getting the same error with an ATi X1300 card which I ditched because of all the driver and video issues with ATi cards.

U9.04 is installed on SATA2-1 and boots as the first drive. Also have 2 IDE drives, the primary with MS XP and the secondary with U8.04. Never got this error before installing the SATA drive and U9.04.
Having replaced the video card I am in no mood to also ditch the Mobo.

Haven't yet noticed any crashes as only just installed the NVidia card. Runs a lot smoother without the ATi card and driver.

[varogami (varogami)]

from: http://forums.fedoraforum.org/showthread.php?t=201871
pci=nommconf on kernel options seems works

Attach my menu.lst

[wraithmonk (geoffitton-deactivatedaccount)]

I am getting the same message with Kubuntu Jaunty 9.04
Kernel 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
And with 2.6.28-15-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

[ 33.124026] +------ PCI-Express Device Error ------+
[ 33.124030] Error Severity : Uncorrected (Non-Fatal)
[ 33.124032] PCIE Bus Error type : Transaction Layer
[ 33.124034] Flow Control Protocol : Multiple
[ 33.124035] Receiver ID : 0010
[ 33.124037] VendorID=1106h, DeviceID=a238h, Bus=00h, Device=02h, Function=00h
[ 33.124040] pcieport-driver 0000:00:02.0: broadcast error_detected message
[ 33.124043] pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
[ 33.124045] pcieport-driver 0000:00:02.0: broadcast resume message
[ 33.124051] pcieport-driver 0000:00:02.0: AER driver successfully recovered
[ 36.561280] ppdev0: registered pardevice
[ 36.608207] ppdev0: unregistered pardevice
[ 37.181384] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 45.461494] CPU0 attaching NULL sched-domain.
[ 45.472087] CPU0 attaching NULL sched-domain.
[ 48.072021] eth0: no IPv6 routers present

[Adilson Oliveira (agoliveira)]

Same problem with Karmic Beta on a brand new X58 MB with i7 processor and ATI Radeon HD 4670.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[KeithR (keith-richardson)]

Seems to have disappeared under 9.10 (new install).

Jeremy Foshee wrote:
> This bug report was marked as Triaged a while ago but has not had any
> updated comments for quite some time. Please let us know if this issue
> remains in the current Ubuntu release,
> http://www.ubuntu.com/getubuntu/download . If the issue remains, click
> on the current status under the Status column and change the status back
> to "New". Thanks.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.