Re: >2GB Bugs still exist in FreeBSD 4.9 ?
From: Gerrit Nagelhout (gnagelhout_at_sandvine.com)
Date: 02/24/04
- Previous message: David Wolfskill: "Re: Can't kill process"
- Maybe in reply to: Phil Rosenthal: ">2GB Bugs still exist in FreeBSD 4.9 ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org> Date: Tue, 24 Feb 2004 15:31:05 -0500
I think this problem happens when the kernel_map runs out of memory. The
actual crash happens because in vfs_subr.c around line 704, if zalloc
returns NULL, the bzero will cause that trap:
simple_unlock(&vnode_free_list_slock);
vp = (struct vnode *) zalloc(vnode_zone);
bzero((char *) vp, sizeof *vp); ******************
simple_lock_init(&vp->v_interlock);
vp->v_dd = vp;
cache_purge(vp);
LIST_INIT(&vp->v_cache_src);
TAILQ_INIT(&vp->v_cache_dst);
numvnodes++;
The size of the kernel memory region can be configured, and is typically
around 1GB. The more RAM is present in the system, the more of this will be
used up by various data structures that are tuned differently depending how
much RAM is present. I think there are a few more places where running out
of kernel memory will cause similar problems. Most of these places don't
seem trivial to fix, and the only solution I have come up with (so far) is
to tune the kernel differently to leave more memory available.
Gerrit
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
- Previous message: David Wolfskill: "Re: Can't kill process"
- Maybe in reply to: Phil Rosenthal: ">2GB Bugs still exist in FreeBSD 4.9 ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
