RE: 4.9 boot problem on em0 platform.

From: Don Bowman (don_at_sandvine.com)
Date: 02/29/04

  • Next message: Deepak Jain: "Re: 4.9 boot problem on em0 platform."
    To: 'Deepak Jain' <deepak@ai.net>, freebsd-hackers@freebsd.org
    Date: Sun, 29 Feb 2004 15:40:44 -0500
    
    

    > From: Deepak Jain [mailto:deepak@ai.net]
    > As a part of tracking down a performance issue, I tried building a
    > custom kernel (with just IPFW, DUMMYNET added, NMBCLUSTERS,
    > commenting
    > out MATH_EMULATE, INET6, I386, I486). The system is currently
    > running a
    > kernel from a similar machine with the same settings. The
    > machine does
    > run on this kernel: 4.9-RELEASE FreeBSD 4.9-RELEASE #8, with
    > the above
    > options, but I have not been able to compile a 4.9-RELEASE #2
    > (which is
    > the source tree on the machine) kernel that has an identical
    > config file.
    >
    > So, when it builds itself from -RELEASE sources, it hangs at:
    >
    > "pmap_mapdev: Couldn't alloc kernel virtual memory" I couldn't find a
    > reference to anything recent. Nothing non-default (from a GENERIC
    > kernel) with respect to ACPI has been touched. I see a reference to
    > -CURRENT from 9/03, but that's it.

    Just a guess, but i think you've bumped nmbclusters or nmbufs up
    too much (or perhaps maxsockets, maxfds, ...) and have run out of
    KVA.

    You can tune clusters & mbufs in loader.conf without recompiling
    kernel. You will want to see what vm.zone_kmem_pages, vm.zone_kmem_kvaspace
    are showing you, vmstat -z, vmstat -m, etc.

    You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are
    trying to put more into the kernel mem space.

    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


  • Next message: Deepak Jain: "Re: 4.9 boot problem on em0 platform."

    Relevant Pages

    • Re: FreeBSD 5.1-R kernel panic
      ... As far as changing the nmbclusters, I'm not sure how many I use now. ... I took a quick look at the developers handbook and couldn't find just ... yet what I needed to change to the kernel to provide a stack trace... ... I can probably run on one CPU for a few days, ...
      (freebsd-current)
    • Re: [SOLVED] RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic
      ... > in the fbsd kernel, with the main bugger being NMBCLUSTERS, ... You need _not_ to build custom FreeBSD kernel in order to increase ... Atlantis ISP, System Administrator ...
      (freebsd-current)
    • Re: [SOLVED] RE: [Backtrace] 4.9 and 5.1-RELEASE occasionly panic
      ... > in the fbsd kernel, with the main bugger being NMBCLUSTERS, ... You need _not_ to build custom FreeBSD kernel in order to increase ... Atlantis ISP, System Administrator ...
      (freebsd-stable)
    • Re: FreeBSD 5.1-R kernel panic
      ... > As far as changing the nmbclusters, I'm not sure how many I use now. ... > yet what I needed to change to the kernel to provide a stack trace... ... to get a stack trace. ... if you only have remote access to ...
      (freebsd-current)
    • Re: WARNING: mclpool limit reached; increase NMBCLUSTERS
      ... you have to increase NMBCLUSTERS in the kernel... ... ukc> nmbclust ... [root@cyanide root]# ls /bsd* ...
      (comp.unix.bsd.openbsd.misc)