RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic on RAM > 4GB without PAE (long)

From: Xin LI/李鑫 (delphij_at_frontfree.net)
Date: 12/18/03

  • Next message: Peter Jeremy: "Partial deadlock in 4.9p1"
    To: "'Doug White'" <dwhite@gumbysoft.com>
    Date: Thu, 18 Dec 2003 14:46:28 +0800
    
    

     

    > -----Original Message-----
    > From: Doug White [mailto:dwhite@gumbysoft.com]
    > Sent: Thursday, December 18, 2003 8:58 AM
    > To: Xin LI/李鑫
    > Cc: stable@FreeBSD.org; current@freebsd.org
    > Subject: Re: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic
    > on RAM > 4GB without PAE (long)
    >
    > PAE only has effect for >4GB (strictly), so exactly 4GB will
    > work fine with !PAE.
    Oh... I am aware of this issue, however, only machines have RAM > 4GB expose
    the problem. So I suspect that something has triggered the problem in 4GB
    w/o PAE case. Because the system will not even boot into single user mode
    under a PAE configuration, I was unable to provide any useful information
    about the PAE case.

    I guess that there is some race condition inside the vm or pmap code.
    However, after a preliminary research on these code I did not found problem.

    > 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.
    When we have removed some RAM, in other words, install 2GB memory on the
    box, the panic's goes away. Please note that the problem is not due to
    defective RAM chips as we have tested all possible combinations and the
    problem persists.

    >
    > 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.
    Oh... I think this is important, however, I got no reason why a server
    running ordinary service will cause panic when heavy load.

    Implementing a forkbomb is a Bad Idea(tm), but I will still argue that our
    daily run and crashdumps shows that this panic is mostly fork-and-malloc
    related, so we have the test program, and it triggered similar panic as we
    have. Because that our panic could not be easily to reproduce, and the two
    panic's were so similiar, I think they might be the same problem.

    In addition, IMHO, a userland program should never cause a kernel-panic if
    the kernel is implemented very well without any flaw. As I mentioned in last
    letter, on a configuration having 2GB of RAM, the system seemed to be
    rock-solid. That's why I have the ugly proof code...

    > > panic: pmap_new_proc: u_map allocation failed
    >
    > kmem exhaustion condition in -stable.
    Er... Is this problem only -STABLE related? Thanks!

    Xin LI

    _______________________________________________
    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"


  • Next message: Peter Jeremy: "Partial deadlock in 4.9p1"

    Relevant Pages

    • Re: Using all of 4GB RAM... questions and Vista versus Linux...
      ... Even though I have 4GB of RAM installed, Linux appears to only be using ... thus creating a memory "hole". ... First is the PAE kernel. ...
      (Fedora)
    • Re: 4.10-RELEASE and -STABLE crashing regularly under load
      ... This is the number one problem on systems with 2GB+ of RAM ... > whether i'm really using pae, and in either case, ... You would set it in your kernel config and then rebuild the kernel. ...
      (freebsd-hackers)
    • Re: performance: store.exe uses 579Mb only out of 4Gb
      ... RAM is mainly used by store.exe in the form of database page buffers. ... You'll find more information on optimizing memory for Exchange in: ... The fact that you're using optin implies that you have a server based on ... response from the vendor is to do something to enable PAE, ...
      (microsoft.public.exchange.admin)
    • RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic on RAM > 4GB without PAE (long)
      ... > work fine with!PAE. ... vmstat -m is useful to keep track of kernel memory use. ... When we have removed some RAM, in other words, install 2GB memory on the ... I think this is important, however, I got no reason why a server ...
      (freebsd-current)
    • Re: 4GB RAM with an intel core 2 processor
      ... When I install the 2 extra memory modules, the kernel tells me on startup ... I took a quick look at PAE and discovered that the PAE kernel is ... Do I have any options for using my 4GB of RAM and still retain USB and the nvidia driver? ...
      (freebsd-current)