H大老毛子固件今天频繁重启并自动进Breed Web 恢复控制台,进到控制台后大概一两分钟就自动恢复到路由器管理页面了~出现了有大概五六次,拔掉电源重启后依旧出现。哪位大佬知道是啥原因么?
下面是异常时候看到的日志。
Feb 13 09:05:34 kernel: Unhandled kernel unaligned access[#1]:
Feb 13 09:05:34 kernel: Cpu 1
Feb 13 09:05:34 kernel: $ 0 : 00000000 00000001 00010000 00000001
Feb 13 09:05:34 kernel: $ 4 : a000014e 000001a5 00000038 00000000
Feb 13 09:05:34 kernel: $ 8 : 9bfb4800 01060000 00000000 00000000
Feb 13 09:05:34 kernel: $12 : 00000000 803ecb88 00000000 00000000
Feb 13 09:05:34 kernel: $16 : a000010e 9a54acbc 9bc1ca90 9a63aa80
Feb 13 09:05:34 kernel: $20 : 9a6c3c28 00000001 00000002 9a412418
Feb 13 09:05:34 kernel: $24 : 00000000 800ceae4
Feb 13 09:05:34 kernel: $28 : 9a5c8000 9a5c9be8 9a412518 800ca9c0
Feb 13 09:05:34 kernel: Hi : 00000000
Feb 13 09:05:34 kernel: Lo : 00000000
Feb 13 09:05:34 kernel: epc : 80323130 0x80323130
Feb 13 09:05:34 kernel: Tainted: P O
Feb 13 09:05:34 kernel: ra : 800ca9c0 0x800ca9c0
Feb 13 09:05:34 kernel: Status: 1100fc03 KERNEL EXL IE
Feb 13 09:05:34 kernel: Cause : 00800010
Feb 13 09:05:34 kernel: BadVA : a000014e
Feb 13 09:05:34 kernel: PrId : 0001992f (MIPS 1004Kc)
Feb 13 09:05:34 kernel: Modules linked in: nfsd exportfs lockd sunrpc ip_set_list_set(O) ip_set_bitmap_ip(O) rt_timer_wdg xt_webstr hw_nat nf_nat_ftp nf_conntrack_ftp ufsd(P) ip_set_hash_net(O) ip_set_hash_mac(O) ip_set_hash_ip(O) xt_set(O) ip_set(O) nfnetlink xhci_hcd usb_storage usblp mt76x3_ap mt76x2_ap
Feb 13 09:05:34 kernel: Process nfsd (pid: 1988, threadinfo=9a5c8000, task=9bd3fb08, tls=00000000)
Feb 13 09:05:34 kernel: Stack : 9a42b8c0 80271f20 0000320a 00000000 00000000 11270000 a000010e 800ceb14
Feb 13 09:05:34 kernel: 9a63aa80 9a507c0c 9b774df0 00000000 9b774000 00000000 11270000 9a54acbc
Feb 13 09:05:34 kernel: 9bc1ca90 9aa1a9e0 00000000 9a667764 00000000 9a667aa4 00000000 9a667734
Feb 13 09:05:34 kernel: 00000060 ffffffff 9a5c9db8 9aaecd00 00000000 9bc1ca90 9b84f118 9b7ac980
Feb 13 09:05:34 kernel: 9b7ac980 00000fff 00000060 802953b4 5e44a0be 0244b85f 9a5c9db8 9a698a58
Feb 13 09:05:34 kernel: ...
Feb 13 09:05:34 kernel: Call Trace:[<80271f20>] 0x80271f20
Feb 13 09:05:34 kernel: [<800ceb14>] 0x800ceb14
Feb 13 09:05:34 kernel: [<9a507c0c>] 0x9a507c0c
Feb 13 09:05:34 kernel: [<9aa1a9e0>] 0x9aa1a9e0
Feb 13 09:05:34 kernel: [<802953b4>] 0x802953b4
Feb 13 09:05:34 kernel: [<9a698a58>] 0x9a698a58
Feb 13 09:05:34 kernel: [<9a6d0000>] 0x9a6d0000
Feb 13 09:05:34 kernel: [<9a6ca6d0>] 0x9a6ca6d0
Feb 13 09:05:34 kernel: [<8005b390>] 0x8005b390
Feb 13 09:05:34 kernel: [<9a6c4188>] 0x9a6c4188
Feb 13 09:05:34 kernel: [<80321dd8>] 0x80321dd8
Feb 13 09:05:34 kernel: [<9a6c3c28>] 0x9a6c3c28
Feb 13 09:05:34 kernel: [<80273e3c>] 0x80273e3c
Feb 13 09:05:34 kernel: [<80167900>] 0x80167900
Feb 13 09:05:34 kernel: [<80320280>] 0x80320280
Feb 13 09:05:34 kernel: [<9a6c48c0>] 0x9a6c48c0
Feb 13 09:05:34 kernel: [<9a69995c>] 0x9a69995c
Feb 13 09:05:34 kernel: [<9a6d0000>] 0x9a6d0000
Feb 13 09:05:34 kernel: [<9a692758>] 0x9a692758
Feb 13 09:05:34 kernel: [<80167900>] 0x80167900
Feb 13 09:05:34 kernel: [<80320280>] 0x80320280
Feb 13 09:05:34 kernel: [<9a6d0000>] 0x9a6d0000
Feb 13 09:05:34 kernel: [<9a6cedd8>] 0x9a6cedd8
Feb 13 09:05:34 kernel: [<9a6c04a0>] 0x9a6c04a0
Feb 13 09:05:34 kernel: [<8032326c>] 0x8032326c
Feb 13 09:05:34 kernel: [<9a68cbe8>] 0x9a68cbe8
Feb 13 09:05:34 kernel: [<9a69e224>] 0x9a69e224
Feb 13 09:05:34 kernel: [<9a68c73c>] 0x9a68c73c
Feb 13 09:05:34 kernel: [<9a6c0e04>] 0x9a6c0e04
Feb 13 09:05:34 kernel: [<9a6c0cc8>] 0x9a6c0cc8
Feb 13 09:05:34 kernel: [<80320724>] 0x80320724
Feb 13 09:05:34 kernel: [<9a6c0cc8>] 0x9a6c0cc8
Feb 13 09:05:34 kernel: [<80047cac>] 0x80047cac
Feb 13 09:05:34 kernel: [<8000c960>] 0x8000c960
Feb 13 09:05:34 kernel: [<80047c1c>] 0x80047c1c
Feb 13 09:05:34 kernel: [<8000c950>] 0x8000c950
Feb 13 09:05:34 kernel: Code: 03e00008 24020001 3c020001 <c0830000> 00622821 e0850000 10a0fffc 00032c02 3063ffff
Feb 13 09:05:34 kernel: ---[ end trace 07fb4b859e756664 ]---
|