Re: Large mem disk with not very recent current

From: Roman Kurakin (rik_at_cronyx.ru)
Date: 09/14/04

  • Next message: Roman Kurakin: "Re: Large mem disk with not very recent current" 
    Date: Wed, 15 Sep 2004 00:57:42 +0400
To: Scott Long <scottl@samsco.org>

    Scott Long wrote:

    > Roman Kurakin wrote:
    >
    >> Kris Kennaway wrote:
    >>
    >>> On Mon, Sep 13, 2004 at 12:56:51PM +0400, Roman Kurakin wrote:
    >>>
    >>>> Hi,
    >>>>
    >>>> I have the following idea/problem. I want to build world in memory.
    >>>> I've put in to my system 1G of memory and tried to put on it sources.
    >>>> But all times I've tried to do that system went to panic. I've used md
    >>>> with malloc type.
    >>>>
    >>>> Any ideas?
    >>>>
    >>>
    >>>
    >>> Please provide more information. It's likely you're trying to create
    >>> a md that is too big, though.
    >>>
    >> It is about 800Mb. But system panics while I try to extract source
    >> tree. It is not very recent
    >> current. The intent of my question was to get some hints how to set
    >> up such build area, I
    >> belive it should help to make compilation much faster than using hard
    >> drive. My home system
    >> is not ready for panic investigation now. I'll update it to current
    >> and set console to it and will
    >> try again.
    >>
    >>
    >> PS. Sorry to all for my last posts to current that are so weak in
    >> "technical" details, the debug
    >> technique I used before was without remote debugging since most of
    >> problems were very
    >> near my code and it was enough for me anlo three things: my mind,
    >> printed sources, and printf.
    >> So now I am in stage of adaptation to/setting up remote debugging.
    >>
    >> rik
    >
    >
    > What kind of panic was it? Try using swap backing instead of malloc.

    kmem_map too small.

    > Malloc will consume wired memory and will generally make life difficult
    > for other parts of the kernel that need memory later. Swap-backed pages
    > will stay in RAM until the VM needs to push them out due to memory
    > pressure.

    Ok. I'll try to try this this night.

    Thanks.

    rik

    > Scott
    >
    >

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

  • Next message: Roman Kurakin: "Re: Large mem disk with not very recent current"

    Relevant Pages

    • Re: Microsoft Word wont load on my iMac G4 after kernel panic
      ... that it is hardware related, but I've found that an archive and install ... fixes it for about another 6 mos to a year (and they the panics return). ... reported there was 6 weeks ago, and said there was a memory exception ... /Library/Logs contains your panic reports. ...
      (microsoft.public.mac.office.word)
    • Re: Large mem disk with not very recent current
      ... But system panics while I try to extract source tree. ... > So now I am in stage of adaptation to/setting up remote debugging. ... Try using swap backing instead of malloc. ... Malloc will consume wired memory and will generally make life difficult ...
      (freebsd-current)
    • panic in raid1_end_write_request
      ... I have a Dell PE2650, Dual Xeon, 1G memory and several software raid1 ... kernel 2.6.10-1.747_FC3smp which includes 2.6.10-ac10. ... This system panics frequently, between several hours to several days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: panic: vm_thread_swapin: cannot get kstack for proc: 643 under high memory load
      ... System was under high memory ... > load due to a run-away pine process that was also generating a very high ... > there was no memory into which to load the stack?). ... In other words, vm_thread_swapinpanics if there ...
      (freebsd-stable)
    • Re: quick interactivity? question regarding -current
      ... as suggested by someone a month ago because I was having panics ... | a core dump ... I didn't know about vmstat -m until the other day, ... maybe that would help me determine what was up if it's due to a memory ...
      (freebsd-current)