linux-um archives
 help / color / mirror / Atom feed
From: james donald <svc5354@yahoo.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] highmem support
Date: Tue, 23 Sep 2003 10:01:27 -0700 (PDT)	[thread overview]
Message-ID: <20030923170127.8475.qmail@web80606.mail.yahoo.com> (raw)

highmem support is current broken. although i am able
to compile with highmem support with
uml-patch-2.4.20-6 but i am getting kernel panic when
running with mem=2048M

any idea which was the last version with working
highmem support?

-james

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

                 reply	other threads:[~2003-09-23 17:02 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=20030923170127.8475.qmail@web80606.mail.yahoo.com \
    --to=svc5354@yahoo.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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