Re: PF related panic

[Martti Kuparinen <martti.kuparinen%iki.fi@localhost>]

I was using a GENERIC kernel but I created PF based on GENERIC

--- GENERIC     2009-10-28 11:03:42.000000000 +0200
+++ PF  2009-11-12 07:30:57.000000000 +0200
@@ -104,3 +104,3 @@
 #options       KGDB_DEVNAME="\"com\"",KGDB_DEVADDR=0x3f8,KGDB_DEVRATE=9600
-#makeoptions   DEBUG="-g"      # compile full symbol table
+makeoptions    DEBUG="-g"      # compile full symbol table
 #options       SYSCALL_STATS   # per syscall counts
@@ -187,4 +187,4 @@
 options        PFIL_HOOKS      # pfil(9) packet filter hooks
-options        IPFILTER_LOG    # ipmon(8) log support
-options        IPFILTER_LOOKUP # ippool(8) support
+#options       IPFILTER_LOG    # ipmon(8) log support
+#options       IPFILTER_LOOKUP # ippool(8) support
 #options       IPFILTER_DEFAULT_BLOCK  # block all packets by default
@@ -1090,4 +1090,4 @@
 pseudo-device  ksyms                   # /dev/ksyms
-#pseudo-device pf                      # PF packet filter
-#pseudo-device pflog                   # PF log if
+pseudo-device  pf                      # PF packet filter
+pseudo-device  pflog                   # PF log if
 pseudo-device  lockstat                # lock profiling

I also commented out lkm=YES in /etc/rc.conf before reboot. Using PF as a module 
and I can reproduce a crash in 1 second, not using module and I haven't had any 
problems so far.

My host is IPv6 enabled but I scp'd the large file using IPv4.

Martti