[SOLVED] 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/25/03

  • Next message: Matthew Dillon: "Re: Problems reclaiming VM cache = XFree86 startup annoyance" 
    To: <stable@FreeBSD.org>, <current@freebsd.org>
Date: Thu, 25 Dec 2003 14:38:42 +0800

    First I would say "thank you" to those who helped me to find the cause of
    the problem. Now I have confirmed that the problem goes away after a kernel
    configuration tuning.

    To trigger the problem, the box must have more than 2GB RAM and the
    following configuration:

    options MAXDSIZ=(1024UL*1024*1024)
    options MAXSSIZ=(128UL*1024*1024)
    options DFLDSIZ=(1024UL*1024*1024)

    A default, say, GENERIC kernel would not trigger panic's during my test.

    The problem exists on 4-STABLE and 5-CURRENT, however, by increasing kernel
    virtual address space by adding a line like the following:

    options KVA_PAGES=512

    The panics goes away.

    I would suggest the following patch against -HEAD to be applied:

    Index: NOTES
    ===================================================================
    RCS file: /home/ncvs/src/sys/conf/NOTES,v
    retrieving revision 1.1192
    diff -u -r1.1192 NOTES
    --- NOTES 7 Dec 2003 04:41:11 -0000 1.1192
    +++ NOTES 25 Dec 2003 06:36:27 -0000
    @@ -89,6 +89,12 @@
     # and explicitly set the maximum with a shell command for processes
     # that regularly exceed the limit like INND.
     #
    +# Adjusting these parameters may result in a larger kernel memory
    +# usage. Thus you may want to enlarge kernel virtual address space.
    +# On a i386 box with more than 2GB of memory and the following
    +# options, KVA_PAGES=512 would be helpful to solve some fork related
    +# kernel panics.
    +#
     options MAXDSIZ=(1024UL*1024*1024)
     options MAXSSIZ=(128UL*1024*1024)
     options DFLDSIZ=(1024UL*1024*1024)

    Thank you again for your help!

    _______________________________________________
    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: Matthew Dillon: "Re: Problems reclaiming VM cache = XFree86 startup annoyance"

    Relevant Pages

    • Re: [2.6.27] filesystem (ext3) corruption (access beyond end)
      ... Ok I ran several disk-intensive jobs (git clone, kernel build, apt-get dist-upgrade) ... but none of those could trigger any bugs. ... BUT, running my http://vanheusden.com/pyk/ script, I definately can trigger the ...
      (Linux-Kernel)
    • Re: 2.6.19 file content corruption on ext3
      ... actually just expose a long-time userspace bug that was just a LOT harder ... Maybe the reason this is so easy to trigger with rtorrent is not because ... rtorrent does some magic pattern that triggers a kernel bug, ... whenever we do an _expanding_ truncate, ...
      (Linux-Kernel)
    • Fw: Re: [2.6.27] filesystem (ext3) corruption (access beyond end)
      ... Ok I ran several disk-intensive jobs (git clone, kernel build, apt-get dist-upgrade) ... but none of those could trigger any bugs. ... BUT, running my http://vanheusden.com/pyk/ script, I definately can trigger the ...
      (Linux-Kernel)
    • Re: Panic when finishing raidreconf on 2.4.0-test4 with preempt
      ... A preempt error is triggered and the kernel ... *) an API change combined with missing error handling, which raidreconf ... perhaps calling mkraid after beating ... the VM half way to death can trigger the same error? ...
      (Linux-Kernel)
    • Re: echo mem > /sys/power/state
      ... kprobes had similar problems and it now has a few simple smoke-tests ... - which i just saw trigger on a patch that i did not notice would ... getting out of sync with the kernel (and its capabilities enabled in the ... the testing barrier increases significantly. ...
      (Linux-Kernel)