Controller Based WLANs

What does the ?PCI DATA ERROR? in an AP's console output mean?

Product and Software: This article applies to Aruba 120 series APs (for example, AP-120,121,124, and 125).

 

 

If the following message is seen in the console output of an AP-12x, the AP is defective and an RMA should be requested and AP replaced.

 

PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core

 

 

This console output of an AP-125 during boot-up time exhibits this problem:

 

Aruba Networks
ArubaOS Version 3.4.0.7 (build 22858 / label #22858)
Built by p4build@trinidad on 2009-11-13 at 18:52:29 PST (gcc version 3.4.5 Cavium Networks Version: 1.4.0, build 58)
CVMSEG size: 2 cache lines (256 bytes)
Setting flash physical map for 16MB flash at 0x1ec00000
Determined physical RAM map:
Primary instruction cache 16kB, virtually tagged, 2 way, 64 sets, linesize 128 bytes.
Primary data cache 8kB, 64-way, 1 sets, linesize 128 bytes.
Using 500.000 MHz high precision timer. cycles_per_jiffy=1000000
Memory: 57268k/65536k available (1919k kernel code, 8208k reserved, 565k data, 2232k init, 0k highmem)
Calibrating delay using timer specific routine.. 1000.38 BogoMIPS (lpj=1000381)
available.
Checking for the multiply/shift bug... no.
Checking for the daddi bug... no.
Checking for the daddiu bug... no.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13210112
LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ..........................................................................................................................................................................................................
PCI Status: PCI 32-bit
slot 3, pin 1, dev_num 3, irq A
PCI dev 3.0 slot 3 pin 1: 168c:ff1d using irq 44
slot 4, pin 1, dev_num 4, irq B
PCI dev 4.0 slot 4 pin 1: 168c:ff1d using irq 45
/proc/octeon_perf: Octeon performace counter interface loaded
hw_random hardware driver 1.0.0 loaded
wdt: registered with refresh
Enabling Watchdog
Octeon ethernet driver version: 1.5.0, build 187 Nov 13 2009 18:54:53
Interface 0 is RGMII
eth0: 1Gbs Full duplex, port 1, queue 1
isa bounce pool size: 16 pages
physmap flash device: 1000000 at 1ec00000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
phys_mapped_flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
Parsing the partition info
i2c /dev entries driver
i2c-palomino: using default base 0x8001070000000000
: Found DS1374 on octeon twsi
Executing 3010 Clock Adjustment
AD7416 driver probing for devices on Palomino TPM0
.AD7416 driver probing for devices on octeon twsi
.FOUND AD7416 at address: 48
Found AD7416 on bus octeon twsi.
PCI ERROR[DPERR]: Data parity error detected by PCX core

Starting HW SHA1 KAT ...Completed HW SHA1 KAT
Starting HW HMAC-SHA1 KAT ...Completed HW HMAC-SHA1 KAT
Starting HW DES KAT ...Completed HW DES KAT
Starting HW AES KAT ...Completed HW AES KAT

AP xml model 24, num_radios 2 (jiffies 1622)
radio 0: band 1 ant 0 max_ssid 16
radio 1: band 0 ant 0 max_ssid 16
asap_gre_init: ADDED GRE protocol c00000000013e818
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.1 (AR5416, REGOPS_FUNC, PRIVATE_DIAG, WRITE_EEPROM, 11D)
ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
ath_dfs: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_dev_attach: unable to attach hardware; HAL status 14
PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core
ath_dev_attach: unable to attach hardware; HAL status 14
PCI ERROR[DPERR]: Data parity error detected by PCX core
Ethernet port 1 mode: active-standby
<6>Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)
bonding: bond0: enslaving eth0 as a backup interface with a down link.
bonding: bond0: enslaving eth1 as a backup interface with a down link.
net.aruba_asap.br_initsecure_jack_link_state_change: Error finding device eth0
= 1
Getting an IP address...
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
172.16.250.98 255.255.255.0 172.16.250.1
Running ADP...Done. Master is 172.16.250.4
AP rebooted Mon Nov 30 23:51:25 PST 2009: SAPD: AP image version on controller (3.0.0) not compatible with AP type 125

<<<<< Welcome to the Access Point >>>>>

~ # Kernel watchdog refresh ended.

ath_dev_attach: unable to attach hardware; HAL status 14
PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core
PCI ERROR[DPERR]: Data parity error detected by PCX core
ath_dev_attach: unable to attach hardware; HAL status 14
PCI ERROR[DPERR]: Data parity error detected by PCX core

 

 

Based on this error message, it is concluded that the hardware is faulty and the AP needs to be replaced.

 

Version history
Revision #:
1 of 1
Last update:
‎07-05-2014 07:43 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.