各位大佬,请指教!多谢了!
突然断网,发现上网行为管理SecPath ACG1000-SE的管理地址不通了,重启设备,设备启动不起来了。
SPI stage 1 bootloader
SPI ID: ef:40:17:00:00
header found at offset 0x10000
Image 1.2: address: 0xffffffffc0000000, header length: 192, data length: 440048
Validating data...
Starting stage 1.5 bootloader at 0xffffffff81000000
Warning: Board descriptor tuple not found in eeprom, using defaults
CUST_NB02 board revision major:1, minor:0, serial #: unknown
OCTEON CN7020-SCP pass 1.2, Core clock: 1000 MHz, IO clock: 400 MHz, DDR clock: 533 MHz (1066 Mhz DDR)
Base DRAM address used by u-boot: 0x8fc00000, size: 0x400000
DRAM: 2 GiB
Clearing DRAM...... done
Using default environment
MMC: Octeon MMC/SD0: 1
SF: Detected W25Q64CV with page size 256 Bytes, erase size 4 KiB, total 8 MiB
Found valid SPI bootloader at offset: 0x100000, size: 1506032 bytes
U-Boot 2.1.1 (Build time: Jun 13 2018 - 09:38:06)
Using DRAM size from environment: 2048 MBytes
CUST_NB02 board revision major:1, minor:0, serial #: unknown
OCTEON CN7020-SCP pass 1.2, Core clock: 1000 MHz, IO clock: 400 MHz, DDR clock: 533 MHz (1066 Mhz DDR)
Base DRAM address used by u-boot: 0x8f000000, size: 0x1000000
DRAM: 2 GiB
Clearing DRAM...... done
Octeon MMC/SD0: 1
Flash boot bus region not enabled, skipping NOR flash config
PCIe: Port 0 not in PCIe mode, skipping
PCIe: Port 1 not in PCIe mode, skipping
PCIe: Port 2 not in PCIe mode, skipping
PCI console init succeeded, 1 consoles, 1024 bytes each
Press CTRL C to enter menuboot£º 0
reading vmlinux.64
....................................................................................
87578320 bytes read in 13729 ms (6.1 MiB/s)
argv[2]: cOnsole=ttyS0,9600
argv[3]: numcores=2
Allocating memory for ELF segment: addr: 0xffffffff80100000 (adjusted to: 0x100000), size 0x55e0500
## Loading big-endian Linux kernel with entry point: 0xffffffff80748740 ...
Bootloader: Done loading app on coremask: 0x3
Starting cores:
0x3
/sbin/rc starting
Mounting file systems
Setting up loopback
log disk part is sda1.
[ 394.710968] INFO: task sync:1323 blocked for more than 120 seconds.
[ 394.786084] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 394.879947] sync D ffffffff80751cbc 0 1323 1320 0x00100000
[ 394.964641] Stack : 800000008e421980 ffffffff8020a384 ffffffff80972c80 ffffffff802497dc
8000000086420c38 0000000000000103 000000fff469d31c 80000000898d6e00
0000000014d94001 8000000086420c38 800000006294ee18 00000000f469d31c
8000000086420c38 ffffffff8022a608 0000002885670a90 0000000000000103
000000fff469d000 800000006294ee18 80000000898d6e00 0000000000000000
0000000000000000 0000000000000000 0000000014d94001 ffffffff802497dc
0000000000000000 8000000086420c38 ffffffff85483480 ffffffff85483480
ffffffff85483480 ffffffff80972c80 800000008e5ebd18 8000000086420c38
ffffffff80972c80 ffffffff8022d810 80000000899cacd8 0000000000000000
80000000865d7c20 8000000063679008 0000000000000002 80000000899cacd8
...
[ 395.748653] Call Trace:
[ 395.777939] [<ffffffff807519a8>] __schedule+0x448/0x678
[ 395.840545] [<ffffffff80751cbc>] schedule+0x3c/0xb8
[ 395.898986] [<ffffffff80750750>] schedule_timeout+0x168/0x1c0
[ 395.967844] [<ffffffff8075146c>] wait_for_common+0x114/0x168
[ 396.035659] [<ffffffff802844a8>] sync_inodes_sb+0xb0/0x210
[ 396.101391] [<ffffffff8025e5a0>] iterate_supers+0x140/0x148
[ 396.168171] [<ffffffff802896d8>] sys_sync+0x38/0xa8
[ 396.226619] [<ffffffff8017ed04>] handle_sys64+0x44/0x68
[ 396.289223]
[ 396.307036] Kernel panic - not syncing: hung_task: blocked tasks
*** NMI Watchdog interrupt on Core 0x00 ***
$0 0x0000000000000000 at 0x0000000014101ce0
v0 0xffffffff809f0000 v1 0x0000000000000000
a0 0xffffffff855672f0 a1 0x0000000000000001
a2 0x0000000000000000 a3 0x30a53ac76b000000
a4 0x000000614a758ed6 a5 0x3030306439363032
a6 0x202843617669756d a7 0x204f6374656f6e20
t0 0x0000000000000004 t1 0xffffffff8556dd88
t2 0xffffffff85660000 t3 0x0000000000000000
s0 0xffffffff809784b8 s1 0xffffffff808d5370
s2 0x000000000000016e s3 0x00000000ee6b2800
s4 0xffffffff80967940 s5 0x7fffffffffffffff
s6 0x0000000000000004 s7 0x0000000000000001
t8 0x0000000000000048 t9 0x0000000000000001
k0 0x0000000000000000 k1 0x0f0000000238fd07
gp 0xffffffff80964000 sp 0xffffffff809676f0
s8 0x00000059682f026e ra 0xffffffff8074bbb0
err_epc 0xffffffff8019ab60 epc 0xffffffff801e9f48
status 0x0000000014581ce4 cause 0x0000000040808808
sum0 0x0000000000100000 en0 0x18002f0400000000
*** Chip soft reset soon ***
参考下这个链接吧:
https://zhiliao.h3c.com/Theme/details/7540
其次有条件确认下软件版本,涉及很多挂死问题,需要升级软件版本
https://zhiliao.h3c.com/Theme/details/192784
【产品型号】
涉及ACG1000系列应用控制网关产品。
【涉及版本】
产品型号 | 存在问题版本号 | 解决问题版本号 |
ACG1000-AK130 ACG1005-PWR ACG1000-BE-PWR ACG1000-BE ACG1010-X1 ACG1000-AK220 ACG1000-AK210 | R6611P10-BI(不含)之前版本 | R6611P10-BI或更新 |
ACG1005-PWR ACG1000-BE-PWR ACG1000-BE ACG1000-AK150 ACG1000-AK210 ACG1000-AK220 ACG1010-X1 ACG1030-X1 ACG1050-X1 ACG1000-B100 ACG1000-B200 ACG1000-B300 | R6611P10(不含)之前版本 | R6611P10或更新 (注意该款型无法升级至R6612及更新版本) |
ACG1000-SE-PWR ACG1000-SE ACG1030-X1 ACG1050-X1 ACG1000-AK230 ACG1000-AK240 ACG1000-AK250 ACG1000-AK260 ACG1000-TE ACG1000-ME ACG1060-X1 ACG1070-X1 ACG1000-C9130 ACG1000-C9150 ACG1000-C9160 ACG1000-AK215 ACG1000-AK225 ACG1000-AK255 ACG1000-AK265 ACG1000-AK270 ACG1000-AK280 ACG1000-AE ACG1000-C9170 ACG1000-AK275 ACG1000-PE ACG1000-EE ACG1000-AK285 ACG1000-XE1 ACG1000-Blade-E ACG1000-Blade-X | R6611P10(不含)之前版本 R6612(包含)~R6612P02(不含) | R6611P10或更新 R6612P02或更新 |
【问题描述】
上述型号产品运行存在问题版本时,设备出现转发异常、Web页面无法登录等挂死现象,或者自动重启等情况。
【原因分析】
设备运行过程中,系统使用的Postgre数据库长链接长时间占用控制平面内存不释放,导致设备内存不足,出现设备挂死或者自动重启等故障发生。
【规避措施/解决方案】
可通过升级表中解决问题版本号预防问题发生。
如设备已出现挂死现象,重启设备释放内存可紧急恢复。
暂无评论
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论