Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-25-11, 04:46 PM   #1
rnissl
Registered User
 
Join Date: Jun 2005
Posts: 36
Default 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D acceleration

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.
Attached Files
File Type: gz nvidia-bug-report.log.gz (77.2 KB, 69 views)
rnissl is offline   Reply With Quote
Old 02-25-11, 05:39 PM   #2
Licaon
Registered User
 
Licaon's Avatar
 
Join Date: Nov 2004
Location: Between the keyboard and the chair.
Posts: 490
Default 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
Licaon is offline   Reply With Quote
Old 02-26-11, 07:58 AM   #3
rnissl
Registered User
 
Join Date: Jun 2005
Posts: 36
Default Re: 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D accelera

Hi,

Quote:
Originally Posted by Licaon View Post
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 View Post
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 is offline   Reply With Quote
Old 03-29-11, 03:44 PM   #4
rnissl
Registered User
 
Join Date: Jun 2005
Posts: 36
Default 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 is offline   Reply With Quote
Old 04-03-11, 02:41 AM   #5
rnissl
Registered User
 
Join Date: Jun 2005
Posts: 36
Default 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.
rnissl is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


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


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