From: Stephan von Krawczynski <skraw@ithnet.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: orf@mailbag.com, linux-kernel@vger.kernel.org,
brownfld@irridia.com, andrea@suse.de, akpm@zip.com.au
Subject: Re: 2.4.16 memory badness (reproducible)
Date: Tue, 11 Dec 2001 21:04:12 +0100 [thread overview]
Message-ID: <20011211210412.59491313.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112111850090.1164-100000@localhost.localdomain>
In-Reply-To: <200112082142.fB8LgAb02089@orp.orf.cx> <Pine.LNX.4.21.0112111850090.1164-100000@localhost.localdomain>
On Tue, 11 Dec 2001 19:07:41 +0000 (GMT)
Hugh Dickins <hugh@veritas.com> wrote:
> I believe this error comes, not from a (genuine or mistaken) shortage
> of free memory,
Me, too.
> but from shortage or fragmentation of vmalloc's virtual
> address space. Does patch below (to 2.4.17-pre4-aa1 since I think that's
> what you tried last; easily adaptible to other trees) doubling vmalloc's
> address space (on your 1GB machine or larger) make any difference?
> Perhaps there's a vmalloc leak and this will only delay the error.
At least I think this direction to search the bug looks a lot more promising than a general mem shortage problem. After reviewing modify_ldt this looked like the only useable idea to Leighs problem.
Regards,
Stephan
next prev parent reply other threads:[~2001-12-11 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 15:39 2.4.16 memory badness (reproducible) Leigh Orf
2001-12-08 15:56 ` Ken Brownfield
2001-12-08 18:54 ` Leigh Orf
2001-12-08 19:41 ` Andrew Morton
2001-12-08 20:04 ` Leigh Orf
2001-12-08 21:42 ` Leigh Orf
2001-12-08 22:24 ` Leigh Orf
2001-12-11 19:07 ` Hugh Dickins
2001-12-11 20:04 ` Stephan von Krawczynski [this message]
2001-12-11 22:13 ` H. Peter Anvin
2001-12-11 22:59 ` Andrea Arcangeli
2001-12-12 14:51 ` Leigh Orf
2001-12-18 14:27 ` Holger Lubitz
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=20011211210412.59491313.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=brownfld@irridia.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orf@mailbag.com \
/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.