Re: PF related panic

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

I created another debug kernel (DEBUG2)


--- GENERIC     2009-10-28 11:03:42.000000000 +0200
+++ DEBUG2      2009-11-12 09:28:48.000000000 +0200
@@ -90,4 +90,4 @@
 # Diagnostic/debugging support options
-#options       DIAGNOSTIC      # expensive kernel consistency checks
-#options       DEBUG           # expensive debugging checks/support
+options        DIAGNOSTIC      # expensive kernel consistency checks
+options        DEBUG           # expensive debugging checks/support
 #options       KMEMSTATS       # kernel memory statistics (vmstat -m)
@@ -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


IPF has been removed and PF is still a module -- and the kernel still
crashes. So, maybe something is not properly initialized when PF is a module...

Martti