One of our IP440's crashed with 'panic: page fault'

We had a developer trying to stress-test across the FW from internal to a
server in the DMZ

This resulted in a crash/reboot of the IP440.  This has never happened to us
before.

Is there any kind of alerting we could have the IP440 setup to warn us that
it is running out of memory before it crashes?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

IPSO fw1 3.2-fcs4 releng 783  08.17.1999-124427 i386

====> Crash information:

Date:           Mon Jul 17 16:07:39 2000
Binary:         /var/crash/kernel.1     1487753 Tue Aug 17 16:28:13 1999
Crash file:     /var/crash/vmcore.1     26128384        Mon Jul 17 16:07:30
2000

====> Crash trace:

(no debugging symbols found)...IdlePTD 28e000
current pcb at 24c444
panic: page fault
#0  0xf01eedeb in boot
    (100, 2, efbff4e8, f01f40ef, f01f356c, f3531000, f02d3000, f2c8e100)
(kgdb) #0  0xf01eedeb in boot
    (100, 2, efbff4e8, f01f40ef, f01f356c, f3531000, f02d3000, f2c8e100)
#1  0xf011db74 in panic
    (f01f356c, f3531000, f02d3000, f2c8e100, f3531024, 0, fffff, f02df09b)
#2  0xf01f40ef in trap_fatal
    (efbff540, 2b2fd8, f2c8e100, efbff540, 0, f3531024, efbff503, 1)
#3  0xf01f3c50 in trap_pfault
    (efbff540, 0, 2b2fd8, f2a89aa4, f327e008, c, f01ec180, f01e0010)
#4  0xf01f3897 in trap
    (f01e0010, efbf0010, f327e008, f2a89aa4, efbff5a4, efbff568, 2b2fd8,
f3530fa0)
#5  0xf01ec0d1 in calltrap
    (f2d80b88, efbff604, f2cdd600, 51bb, f2cdd600, efbffda4, f25494b2,
f2cdd600)
#6  0xf25347f8 in end
    (f2cdd600, efbff604, f2cdd600, c0d87a18, f2c8e100, f255df78, 6b40,
efbffec4)
#7  0xf25494b2 in end
    (c0d87a18, f2cdd600, f256074b, 2100, f2d5ac00, efbffde0, f013ab63, 2100)
#8  0xf2560770 in end
    (2100, c0d87a18, f2cdd600, 7, f2c8e100, f2b4b480, efbffe90, f0137ef4)
#9  0xf013ab63 in spec_ioctl
    (efbffe00, 0, f2d5ac00, c0d87a18, 7, 0, f02142a4, f2b4b480)
#10 0xf0137ef4 in vn_ioctl
    (f2d5ac00, c0d87a18, f2cdd600, f2c8e100, f0216610, efbfc10c, f2c8e100,
f2cdd600)
#11 0xf011f55f in ioctl
    (f2c8e100, efbfff94, efbfff8c, efbfc184, 0, 1, f0216610, f2d6e96c)
#12 0xf01f43de in syscall
    (efbf0027, efbf0027, 1, 0, efbfc118, efbfffe4, efbfc184, 0)
#13 0xf01ec11b in Xsyscall (Cannot access memory at address 0xefbfc120.
)
Cannot access memory at address 0xefbfc118.

====> Done


================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to