lkml.org 
[lkml]   [2002]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: Memory corruption when running VMware. (was File curruption when running VMware)
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.066 / U:2.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site