From: Ville Herva <vherva@viasys.com>
To: Andrew Morton <akpm@osdl.org>
Cc: petr@vandrovec.name, linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1-mm2 breaks vmware
Date: Fri, 20 Aug 2004 17:43:04 +0300 [thread overview]
Message-ID: <20040820144304.GF8307@viasys.com> (raw)
In-Reply-To: <20040820131825.GI23741@viasys.com>
On Fri, Aug 20, 2004 at 04:18:25PM +0300, you [Ville Herva] wrote:
>
> I just noticed I had missed get_user_pages-handle-VM_IO.patch - I'll try
> backing that out first. I'll report back if I find anything interesting
> with different patch mixtures.
Well, I just tried 2.6.8.1-mm2 minus get_user_pages-handle-VM_IO.patch but
that didn't help with the "cannot allocate memory" problem. Curiously, I
didn't get the "get_user_pages() returns -EFAULT" warning with this kernel.
Also, neither "echo 1 > /proc/sys/vm/overcommit_memory" nor "echo 1 >
/proc/sys/vm/legacy_va_layout" helped.
It seems this is "cannot allocate memory" might have something to do with
/dev/mem mmap() permissions - here's a strace:
--8<-----------------------------------------------------------------------
5022 geteuid32() = 1414
5022 setresuid32(-1, 0, -1) = 0
5022 open("/dev/mem", O_RDWR) = 8
5022 getuid32() = 1414
5022 setresuid32(-1, 1414, -1) = 0
5022 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x3d6000) = -1 EPERM (Operation not permitted)
5022 close(8) = 0
5022 ioctl(4, 0xf0, 0x3d6000) = 0
5022 time(NULL) = 1093011756
5022 open("/etc/localtime", O_RDONLY) = 8
5022 fstat64(8, {st_mode=S_IFREG|0644, st_size=682, ...}) = 0
5022 close(8) = 0
5022 writev(3, [{"Aug 20 17:22:36: ", 17}, {"VMX|", 4}, {"Msg_Post: Error\n", 16}], 3) = 37
5022 writev(3, [{"Aug 20 17:22:36: ", 17}, {"VMX|", 4}, {"[msg.msg.noMem] Cannot allocate "..., 40}], 3) = 61
5022 writev(3, [{"Aug 20 17:22:36: ", 17}, {"VMX|", 4}, {"--------------------------------"..., 41}], 3) = 62
--8<-----------------------------------------------------------------------
I just put get_user_pages-handle-VM_IO.patch back and reverted
dev-mem-restriction-patch.patch - I'll report back when it has compiled.
-- v --
v@iki.fi
next prev parent reply other threads:[~2004-08-20 14:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 10:42 2.6.8.1-mm2 breaks vmware Ville Herva
2004-08-20 10:51 ` Andrew Morton
2004-08-20 13:18 ` Ville Herva
2004-08-20 14:43 ` Ville Herva [this message]
2004-08-20 15:16 ` Ville Herva
2004-08-20 18:45 ` Andrew Morton
2004-08-20 18:49 ` Arjan van de Ven
2004-08-20 19:30 ` Ville Herva
2004-08-22 11:42 ` Tonnerre
2004-08-22 13:59 ` Petr Vandrovec
2004-08-22 14:15 ` Alan Cox
2004-08-20 19:25 ` Ville Herva
2004-08-21 6:29 ` Ville Herva
[not found] ` <20040821134918.GA1585@devserv.devel.redhat.com>
[not found] ` <20040821190027.GQ3024@viasys.com>
[not found] ` <20040821190730.GA25932@devserv.devel.redhat.com>
2004-08-22 14:31 ` Petr Vandrovec
2004-08-22 15:07 ` Arjan van de Ven
2004-08-22 21:19 ` Ville Herva
2004-08-23 5:53 ` [OT] vmware, 2.6 kernel and altgr key (Re: 2.6.8.1-mm2 breaks vmware) Ville Herva
2004-08-20 12:11 ` 2.6.8.1-mm2 breaks vmware Arjan van de Ven
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=20040820144304.GF8307@viasys.com \
--to=vherva@viasys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
/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