Tested on 4.3....

-----
[(ttyv0)#~] kldstat
Id Refs Address    Size     Name
 1    3 0xc0100000 1a7108   kernel
 2    1 0xc0acf000 3000     daemon_saver.ko
 3    1 0xc0ad8000 12000    linux.ko
[(ttyv0)#~] kldload ipfw
module_register: module ipfw already exists!
linker_file_sysinit "ipfw.ko" failed to register! 17
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, 
default to deny, unlimited logging
[(ttyv0)#~] kldstat
Id Refs Address    Size     Name
 1    4 0xc0100000 1a7108   kernel
 2    1 0xc0acf000 3000     daemon_saver.ko
 3    1 0xc0ad8000 12000    linux.ko
 4    1 0xc0bf0000 6000     ipfw.ko
[(ttyv0)#~] kldunload ipfw

Fatal trap 12: page fault while in kernel mode
fault virtual address           = 0x4
fault code              = supervisor read, page not present
instruction pointer             = 0x8:0xc013c63b
stack pointer           = 0x10:0xc6a6ded8
frame pointer           = 0x10:0xc6a6ded8
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
procesor eflags         = interrupt enabled, reseume, iopl=0
current process         = 378 (kldunload)
interrupt mask          = none
trap number             = 12
panic : page fault
syncing disks... 15 15 11 2
done
uptime 6m6s
Automatic reboot in 15 seconds - press a key on the console to abort 
-----
:(((((( 

Cheers,
Radu Bogdan Rusu (aka veedee)
C7 Campus Network System Administrator

On Fri, 9 Nov 2001 04:21:41 -0500 (EST), Andrew R. Reiter wrote:
>Yes, there is an open pr regarding this.  In -current all this is fixed,
>but I know ipfw and, iirc, nfs modules have these problems in 4.4.  
>Andrew
>On Fri, 9 Nov 2001, Dimitar Peikov wrote:
>:
>:This morning I've cvsuped to STABLE and put 'options IPFIREWALL' into my 
>:kernel configuration file. After installing all I try to 'kldload ipfw' which 
>:complains that ipfw module is already in kernel, but kldstat reports that 
>:module is being loaded! Then I've decided to kldunload it.... Kernel panic 
>:.... reboot!
>:
>:It is regular to kernel crash if ipfw is loaded as module, but why when it was 
>:build into kernel? In that case it would be good kldload/kldunload to exit! 
>:Why kldload loads module in case that it is compiled in kernel?
>:
>:-- 
>:Dimitar Peikov
>:Programmer Analyst
>:Globalization Group
>:"We Build e-Business"  
>:
>:RILA Solutions  
>:27 Building, Acad.G.Bonchev Str.  
>:1113 Sofia, Bulgaria  
>:
>:phone: (+359 2) 9797320 
>:phone: (+359 2) 9797300 
>:fax:   (+359 2) 9733355  
>:http://www.rila.com 
>:
>:
>:
>:To Unsubscribe: send mail to [EMAIL PROTECTED]
>:with "unsubscribe freebsd-net" in the body of the message
>:
>--
>Andrew R. Reiter
>[EMAIL PROTECTED]
>[EMAIL PROTECTED]
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-net" in the body of the message





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to