Hi,I have an access point ap250(firmware version is 8.0r1) ,but not work.the ap reboot cycles and hand in middle. When I try to pull out PoE cable,sometime go well,but after a few seconds,the ap reboot and hang up.

[hatankkt]

this one of the log 

U-Boot 2012.10 (Apr 27 2019 - 23:37:32)

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 c413:e2d4:e980

NVRAM_MAGIC found at offset 700000

nvram_init: ret 1

Reset TPM chip...

Reset AUTH chip...

AP reboot abnormal:2

the stack magic is unmatch

Hit any key to stop autoboot: 0

Hit any key to interrupt boot from flash: 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

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

register snif device on interface eth0.

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

register snif device on interface eth1.

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)

BCM radio init config

Chanspec set to 0x1006

Chanspec set to 0xd826

BCM radio init config done

Aerohive Wireless Extension 2.0.0 ... INIT!

Aerohive Forwarding Engine module ... INIT!

Image L7 repository version 5, checking existing L7 repository... ...

Existing L7 repository version 5

Nothing to be done or verified with L7 repository version 5

[ashley_finch]

If it's in a boot loop, sometimes it can be recovered by formatting the AP and flashing the firmware to it. However you'll need a support case for this.

[hatankkt]

Thanks for answering both.

But in my case,another AP250s (the same firmware version 8.0r1) are getting power from same PoE switch and boots well .

And device was in version 10.0r5 before, even that time also it was showing the same behavior.

If there is another way to recover , please provide me.

[jose_gonzalez]

Not normal behavior. If you can't get it to stay up long enough to reset and or update firmware, then RMA it. But before you do that you may want to make sure it's getting good power. If a switch is providing POE, check it's logs, try a different POE port or power injector.

[samantha_lynn]

Is this happening to one AP or several in the network? Also, could you tell me if this AP has configuration pushed to it, or if it is in a reset state? Finally, that is a fairly old firmware version, I would strongly recommend updating to the latest firmware version and testing again to see if this issue has been resolved in a later firmware version.