From: Holger Lubitz <h.lubitz@internet-factory.de>
To: linux-kernel@vger.kernel.org
Subject: Re: modify_ldt returning ENOMEM on highmem
Date: Tue, 18 Dec 2001 15:19:34 +0100 [thread overview]
Message-ID: <3C1F5076.3B6A509E@internet-factory.de> (raw)
In-Reply-To: <200112171852.fBHIqJR05703@orp.orf.cx>
Leigh Orf proclaimed:
> Do you have an NTFS disk mounted? I had a similar problem which was
> "fixed" by not having an NTFS vol mounted. Apparently the ntfs code
> makes a lot of calls to vmalloc which leads to badness.
Yes, I have. I'll try not mounting it. Which would be a better
workaround than disabling 1/8 of my RAM.
The funny thing is just - why does it work fine with up to 896 MB, but
gives ENOMEM with _more_ RAM?
Holger
next prev parent reply other threads:[~2001-12-18 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 18:52 Leigh Orf
2001-12-18 14:19 ` Holger Lubitz [this message]
2001-12-18 14:50 ` Brian Gerst
2001-12-17 19:20 Manfred Spraul
2001-12-18 3:40 ` Leigh Orf
[not found] ` <Your message of "Mon, 17 Dec 2001 20:20:25 +0100." <3C1E4579.4A46F32F@colorfullife.com>
2001-12-18 9:08 ` Anton Altaparmakov
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=3C1F5076.3B6A509E@internet-factory.de \
--to=h.lubitz@internet-factory.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome