strange panic

[Jake Burkholder]

Apparently, On Mon, Apr 21, 2003 at 08:26:02AM +0200,
	Anders Andersson said words to the effect of;

> On Sun, Apr 20, 2003 at 10:14:44AM +0200, Anders Andersson wrote:
> > Hi,
> > 
> > I have gotten this panic on ultra10:
> > 
> > db> trace
> > panic() at panic+0xcc
> > trap() at trap+0x3bc
> > -- memory address not aligned sfar=0xc2ddcb1c sfsr=0x4002d %o7=0xc012e8c0 --
> > ipfw_ctl() at ipfw_ctl+0x174
> > rip_ctloutput() at rip_ctloutput+0x164
> > sogetopt() at sogetopt+0x38
> > getsockopt() at getsockopt+0xb0
> > syscall() at syscall+0x2b4
> > -- syscall (118, FreeBSD ELF64, getsockopt) %o7=0x1032c0 --
> > userland() at 0x108598
> > user trace: trap %o7=0x1032c0
> > pc 0x108598, sp 0x7fdfffff121
> > pc 0x107468, sp 0x7fdfffff1f1
> > pc 0x1079ec, sp 0x7fdfffff2b1
> > pc 0x1001dc, sp 0x7fdfffff371
> > pc 0, sp 0x7fdfffff431
> > done

ipfw doesn't work well on sparc64.  It wasn't written to take architectures
with alignment constraints into account, so it causes these panics.  The
author doesn't seem to acknowledge that such architectures exist.

You're probably getting this from the daily periodic scripts listing the
firewall rules, you could just comment that out of the periodic scripts.

I'll try to get this fixed before 5.1-RELEASE unless someone else beats me
to it.

Jake

> 
> Since this happens regular every night here is the panic message:
> 
> db> panic
> panic: from debugger
> Debugger("panic")
> Stopped at      Debugger+0x1c:  ta              %xcc, 1
> db> 
> 
> gdb doesnt help:
> 
> ---
> dmesg: kvm_read: invalid address (0)
> ---
> #0  0x0000000000000000 in ?? ()
> (kgdb) where
> #0  0x0000000000000000 in ?? ()
> -- 
> Anders Andersson
> <anders at andersa.net>
> _______________________________________________
> freebsd-sparc64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
> To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe at freebsd.org"