From: David VomLehn <dvomlehn@cisco.com>
To: linux-mips@linux-mips.org
Subject: NFS mount fails with CONFIG_HIGHMEM on MIPS 24Kc system on 2.6.24
Date: Fri, 15 Feb 2008 12:17:45 -0800 [thread overview]
Message-ID: <47B5F369.7060600@cisco.com> (raw)
We have a 2.6.24final port to a MIPS 24Kc-based system which works
normally without CONFIG_HIGHMEM enabled. When we enable HIGHMEM, the
system boots normally using a CRAMFS root filesystem. If we use an NFS
root filesystem, however, it appears to go through a normal boot,
including the freeing of init memory, but then just sits indefinitely in
r4k_wait().
I can see that using HIGHMEM enables use of kmap_atomic in networking
code. Are there issues with networking or NFS with HIGHMEM enabled?
--
David VomLehn, dvomlehn@cisco.com
The opinions expressed herein are likely mine, but might not be my employer's...
reply other threads:[~2008-02-15 20:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47B5F369.7060600@cisco.com \
--to=dvomlehn@cisco.com \
--cc=linux-mips@linux-mips.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