Wireless Access

Reply
Occasional Contributor II

AP-105 Reboot Loop

Hi,

 

I have problems with an AP-105 which constantly reboots. Anyone has any tips what to do?

See the console output below:

 

APBoot 1.2.4.4 (build 26618)
Built: 2011-01-07 at 13:42:04

Model: AP-10x
CPU:   AR7161 revision: A2
Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
DRAM:  128 MB
POST1: passed
Copy:  done
Flash: 16 MB
PCI:   scanning bus 0 ...
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       00  00  168c  0029 00002   01 10000000 00000000 00000000 00000000
       02  00  168c  ffff 000ff   ff ffffffff ffffffff ffffffff ffffffff
Net:   eth0
Radio: ar922x#0

Hit <Enter> to stop autoboot:  0
Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 100 Mb/s full duplex
DHCP broadcast 1
DHCP broadcast 2
DHCP broadcast 3
DHCP broadcast 4
DHCP broadcast 5

Retry count exceeded; starting again
eth0 up: 100 Mb/s full duplex
DHCP broadcast 1
DHCP broadcast 2
DHCP broadcast 3
DHCP IP address: 172.16.0.248
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 172.16.0.254
DHCP DNS server: 172.16.0.254
DHCP DNS domain: test
Controller address: 172.16.0.254
Using eth0 device
TFTP from server 172.16.0.254; our IP address is 172.16.0.248
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: ####################################################
done
Bytes transferred = 3364988 (33587c hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Automatic boot of image at addr 0x02000000 ...
ELF file is 32 bit
Loading .text @ 0x80e00000 (3296120 bytes)
Clearing .bss @ 0x81124b80 (16 bytes)
Loading .data @ 0x81124b90 (32 bytes)
## Starting application at 0x80e00000 ...
Uncompressing..............................
▒
Aruba Networks
ArubaOS Version 3.4.5.1 (build 31936 / label #31936)
Built by p4build@crete on 2012-01-16 at 08:48:52 PST (gcc version 3.4.3)
Cache parity protection disabled
Using 340.000 MHz high precision timer. cycles_per_jiffy=680000
Memory: 123776k/131072k available (1612k kernel code, 7224k reserved, 443k data, 2588k init, 0k highmem)
 available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13190144
LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ..........................................................................................................................................................................................................
AR7100 GPIOC major 0
wdt: registered with refresh
Enabling Watchdog
Creating 1 MTD partitions on "ar7100-nor0":
0x00000000-0x01000000 : "flash"
i2c /dev entries driver
i2c-talisker: using default base 0x18040000
AD7416 driver probing for devices on AR7100 I2C
.
Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
Starting Kernel DES KAT ...Completed Kernel DES KAT
Starting Kernel AES KAT ...Completed Kernel AES KAT

ag7100_mod: module license 'unspecified' taints kernel.
AG7100: Length per segment 512
AG7100: Max segments per packet 4
AG7100: Max tx descriptor count    400
AG7100: Max rx descriptor count    252
AG7100: fifo cfg 3 018001ff
AG7100CHH: Mac address for unit 0
AG7100CHH: 6c:f3:7f:c5:b5:ab
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 0
AP xml model 39, num_radios 2 (jiffies 2005)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 8
radio 1: band 0 ant 0 max_ssid 8
asap_gre_init: ADDED GRE protocol c009e5e8
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)
PCI error 1 at PCI addr 0x10017044
PCI status: 0x22b0
ar7100 data bus error: cause 0x5080c01c
Data bus error, epc == c02ff928, ra == c02ff928
Oops[#1]:
Cpu 0
$ 0   : 00000000 00000000 deadc0de b0017044
$ 4   : 87cc0000 00007044 0000000f 00000002
$ 8   : 87cc0000 87cd3672 00000010 00000000
$12   : 00000000 ffffffff 00200200 00000000
$16   : 00000000 c02ff2d0 c02ff2bc 00000002
$20   : 0000000f 00007044 87cc0000 80170000
$24   : 00000010 801d6600
$28   : 8054e000 8054fb88 00000003 c02ff928
Hi    : 000001c4
Lo    : 9baac000
epc   : c02ff928 ath_hal_wait+0x6c/0xa8 [ath_hal]     Tainted: P
ra    : c02ff928 ath_hal_wait+0x6c/0xa8 [ath_hal]
Status: 1000c403    KERNEL EXL IE
Cause : 1080001c
PrId  : 00019374
Modules linked in: ath_pci ath_dev dfs ath_rate_atheros ath_hal wlan asap_mod drvlog_mod ag7100_mod
Process busybox (pid: 57, threadinfo=8054e000, task=811fc540)
Stack : 00000000 00000001 0001ae30 c02ff3c0 00000000 c02ff2a4 87cc0000 c0300000
        c0300000 c0300000 802c0000 c0319808 b7010018 00000000 00000000 ffffffff
        00000000 87cc0000 b0010000 00000000 8054fc50 8115b098 c0309760 c0309714
        00000001 8054fc50 87ca0000 c041a730 00000000 8054fc50 00000029 81150280
        87ca0000 c041a730 8054fd90 c02ff814 0000000d 00000000 8054fc28 81150280
        ...
Raw Call Trace:
[<c02ff3c0>] ath_hal_malloc+0x24/0x5c [ath_hal]
[<c02ff2a4>] ath_hal_reg_write+0x0/0x18 [ath_hal]
[<c0300000>] ath_hal_mhz2ieee+0x144/0x1a4 [ath_hal]
[<c0300000>] ath_hal_mhz2ieee+0x144/0x1a4 [ath_hal]
[<c0300000>] ath_hal_mhz2ieee+0x144/0x1a4 [ath_hal]
[<c0319808>] ar5416SetResetReg+0x1c0/0x380 [ath_hal]
[<c0309760>] ar5416Attach+0x90/0xa10 [ath_hal]
[<c0309714>] ar5416Attach+0x44/0xa10 [ath_hal]
[<c02ff814>] ath_hal_attach+0x70/0x10c [ath_hal]
[<c02ff04c>] _ath_hal_attach+0x4c/0xc0 [ath_hal]
[<c007b080>] bus_read_cachesize+0x30/0x60 [ath_dev]
[<80170000>] __find_get_block+0xe0/0x260
[<80169024>] kmem_cache_alloc+0x6c/0x74
[<c005d5ac>] ath_dev_attach+0x110/0x11b4 [ath_dev]
[<c005d570>] ath_dev_attach+0xd4/0x11b4 [ath_dev]
[<801df39c>] pci_bus_read_config_byte+0x3c/0x68
[<80216228>] ar7100_pci_read_config+0xc8/0x158
[<80216228>] ar7100_pci_read_config+0xc8/0x158
[<c041355c>] ath_attach+0x68/0x808 [ath_pci]
[<c040bfa4>] __ath_attach+0x50/0x3c4 [ath_pci]
[<801e0000>] pci_read_bases+0x230/0x2f8
[<802258a8>] alloc_netdev+0x38/0xd4
[<c040c884>] ath_pci_probe+0x464/0x584 [ath_pci]
[<c040c604>] ath_pci_probe+0x1e4/0x584 [ath_pci]
[<801d18d4>] kobject_get+0x20/0x34
[<801f8e10>] get_device+0x20/0x34
[<801e1ea0>] pci_device_probe+0x80/0xa4
[<801e1e48>] pci_device_probe+0x28/0xa4
[<801e1d68>] pci_bus_match+0x18/0x28
[<801282a0>] __call_console_drivers+0x80/0xac
[<801fadb0>] driver_probe_device+0x7c/0xdc
[<8028fa98>] klist_next+0x40/0x78
[<801d18d4>] kobject_get+0x20/0x34
[<801fafec>] __driver_attach+0xfc/0x144
[<801faef0>] __driver_attach+0x0/0x144
[<801fa344>] next_device+0x10/0x28
[<801faef0>] __driver_attach+0x0/0x144
[<801fa3b0>] bus_for_each_dev+0x54/0x90
[<801d1cd4>] kobject_register+0x2c/0x80
[<801d1ccc>] kobject_register+0x24/0x80
[<801fa7d8>] bus_add_driver+0xa8/0x148
[<801fb60c>] driver_register+0x68/0xe8
[<80128c10>] printk+0x0/0x28
[<801e1c98>] __pci_register_driver+0x70/0xc4
[<80128c2c>] printk+0x1c/0x28
[<80128c10>] printk+0x0/0x28
[<c0000054>] init_ath_pci+0x54/0x9c [ath_pci]
[<80146f28>] sys_init_module+0x284/0x438
[<80146e18>] sys_init_module+0x174/0x438
[<8016c848>] do_sys_open+0x110/0x15c
[<8010ef64>] stack_done+0x20/0x3c
[<8010ef64>] stack_done+0x20/0x3c

Stack : 00000000 00000001 0001ae30 c02ff3c0 00000000 c02ff2a4 87cc0000 c0300000
        c0300000 c0300000 802c0000 c0319808 b7010018 00000000 00000000 ffffffff
        00000000 87cc0000 b0010000 00000000 8054fc50 8115b098 c0309760 c0309714
        00000001 8054fc50 87ca0000 c041a730 00000000 8054fc50 00000029 81150280
        87ca0000 c041a730 8054fd90 c02ff814 0000000d 00000000 8054fc28 81150280
        ...
Unwound Call Trace:
[<c02ff928>] ath_hal_wait+0x6c/0xa8 [ath_hal]
[<c0319808>] ar5416SetResetReg+0x1c0/0x380 [ath_hal]
[<c0309760>] ar5416Attach+0x90/0xa10 [ath_hal]
[<c02ff814>] ath_hal_attach+0x70/0x10c [ath_hal]
[<c02ff04c>] _ath_hal_attach+0x4c/0xc0 [ath_hal]
[<c005d5ac>] ath_dev_attach+0x110/0x11b4 [ath_dev]
[<c041355c>] ath_attach+0x68/0x808 [ath_pci]
[<c040bfa4>] __ath_attach+0x50/0x3c4 [ath_pci]
[<c040c884>] ath_pci_probe+0x464/0x584 [ath_pci]
[<801e1ea0>] pci_device_probe+0x80/0xa4
[<801fadb0>] driver_probe_device+0x7c/0xdc
[<801fafec>] __driver_attach+0xfc/0x144
[<801fa3b0>] bus_for_each_dev+0x54/0x90
[<801fa7d8>] bus_add_driver+0xa8/0x148
[<801fb60c>] driver_register+0x68/0xe8
[<801e1c98>] __pci_register_driver+0x70/0xc4
[<c0000054>] init_ath_pci+0x54/0x9c [ath_pci]
[<80146f28>] sys_init_module+0x284/0x438
[<8010ef64>] stack_done+0x20/0x3c


Code: 02c02021  0240f809  02a02821 <00541024> 26100001  1453fff5  2404000a  24020001  8fbf002c
Flash erase @ 0xbff80000


APBoot 1.2.4.4 (build 26618)
Built: 2011-01-07 at 13:42:04

Model: AP-10x
CPU:   AR7161 revision: A2
Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
DRAM:  128 MB
POST1: mem 0
...

 

Guru Elite

Re: AP-105 Reboot Loop

You should open up a case with TAC so that they can analyze that crash and see if it has been addressed in a future version of ArubaOS code.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: AP-105 Reboot Loop

I just got it running:

 

...
Starting FIPS KAT ... Completed FIPS KAT

AP rebooted Sat May 24 22:41:03 CEST 2014; SAPD: Rebooting after provisioning
shutting down watchdog process (nanny will restart it)...

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

But then after a few minutes it started rebooting again:

~ # RESTARTING ALL TX
PCI error 1 at PCI addr 0x10010048
PCI status: 0x32b0
ar7100 data bus error: cause 0x5080c41c
Data bus error, epc == c09d2404, ra == c09d23fc
Oops[#1]:
Cpu 0
...

 I think there seems to be something wrong with the Mini PCI Wifi Card?

Guru Elite

Re: AP-105 Reboot Loop

Contact support and they will let you know for sure.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: AP-105 Reboot Loop

Of course this would be the best way, but I suppose there is no support coverage for this AP as I bought it for my test-lab.

Anyway, it's worth a try.

Guru Elite

Re: AP-105 Reboot Loop

well we would just be guessing here


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Re: AP-105 Reboot Loop

APs 3 is fairly old. If you have access to the support site you might want to get your controller on the latest GA release it supports.
ACDX #419 | ACMP |

Re: AP-105 Reboot Loop

I meant AOS (Darn iPhone)
ACDX #419 | ACMP |
Occasional Contributor II

Re: AP-105 Reboot Loop

It's already on AOS 6.3.1.6.
AOS 3.x was only for testing purposes.
Guru Elite

Re: AP-105 Reboot Loop

oNek,

 

Looking at 

 

ar7100 data bus error: cause 0x5080c01c

historically does indicate that this is a hardware fault and would typically be RMAed.

 

 

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: