AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142)

bauer3m — Thu, 06 Dec 2018 04:22:00 GMT

My organization is in the early stages of an AP upgrade project throughout our sites (around 55 schools) and I had to recently RMA 7 out of 48 access points (AP250) that were allotted for the same site due to the issue referenced in my question line. Has anyone else seen issues similar to this? Am I really just experiencing a bad lot of APs or could there be something else going on? I will paste a copy of the boot sequence log from a Putty session on one of the RMA'd APs:

U-Boot 2012.10 (Aug 21 2018 - 20:22:25)

I2C: ready

Wait.

Done.

DEV ID= 0000cf12

REV ID= 00000000

SKU ID = 0

OTP status: eca00018

MEMC 0 DDR speed = 800MHz

Log: ddr40_phy_init.c: Configuring DDR Controller PLLs

Log: offset = 0x18010800

Log: VCO_FREQ is 1600 which is greater than 1Ghz.

Log: DDR Phy PLL polling for lock

Log: DDR Phy PLL locked.

Log: ddr40_phy_init::DDR PHY step size calibration complete.

Log: ddr40_phy_init:: Virtual VttSetup onm CONNECT=0x01CF7FFF, OVERRIDE=0x00077FFF

Log: ddr40_phy_init:: Virtual Vtt Enabled

Log: DDR Controller PLL Configuration Complete

PHY register dump after DDR PHY init

PHY register dump after mode register write

DRAM: 512 MiB

WARNING: Caches not enabled

GPIO Init ... Done

Power Input Detection: POE AF, Drive GPIO17(USB 5V enable) success

NAND: NAND_FLASH_DEVICE_ID_ADDR = 18028194

Done that

(ONFI), W29N04GV, blocks per lun: 1000 lun count: 1

*WARNING* Invalid strap options for this NAND: page=1 type=2

Overriding invalid strap options: strap_type=2

128 KiB blocks, 2 KiB pages, 16B OOB, 8-bit

NAND: chipsize

total 0 bad blocks,LIST:

now the up level will see a good flash chip no bad block which size is 20000000

before nvram partition, there are 0 bad blocks

512 MiB

Using default environment

In: serial

Out: serial

Err: serial

Unlocking L2 Cache ...Done

arm_clk=1000MHz, axi_clk=500MHz, apb_clk=250MHz, arm_periph_clk=500MHz

Net: Registering eth

Broadcom BCM IPROC Ethernet driver 0.1

Using GMAC1 (0x18025000)

et0: ethHw_chipAttach: Chip ID: 0xcf12; phyaddr: 0x1e

bcm_robo_attach: devid: 0x53012

bcmiproc_eth-0

MAC address is f4ea:b503:1f00

NVRAM_MAGIC found at offset 700000

nvram_init: ret 1

Reset TPM chip...

Reset AUTH chip...

Hit any key to stop autoboot: 0

Loading kernel from device 0: nand0 (offset 0xf00000) ... done

Loading rootfs from device 0: nand0 (offset 0x3e00000) ... done

## Booting kernel from Legacy Image at 01005000 ...

Image Name: Linux-2.6.36

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 2629256 Bytes = 2.5 MiB

Load Address: 00008000

Entry Point: 00008000

Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 02005000 ...

Image Name: uboot initramfs rootfs

Image Type: ARM Linux RAMDisk Image (uncompressed)

Data Size: 30527488 Bytes = 29.1 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

Power off two PHY...

Loading Kernel Image ... OK

boot_prep_linux commandline: root=/dev/ram console=ttyS0,9600 ramdisk_size=70000 cache-sram-size=0x10000

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

...board_fixup

board_fixup: mem=512MiB

board_map_io

board_init_irq

board_init_timer

board_init

Mounting local file systems...

UBI device number 0, total 3256 LEBs (413433856 bytes, 394.3 MiB), available 123 LEBs (15618048 bytes, 14.9 MiB), LEB size 126976 bytes (124.0 KiB)

set attenuator GPIO 7b0f00->7b4f40

et_module_init: et_txq_thresh set to 0xce4

et_module_init: et_rxlazy_timeout set to 0x3e8

et_module_init: et_rxlazy_framecnt set to 0x20

et_module_init: et_rxlazy_dyn_thresh set to 0

eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)

eth1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)

PCI: Enabling device 0001:01:00.0 (0140 -> 0142)

PCI: Enabling device 0002:01:00.0 (0140 -> 0142)

RE: AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142)

bauer3m — Thu, 06 Dec 2018 04:24:00 GMT

I may add that the 7 APs that were returned did make a successful connection to our Hivemanager and they were able to be provisioned per our policies etc - They quit working and hung at an orange light about 10 days after initial install - Thanks

RE: AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142)

dmccarthy — Thu, 27 Dec 2018 07:00:00 GMT

Hi Matt,

We upgraded in the summer of 2017 in our Districts, and honestly, it is just the quality of the APs does not seem to be the same as it once was. We put in about 70 at one of our High Schools, and no exaggeration, 22 of them had these symptoms.

We did get a new "lot" of 250 APs, and eventually, everything worked as expected, but, what a train wreck. I would call to report this, and they wanted to know if the network was setup correctly, I would explain all I did was replace an older 330 with a 250, and then it did not work. Then they would mention that the lights could be causing interference, or they would want to Putty in over telnet (despite me informing them it was not booting and therefore not getting an IP address). Eventually, through much patience, they did replace the failed APs.

Anyways, to get back to you, it is a hardware failure and replacement is the best method. Aerohive will try to format the flash, then netboot via putty and load a new image, but, that does not work, at least in my case, as I was 0/22 on those methods.

Dave

topic RE: AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142) in Aerohive Migrated Content

AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142)

RE: AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142)

RE: AP250 hanging during boot sequence at "PCI: Enabling device 0002:01:00.0 (0140 -> 0142)