飞塔防火墙运行中突然报错无法正常启动

 
  • 遇到一个BUG,设备正常运行中突然就报错后无法正常启动

 
BUG: unable to handle kernel paging request at 0000009f00000000IP: [<0000009f00000000>] 0x9effffffff
PGD 0
Oops: 0010 [#1] SMP
CPU 2

Modules linked in:
 filter4(P)


Pid: 122, comm: kworker/2:1 Tainted: P             3.2.16 #2
RIP: 0010:[<0000009f00000000>]  [<0000009f00000000>] 0x9effffffff
RSP: 0018:ffff8802328dbdf8  EFLAGS: 00010206
RAX: 0000009f00000000 RBX: ffff8801d9bb7bc0 RCX: 0000000000000005
RDX: 00000000ffffb380 RSI: ffff88023fd0cd20 RDI: ffff8801d9bb7bc0
RBP: ffff8801c9c9bcb8 R08: ffff88023fd0ccc0 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007
R13: ffffffff806f834c R14: ffffffff806f82a0 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff88023fd00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000009f00000000 CR3: 00000001dc3cf000 CR4: 00000000001406a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kworker/2:1 (pid: 122, threadinfo ffff8802328d8000, task ffff880233394890)
Stack:
 ffffffff804bd883 ffff8801d9bb7bc0 ffffffff804bda76 00000000ffffb3d2
 ffffffff806f82a0 ffff8802328ac640 ffff88023fd0ccc0 0000000000000000
 ffff88023fd13300 0000000000000000 ffffffff80270317 ffff8802328ac660
 ffffffff804bd970 ffff8802328ac660 ffff8802328ac640 ffff88023fd0ccc0
 ffff8802328ac660 ffff880233394890 ffff880233394890 ffff880233394890
 ffffffff80270ab5 ffff88023675fdc0 0000000000000282 0000000000000000
 0000000000010c40 ffff8802328dbef0 ffff88023675fda0 ffff8802328ac640
 ffffffff80270990 0000000000000000 0000000000000000 0000000000000000
 ffffffff802753de 1327160600000000 ffff8802328ac640 0000000000000000
 ffffffff806b0000 ffff8802328dbf20 ffff8802328dbf20 0000000000000000
 0000000000000000 0000000000000000 ffffffff80582334 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000000000
 0000000000000000 ffffffff80275360 ffff88023675fda0 ffffffffffffffff
 ffffffff80582330 0000000000000010 0000000000000202 ffff8802328dbf58
 0000000000000018
Call Trace:
 [<ffffffff804bd883>] ? neigh_cleanup_and_release+0x13/0x40
 [<ffffffff804bda76>] ? neigh_periodic_work+0x106/0x1c0
 [<ffffffff80270317>] ? process_one_work+0x117/0x370
 [<ffffffff804bd970>] ? __neigh_for_each_release+0xc0/0xc0
 [<ffffffff80270ab5>] ? worker_thread+0x125/0x2d0
 [<ffffffff80270990>] ? manage_workers.isra.30+0x1e0/0x1e0
 [<ffffffff802753de>] ? kthread+0x7e/0x90
 [<ffffffff80582334>] ? kernel_thread_helper+0x4/0x10
 [<ffffffff80275360>] ? kthread_worker_fn+0x120/0x120
 [<ffffffff80582330>] ? gs_change+0xb/0xb
Code:  Bad RIP value.
RIP  [<0000009f00000000>] 0x9effffffff
 RSP <ffff8802328dbdf8>
CR2: 0000009f00000000
---[ end trace 0a84b7a8917f562a ]---
Kernel panic - not syncing: Fatal exception in interrupt
Pid: 122, comm: kworker/2:1 Tainted: P      D      3.2.16 #2
Call Trace:
 [<ffffffff8057c758>] ? panic+0x95/0x194
 [<ffffffff80204d13>] ? oops_end+0x93/0xa0
 [<ffffffff8057c187>] ? no_context+0x189/0x198
 [<ffffffff802181cb>] ? do_page_fault+0x2bb/0x460
nsm: Corrupted page table at address 7f4a58a30a38
PGD 1c8ce6067 PUD 1c8ce5067 PMD 1c9ec9067 PTE 80000018c7d8d067
Bad pagetable: 000d [#2] SMP
CPU 1

Modules linked in:
 filter4(P)


Pid: 165, comm: nsm Tainted: P      D      3.2.16 #2
RIP: 0033:[<00007f4a58c9f283>]  [<00007f4a58c9f283>] 0x7f4a58c9f282
RSP: 002b:00000000149816a0  EFLAGS: 00010206
RAX: 0000000000000209 RBX: 0000000000000002 RCX: 00000000ffffffff
RDX: 00007f4a58a30a30 RSI: 00007f4a58eb6e3b RDI: 00007f4a58eb5000
RBP: 0000000014981820 R08: 0000000000000000 R09: 00000000003c5cb6
R10: 0000000014981700 R11: 0000000000000032 R12: 000000000000001b
R13: 000000000f172db2 R14: 00007f4a58eadba0 R15: 0000000014981810
FS:  00007f4a58ea9780(0000) GS:ffff88023fc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f4a58a30a38 CR3: 00000001c8cdd000 CR4: 00000000001406a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process nsm (pid: 165, threadinfo ffff88022ce5c000, task ffff880232d50150)

RIP  [<00007f4a58c9f283>] 0x7f4a58c9f282
 RSP <00000000149816a0>
---[ end trace 0a84b7a8917f562b ]---
Kernel panic - not syncing: Fatal exception
Pid: 165, comm: nsm Tainted: P      D      3.2.16 #2
Call Trace:
 [<ffffffff8057c758>] ? panic+0x95/0x194
 [<ffffffff80204d05>] ? oops_end+0x85/0xa0
 [<ffffffff8021827f>] ? do_page_fault+0x36f/0x460
 [<ffffffff8026b21d>] ? do_sigaction+0x9d/0x1f0
 [<ffffffff80268b26>] ? __send_signal+0x166/0x320
 [<ffffffff8026b64b>] ? sys_rt_sigaction+0x6b/0xc0
 [<ffffffff80580daf>] ? page_fault+0x1f/0x30
FortiGate-500D (12:49-03.06.2015)
Ver:05000002
Serial number:FGT5HD3915888888
RAM activation
CPU(00:000306a9 bfebfbff): MP initialization
CPU(02:000306a9 bfebfbff): MP initialization
CPU(04:000306a9 bfebfbff): MP initialization
CPU(06:000306a9 bfebfbff): MP initialization
Total RAM: 8192MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Boot up, boot device capacity: 15272MB.
Press any key to display configuration menu...
......

Reading boot image 2714093 bytes.
Initializing firewall...
已邀请:

kmliu - Fortinet-TAC

赞同来自:

像是硬件故障了,建议返修一下。

要回复问题请先登录注册