>Number:         37475
>Category:       install
>Synopsis:       Update to report #37363
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 04 09:20:01 +0000 2007
>Originator:     Randolf Richardson
>Release:        NetBSD v4.0 RC5
>Organization:
Inter-Corporate Computer & Network Services, Inc.
>Environment:
NetBSD netbsd.guildfordcab.com 4.0_RC5 NetBSD 4.0_RC5 (GENERIC.MP) #0: Wed Nov 28 14:15:53 PST 2007  builds@wb34:/home/builds/ab/netbsd-4-0-RC5/i386/200711280522Z-obj/home/builds/ab/netbsd-4-0-RC5/src/sys/arch/i386/compile/GENERIC.MP i386
>Description:
This is an update to report 37363.  Please delete this report after merging it into 37363.

>How-To-Repeat:
Same problem occurs in NetBSD v4.0 RC5 -- "pf" still doesn't start when "GENERIC.MP" is selected during installation (instead of the default "GENERIC" where it does work).

>Fix:
One solution I've found is to specify the "-f" option in /etc/lkm.conf which causes the module to be loaded anyway.  Although this solution seems to be working, I've not tested it in a high-volume network scenario so I don't know if system instability can occur.

The best solution would be for "pf" to be compiled for multi-processor mode when "GENERIC.MP" is selected during the installation.

I installed from the ISO for i386.  This time I'm using an Intel Core2Duo processor with 1 GB of RAM and a single 250 GB hard drive.