[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: kmem_malloc crashes running FreeBSD 5.2.1-RELEASE-p5
From:       Kris Kennaway <kris () obsecurity ! org>
Date:       2004-04-29 0:01:58
Message-ID: 20040429000158.GA61693 () xor ! obsecurity ! org
[Download RAW message or body]


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 
> script.
> 
> I am able to crash this system at will (takes about 5-10 minutes by 
> running the
> security scripts in a loop and using gtar to copy files to the server at 
> the same
> time. I have included output from one core dump below. The other core dumps
> I have so far are almost exactly the same e.g. "Error accessing memory 
> address
> 0xf8b7983c" is the same in all core dumps so far.
> 
> 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 same problem running 4.9 but were able to 
> fix it
> by setting the MAXMEM option in our kernel conf file to a value 1GB less 
> than
> actual physical memory size. This does not help with 5.2.1-RELEASE-p5.
> 
> My group is under pressure to bring 3 of these servers on-line for our user
> community by the end of the month and would greatly appreciate any help
> in resolving this problem.

See PR 53416.  You just need to tune your kernel resource allocation
to deal with the large amount of memory your system has.

Kris

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]