From: Andrea Arcangeli <andrea@suse.de>
To: Hong-Gunn Chew <hgchewML@optusnet.com.au>
Cc: "'Petr Vandrovec'" <VANDROVE@vc.cvut.cz>,
"'Linux kernel mailing list'" <linux-kernel@vger.kernel.org>,
riel@conectiva.com.br
Subject: Re: Memory corruption when running VMware. (was File curruption when running VMware)
Date: Fri, 3 May 2002 10:08:03 +0200 [thread overview]
Message-ID: <20020503100803.J11414@dualathlon.random> (raw)
In-Reply-To: <37A7BD60863@vcnet.vc.cvut.cz> <001701c1f24d$b7e50e10$241d7f81@hgclaptop>
On Fri, May 03, 2002 at 12:23:35PM +0930, Hong-Gunn Chew wrote:
> Hi Petr, Andrea,
>
> Petr wrote:
> > So if you have >890MB of RAM and your kernel is compiled
> > with support for pte in high memory, please stop using
> > VMware, or reconfigure your
> > kernel to not use pte in high memory (4GB config without
> > pte-in-highmem is OK). Using pte-in-highmem with vmmon will
> > cause kernel oopses and/or
> > memory corruption :-(
>
> I have been trying different kernel configurations to overcome this
> problem. I found that turning on APIC seem to work properly. However
> turning on IO-APIC causes it to hang just after X is started, which
> seems to be during the startup of gdm.
> I do have a silly question to ask though. How do I compile the kernel
> NOT to use pte in high memory?
the simplest patch to avoid pte in highmem is this. It's against 19pre7aa3
but it will apply cleanly to the kernel you're using.
--- 2.4.19pre7aa3/mm/memory.c.~1~ Tue Apr 30 19:53:08 2002
+++ 2.4.19pre7aa3/mm/memory.c Fri May 3 09:58:23 2002
@@ -1493,7 +1493,7 @@
{
struct page * page;
- page = alloc_page(GFP_KERNEL | __GFP_HIGHMEM);
+ page = alloc_page(GFP_KERNEL);
if (page)
clear_pagetable(page);
return page;
However if I would be in you I'd simply add mem=850M to the append line
in /etc/lilo.conf until the vmmon/vmnet update is released, that should
be the most confortable approch from your part.
> Andrea wrote:
> > passing to the kernel mem=850M in lilo at boot will be enough.
>
> This did not work as it causes vmware to seg fault with a kernel oops:
Hmm looking at the bounce_end_io_read it looks like the kernel didn't
recognized you specified mem=850M via lilo, not idea why. You should
check with `free` that your kernel is using only 850M of ram before
starting vmware. Can you show the contents of /proc/meminfo right after
boot?
> [generic_file_readahead+288/304] [bounce_end_io_read+164/288]
> [isapnp_set_mem+23/272] [vfs_link+23/256] [system_call+51/56]
> [<f61fd5d1>] [<c01272b0>] [<c0131e94>] [<c01e0527>]
> [<c013e487>] [<c0106f0b>]
>
> Code: 8b 11 89 d0 25 00 07 01 00 3d 00 04 00 00 75 12 81 ca 00
> 00
>
> Cheers,
> Hong-Gunn
Andrea
next prev parent reply other threads:[~2002-05-03 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 15:30 File corruption when running VMware Petr Vandrovec
2002-04-26 16:14 ` Hong-Gunn Chew
2002-04-26 23:01 ` Andrea Arcangeli
2002-04-26 23:56 ` Andrea Arcangeli
2002-04-27 0:00 ` Andrea Arcangeli
2002-04-27 15:36 ` Andrea Arcangeli
2002-05-03 2:53 ` Memory corruption when running VMware. (was File curruption when running VMware) Hong-Gunn Chew
2002-05-03 8:08 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 3:07 Hong-Gunn Chew
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=20020503100803.J11414@dualathlon.random \
--to=andrea@suse.de \
--cc=VANDROVE@vc.cvut.cz \
--cc=hgchewML@optusnet.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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