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

From: Sten (sten_at_blinkenlights.nl)
Date: 12/25/03

  • Next message: Thorsten Steentjes: "Re: possible (kernel) bug with zebra"
    Date: Thu, 25 Dec 2003 19:20:48 +0100 (CET)
    To: Xin LI/李鑫 <delphij@frontfree.net>
    
    

    On Thu, 25 Dec 2003, [gb2312] Xin LI/李鑫 wrote:

    > 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'd really love getting rid of most hardcoded memory allocations
    in the fbsd kernel, with the main bugger being NMBCLUSTERS,
    which one always forgets about untill it's too late :(.
    In solaris auto-tuning has been a top priority for a long while,
    and propper dynamic tuning should get it right ( or even better )
    in 99% of the cases. People with other needs should be able
    to build a custom kernel.

    Maybe a nice goal for 6.0 :)

    I do have to note that fbsd5 has been getting better and better,
    on sparc64 it beats out linux and netbsd for my purposes.
    Good work.

    -- 
    Sten Spans
    There is a crack in everything that's how the light gets in.
    _______________________________________________
    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: Thorsten Steentjes: "Re: possible (kernel) bug with zebra"

    Relevant Pages

    • Re: [SOLVED] RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic on RAM > 4GB without PAE (long)
      ... On Thu, 25 Dec 2003, Xin LI/李鑫 wrote: ... > configuration tuning. ... > A default, say, GENERIC kernel would not trigger panic's during my test. ...
      (freebsd-current)
    • 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)
    • 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)
    • Re: 2.6.21.5 june 30th to july 1st date hang?
      ... As far as I can tell many kernel versions contained the source code bug. ... in order to trigger the problem you also need to have NTP ... servers that were erroneously broadcasting the addition of a leap second. ...
      (Linux-Kernel)