Re: kernel dump with 7.1-RELEASE
On Fri, Jan 09, 2009 at 06:39:53PM +0200, Omer Faruk Sen wrote: Hi, I am having kernel dump with FreeBSD 7.1: Here is crashinfo output of it (Actually i don't know the state of crashinfo in Fbsd 7.1) 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 panic: semexit - semid not allocated GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: Physical memory: 8173 MB Dumping 437 MB: 422 406 390 374 358 342 326 310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 70 54 38 22 6 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:195 #1 0x0004 in ?? () #2 0x804b4ce9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #3 0x804b50f2 in panic (fmt=0x104 Address 0x104 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:574 #4 0x804f846d in semexit_myhook (arg=Variable arg is not available. ) at /usr/src/sys/kern/sysv_sem.c:1328 #5 0x80490dbc in exit1 (td=0xff000995f370, rv=0) at /usr/src/sys/kern/kern_exit.c:244 #6 0x8049239e in sys_exit (td=Variable td is not available. ) at /usr/src/sys/kern/kern_exit.c:109 #7 0x8078a7c7 in syscall (frame=0xb0d4ac80) at /usr/src/sys/amd64/amd64/trap.c:907 #8 0x8077088b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:330 #9 0x000800a2a30c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) The change that is believed to fix the reported panic is committed as r187223 to HEAD. MFC is set to 1 month, because, mmm, because. The MFC requires mostly mechanical changes of the MAC hook names. pgpPIOrHprK4F.pgp Description: PGP signature
how ipfw firewall is implemented in the kernel
Hi, Can anyone please help me understand how the IPFW firewall is implemented in the kernel. I have created new ACTIONS in ipfw. I have already implemented in the userland. Now i need to check the IPFW rule list (in ip_input.c and in ip_output.c) and call a custom routine if there is a match to those rules. I would really appreciate if anyone could point me to right direction/reference. thanks ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
How to calculate current kmem usage?
Hi, Could someone explain please, how to calculate current kernel memory utilization, one that is limited by vm.kmem_size? There is a script on http://wiki.freebsd.org/ZFSTuningGuide that calculates kernel memory utilization by summing the values from `kldstat' output (TEXT) and the values from `vmstat -m' output (DATA). Are these the only data needed for proper calculation of kmem? What about zone(9) allocations? Shouldn't data from `vmstat -z' output be added to calculate kmem usage? The reason I am asking about this is that we are tuning vfs.ufs.dirhash_maxmem on our storage servers. By default it is 2Mb that looks like very small value. We increased it to 30Mb and all 30Mb were filled very quickly, so we are considering to increase it more but we need the method to monitor the system resources we can hit (we use the default value for vm.kmem_size 300Mb that is not so large). So what the system parameters we should monitor increasing vfs.ufs.dirhash_maxmem? I see the growth of dirhash_maxmem corresponds the growth of wired memory. Currently wired is 222M on this host. Isn't wired memory limited by vm.kmem_size or it is limited only by vm.kvm_size? BTW, how reasonably large the value of vfs.ufs.dirhash_maxmem can be? I have seen recommendations to increase it until it all in usage, but may be there are other considerations I should take into account? We use rsync on our storage servers to synchronize data between the hosts and I suppose this is the main dirhash_mem eater. -- Mikolaj Golub ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how ipfw firewall is implemented in the kernel
On Wednesday 14 January 2009 18:32:07 Biks N wrote:
Hi,
Can anyone please help me understand how the IPFW firewall is
implemented in the kernel.
I have created new ACTIONS in ipfw. I have already implemented in the
userland.
Now i need to check the IPFW rule list (in ip_input.c and in
ip_output.c) and call a custom routine if there is a match to those
rules.
I would really appreciate if anyone could point me to right
direction/reference.
ipfw is hooked into the pfil(9) hook points in ip_{in,out}put() (look for
calls to pfil_run_hooks() in the respective files).
From there the call path goes on to the ipfw_check_* functions defined in
netinet/ip_fw_pfil.c
Finally ipfw_chk() in netinet/ip_fw2.c where the ruleset is processed and
where you should add your required processing.
--
/\ Best regards, | mla...@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mla...@efnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how ipfw firewall is implemented in the kernel
Thanks a lot!
That was really very helpful!!!
On Wed, Jan 14, 2009 at 1:42 PM, Max Laier m...@love2party.net wrote:
On Wednesday 14 January 2009 18:32:07 Biks N wrote:
Hi,
Can anyone please help me understand how the IPFW firewall is
implemented in the kernel.
I have created new ACTIONS in ipfw. I have already implemented in the
userland.
Now i need to check the IPFW rule list (in ip_input.c and in
ip_output.c) and call a custom routine if there is a match to those
rules.
I would really appreciate if anyone could point me to right
direction/reference.
ipfw is hooked into the pfil(9) hook points in ip_{in,out}put() (look for
calls to pfil_run_hooks() in the respective files).
From there the call path goes on to the ipfw_check_* functions defined in
netinet/ip_fw_pfil.c
Finally ipfw_chk() in netinet/ip_fw2.c where the ruleset is processed and
where you should add your required processing.
--
/\ Best regards, | mla...@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mla...@efnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
panic: Going nowhere without my init!
Hi All, Thanks for answering my previous question FreeBSD kernel Debugging tools for Virtual Memory Module, thank you Dag-Erling Smørgrav. Today i made a comment in Getpid() function of sys/kern/kern_prot.c file and i got error of panic: Going nowhere without my init! Can not dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Could anyone help me in solving this error? Thanks Kamlesh MS CS, CSUS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
bg_fsck ignores fstab pass numbers?
Hi, I've noticed that fsck in background mode never checks separate disks in parallel for pass numbers =2, as described in fsck(8). Taking a look at preen.c:checkfstab() (if I understand correctly) reveals that in background mode it will explicitly check each disk in turn (ironically in the foreground), rather than fork them off and queue up waiting for the children. Does anyone know the reason for that? Is it simply a matter of wanting to lower the impact and resource usage on the system? C -- Callum Gibson @ home http://members.optusnet.com.au/callumgibson/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
