From: Zan Lynx <zlynx@acm.org>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Nick Cheng <nick.cheng@areca.com.tw>,
Erich Chen <erich@areca.com.tw>,
kopi@linuxbox.cz
Subject: Re: arcmsr & areca-1660 - strange behaviour under heavy load
Date: Tue, 26 Feb 2008 14:04:12 -0700 [thread overview]
Message-ID: <1204059852.665822.13.camel@localhost> (raw)
In-Reply-To: <alpine.LRH.0.9999.0802262018230.14724@linuxbox.linuxbox.cz>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Tue, 2008-02-26 at 20:29 +0100, Nikola Ciprich wrote:
> Hi Andrew,
> no, right now I have the machine in the weird state, swap is empty (3GB),
> and so is bigger part of RAM (~100MB free), and the gcc crashes even when
> trying to compile c program with empty main function. so it doesn't seem
> to be problem with memory exhaustion.
Maybe memory fragmentation? Perhaps the driver tries to allocate a
large block of memory and cannot find a continuous block of the right
size.
Maybe the driver developers used different kernel .config options than
you are using.
Try increasing the value in /proc/sys/vm/min_free_kbytes.
Try switching some things like SLAB or SLUB, try booting with
kernelcore=512M to enable the Movable memory zone, or try 64-bit vs
32-bit kernels.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-27 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 11:20 arcmsr & areca-1660 - strange behaviour under heavy load Nikola Ciprich
2008-02-25 0:10 ` Andrew Morton
2008-02-26 9:35 ` Nikola Ciprich
2008-02-26 10:30 ` nickcheng
2008-02-26 10:30 ` nickcheng
2008-02-26 17:43 ` Andrew Morton
2008-02-26 19:29 ` Nikola Ciprich
2008-02-26 21:04 ` Zan Lynx [this message]
2008-02-27 1:53 ` nickcheng
2008-02-27 1:53 ` nickcheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1204059852.665822.13.camel@localhost \
--to=zlynx@acm.org \
--cc=akpm@linux-foundation.org \
--cc=erich@areca.com.tw \
--cc=extmaillist@linuxbox.cz \
--cc=kopi@linuxbox.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nick.cheng@areca.com.tw \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.