Am 04.05.2004 um 01:11 schrieb Kris Kennaway:
I'm pretty sure it's just a matter of the right tuning. All I needed
to do was to add this on my heavily loaded 4GB machine:
options VM_KMEM_SIZE_MAX=419430400 #400MB
Thanks, that appears to have resolved the issue. I encountered no more
On Mon, May 03, 2004 at 08:19:43AM -0700, John Uhlig wrote:
>
> Well, Don Bowman was very helpful in suggesting some kernel parameters.
> Unfortunately, they
> did not work for us. If we had the time to experiment with more
> settings, perhaps we would have
> been able to find the right combinat
Well, Don Bowman was very helpful in suggesting some kernel parameters.
Unfortunately, they
did not work for us. If we had the time to experiment with more
settings, perhaps we would have
been able to find the right combination. Since we do not have that time
due to our schedule I was
forced to
Am 29.04.2004 um 02:01 schrieb Kris Kennaway:
On Wed, Apr 28, 2004 at 02:40:38PM -0700, John Uhlig wrote:
On the web, freebsd mailing lists and bug lists, I have seen existing
thread about "kmem_malloc and kmem_map too small" problems - but no
evidence of a fix or patch. We experienced the sam
On Wed, Apr 28, 2004 at 02:40:38PM -0700, John Uhlig wrote:
> Hi.
>
> We are running FreeBSD 5.2.1-RELEASE-p5 with a fairly generic kernel on a
> Dell PowerEdge 2650 with 1/2TB of disk RAID arrays. It recently crashed at
> about 3AM while running the daily /etc/periodic/security/100.chksetuid
> s
Hi.
We are running FreeBSD 5.2.1-RELEASE-p5 with a fairly generic kernel on a
Dell PowerEdge 2650 with 1/2TB of disk RAID arrays. It recently crashed at
about 3AM while running the daily /etc/periodic/security/100.chksetuid
script.
I am able to crash this system at will (takes about 5-10 minutes
6 matches
Mail list logo
