nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D acceleration (http://www.nvnews.net/vbulletin/showthread.php?t=160035)

rnissl 02-25-11 05:46 PM

270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D acceleration
 
1 Attachment(s)
Hi,

this is a sample error message:
Code:

*** glibc detected *** /usr/lib/vmware/bin/vmware-vmx: malloc(): memory corruption: 0x000000000131cfe0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x73226)[0x7f1e02352226]
/lib64/libc.so.6(+0x75521)[0x7f1e02354521]
/lib64/libc.so.6(__libc_malloc+0x79)[0x7f1e02356aa9]
/usr/lib64/libX11.so.6(_XReply+0xda)[0x7f1e034f8bea]
/usr/lib64/libGL.so.1(+0x78ba3)[0x7f1d3f62eba3]
======= Memory map: ========

It happens at random times (most likely when the Windows 7 x64 login screen appears or when you re-run the assessment in control panel performance information and tools) when the virtual machine is configured to accelerate 3D graphics. I did not see this issue with 260.19.36 and earlier versions.

Bye.

Licaon 02-25-11 06:39 PM

Re: 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D accelera
 
Any reason you have 2 Screen and 2 Monitor sections in xorg.conf ?


also, do try the MTRR trick: http://www.nvnews.net/vbulletin/show...8&postcount=39

rnissl 02-26-11 08:58 AM

Re: 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D accelera
 
Hi,

Quote:

Originally Posted by Licaon (Post 2397095)
Any reason you have 2 Screen and 2 Monitor sections in xorg.conf ?

And 2 Device sections too. Looks like openSuse's Sax chooses different identifiers than nvidia-xconfig, but the latter generated sections are active.

Quote:

Originally Posted by Licaon (Post 2397095)

Adding the kernel command line arguments did have an impact on what cat /proc/mtrr outputs, but it didn't change or correct the reported memory corruption.

Bye.

rnissl 03-29-11 04:44 PM

Re: 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D accelera
 
Hi,

I think this report is related to mine:
http://www.nvnews.net/vbulletin/show...51&postcount=6

Bye.

rnissl 04-03-11 03:41 AM

Re: 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D accelera
 
Hi,

I just wanted to note that vmWare Workstation 7.1.4 solved this issue with 270.29. Haven't checked 270.26 though.

Bye.


All times are GMT -5. The time now is 11:11 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.