[Backtrace] 4.9 and 5.1-RELEASE occasionly panic on RAM > 4GB
without PAE (long)
dwhite at gumbysoft.com
Wed Dec 17 16:58:14 PST 2003
On Thu, 18 Dec 2003, [gb2312] Xin LI/=C0=EE=F6=CE wrote:
> One of my friend is operating servers on a big ICP in China. They found t=
> if they run FreeBSD 4.9 or FreeBSD 5.1-RELEASE on their server, which has
> more than 4GB RAM installed, then they will occasionaly have the server
> panic'ed, or even rebooted without any reason.
> The server hardware is: P4-Xeon-2.4G*2, 4G RAM(DDR266), 146G*2 on asr(4)
> RAID-1. The kernel is not quite different from GENERIC, except that we ha=
> AUTO_EOI1 enabled. When PAE is enabled, then the kernel will not recogniz=
> the asr(4) device, and thus would refuse to boot from it, so we have it
PAE only has effect for >4GB (strictly), so exactly 4GB will work fine
> This problem afffects 4.9-RELEASE and 5.1-RELEASE. As the ICP is a
> conservative user, they will not run -STABLE, nor -CURRENT. I have turned
> the debugging symbols on their server and grabbed the following backtrace=
> Also, I have found how to reproduce this problem on a machine running wit=
> 4GB memory without a PAE configuration, which, in my opinion, should not
> cause a kernel panic because it's just a resource hungry program and all =
> will do should, at most, hang the system, or even being killed directly b=
> the operating system.
Its probably due to poor tuning in this case. See the tuning(7) man page
and innumerable mailing lists posts. Basically, you want to turn down
maxusers (128 or so works best) and maybe change the kernel/user boundary
and kmem sizes. vmstat -m is useful to keep track of kernel memory use.
Also forkbombs (which is what your program is, effectively) are best
controlled by using user resource limits. They're there for a reason. See
the login.conf(5) man page.
> panic: pmap_new_proc: u_map allocation failed
kmem exhaustion condition in -stable.
Doug White | FreeBSD: The Power to Serve
dwhite at gumbysoft.com | www.FreeBSD.org
More information about the freebsd-stable