[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/38245: system lock up with pf.o module on amd64
Note: There was a bad value `' for the field `Class'.
It was set to the default value of `sw-bug'.
>Synopsis: system lock up with pf.o module on amd64
>Arrival-Date: Sun Mar 16 03:00:00 +0000 2008
>Release: NetBSD 4.99.55
Jeremy C. Reed
System: NetBSD tx.reedmedia.net 4.99.55 NetBSD 4.99.55 (GENERIC) #0: Fri Mar 7
09:06:46 CST 2008
My dmesg is at http://reedmedia.net/~reed/tmp-nb73459yt/dmesg.boot
(Also had problem on 4.0_RC2.)
Using pf.o module on amd64 to do nat on ral0 from my re0 which is plugged
into Cisco IP phone causes system to lock up. Can't be pinged.
I don't know when it happens. Sometimes I am using it in X and sometimes
I am away. I am in X and no log messages.
(I can't test at console to see if any messages as I can't use console
after loading module -- see my ticket #38244.)
I repeated this many times with 4.0_RC2 and with 4.99.55.
Before using module and once I stopped using the module, the same system
works fine. Also I don't see this pf.o problem with my NetBSD/i386 4.0
system (which is using rum0 and bge0).
(The working system's dmesg is at
For what its worth, I replaced pf.o with just using builtin ipfilter
and using ipnat to do the same task for 12 hours and no lock up yet.
(pf lock up was probably about 30 miniutes).
I file this as a "kern" issue, but maybe it is a "amd64" issue?
I may try to build pf into kernel and try than instead of module.
But it is very inconvenient to have this system lock up quickly
For me it locks up every time maybe 30 minutes after I modload pf.o,
enable forwarding, and enable PF with one rule:
nat on ral0 from !(ral0) -> (ral0:0)
with the cisco IP phone plugged into my re0.
Main Index |
Thread Index |