All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] x86_64 when mem > 384M loadable modules do not work
Date: Thu, 28 Nov 2013 16:47:13 +0100	[thread overview]
Message-ID: <11957281.y1PM5USAYd@sandpuppy> (raw)
In-Reply-To: <529755F0.80509@panasas.com>

Am Donnerstag, 28. November 2013, 16:40:48 schrieb Boaz Harrosh:
> Hi um hackers
> 
> I'm using an x86_64 deployment both host and um-guest.
> (Fedora 18)
> 
> When I load with mem=384M all is well but anything bigger will
> eventually give me problems because loadable modules will no
> longer load. The bigger mem= is, the earlier it will start.
> 
> When the Kernel tries to load the .ko driver I get these messages:
> 
> subarch: overflow in relocation type 11 val 805b1e40
> subarch: `nfsv4' likely not compiled with -mcmodel=kernel
> subarch: overflow in relocation type 11 val 806e4ca0
> subarch: `nfsv3' likely not compiled with -mcmodel=kernel
>    ...
> 
> (The first print is always around that same number
>  805b1e40 independent of the mem= (> 384M)
> )
> 
> Do you guys see the same problem? I'm using loadable modules
> because it is kind of mandatory for the kind of development I
> do.
> 
> Please help because 384M is not enough for me anymore, even
> when I define a swap device for the uml to use.

/me has a deja vu.
I've fixed that issue some time ago.

Let's see why it happens again. :)

Thanks,
//richard

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
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:[~2013-11-28 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 14:40 [uml-devel] x86_64 when mem > 384M loadable modules do not work Boaz Harrosh
2013-11-28 15:47 ` Richard Weinberger [this message]
2013-11-28 16:09 ` Richard Weinberger
2013-12-01 11:46   ` Boaz Harrosh

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=11957281.y1PM5USAYd@sandpuppy \
    --to=richard@nod.at \
    --cc=bharrosh@panasas.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 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.