Try freebsd-hackers and/or freebsd-stable mailing lists, they are more technically oriented for stuff like this.
abe wrote: > Hi, > > I've written to the list recently with regard to a panic that keeps occuring > and perhaps my message was not formatted as well as it could have been. In more >testing > it seems that the minute the ipfw rules are loaded (which previously worked without >issue), > the machine panics. Any network connectivity attempted afterwards results in a >panic. > This includes ping, telnet, smtp, etc. When the machine panics, it drops into the >debugger > and displays the following: > > Stopped at add_dyn_rule+0172: movl 0(%edx,%ebx,4)x%eax > > I am including the entire 'trace' output from the debugger, but have also tried to > produce a core to get a backtrace via gdb however it doesn't seem to be dumping a >core. > savecore="YES" as well as dumpdir and dumpdev are set properly in rc.conf, yet >nothing > is produced and the system claims no dumpdev is set. > > If anyone has any experience with this issue, as I believe it to be with ipfw due to > lengthy testing on 4 different machines now (was 3 before), please feel free to >email me > and clue me in. Thanks a lot. > > Regards, > > Abe > > > ------------------------------------------------------------------------ > > add_dyn_rule(c0424894,0,c1258e00) at add_dyn_rule+0x172 > install_state(c1258e00) at install_state+0x179 > ip_fw_chk(cc88cda4,14,c1153000,cc88cdaa,cc88cdac) at ip_fw_chk+0x8d8 > ip_output(c0e63800,0,cbafad7c,0,0) at ip_output+0x530 > udp_output(cbafad40,c0e63800,0,0,cb69ba40) at udp_output+0x238 > udp_send(cbac8980,0,c0e63800,0,0) at udp_send+0x20 > sosend(cbac8980,0,cc88cecc,c0e63800,0) at sosend+0x5df > sendit(cb69ba40,5,cc88cf0c,0,bfbfeb2b) at sendit+0x253 > sendto(cb69ba40,cc88cf80,1b,bfbff400,0) at sendto+0x4e > syscall2(2f,2f,2f,0,bfbff400) at syscall2+0x1f5 > Xint0x80_syscall() at Xint0x80_syscall+0x25 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
