Dave Ockwell-Jenner wrote: > .... > I've attached a snippet from /var/adm/messages [1] showing the actual > panic message. I've also included the stack trace from the resulting > crash dump file [2]. Curiously, this issue existed with IP Filter > 4.1.16 and pfil 2.1.11, which I was running until recently. I upgraded > to 4.1.20 in the hope that it would correct this issue. Needless to > say, the stock IP Filter that shipped in Solaris 10 panic'd every time > an IPsec connection attempt was made.
Are you using the ipsec/ike proxy in ipfilter? > Darren, or anyone who has a better clue than me - could you point me > in the right direction if it's something I'm doing wrong? > > [1] > > May 1 16:43:15 hostname ^Mpanic[cpu0]/thread=2a100047cc0: > May 1 16:43:15 hostname unix: [ID 799565 kern.notice] BAD TRAP: > type=31 rp=2a100046e00 addr=6ac54ab0 mmu_fsr=0 > May 1 16:43:15 hostname unix: [ID 100000 kern.notice] > May 1 16:43:15 hostname unix: [ID 839527 kern.notice] sched: > May 1 16:43:15 hostname unix: [ID 520581 kern.notice] trap type = 0x31 > May 1 16:43:15 hostname unix: [ID 381800 kern.notice] addr=0x6ac54ab0 > May 1 16:43:15 hostname unix: [ID 101969 kern.notice] pid=0, > pc=0x1040d24, sp=0x2a1000466a1, tstate=0x4480001600, context=0x0 > ... > # adb -w ./unix.2 ./vmcore.2 If you can do this in adb: 0x6ac54ab0/x 0x1040d24/i and hit return a few times, that'd help. Darren
