nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA FreeBSD (http://www.nvnews.net/vbulletin/forumdisplay.php?f=47)
-   -   For "known issues": Too much memory (http://www.nvnews.net/vbulletin/showthread.php?t=129203)

BearPerson 02-28-09 03:02 PM

For "known issues": Too much memory
 
Hi folks,

I had this issue chew up my saturday, managed to fix it though.
Posting it here hoping that it may be useful:

Hardware: nvidia 9600 GT, on an Intel DP43TF, 4GB RAM installed
Software: x86 FreeBSD 7.1-RELEASE, X.Org 1.5.3, nvidia driver 180.29

Issue: system locks up when starting X.

Specifically, the following message is printed twice during X startup:
Code:

NVIDIA: failed to set MTRR 0xc0000000, 0M (write-combining)
Also, startup is excessively slow, with at least a minute pause after monitor EDID is read.
When the screen is finally initialized, (as seen by an X log message about the logo getting loaded),
syslog reports
Code:

kernel: NVRM: Xid (0001:00): 6, PE0001
and the system locks up shortly afterwards.

Solution:
I suspect this is due to address space issues.
It occurs when my (32-bit, non-PAE) system is booted with 4GB of memory installed,
and vanishes when I boot with 2GB of memory.

Interestingly, this issue is NOT fixed if I boot with hw.physmem=2GB,
and 4GB installed in the machine. The issue must probably be
with memory maps the kernel gets from the BIOS, I guess.

This issue is strange and frustrating enough that it could probably be added as "known issue",
or if it is easily reproducable and not too hard to detect in the driver,
a better warning message (or even making it an actual error) may be helpful.

Keep up the good work, folks!

ZOleg 03-02-09 06:04 PM

Re: For "known issues": Too much memory
 
BearPerson see here - http://www.nvnews.net/vbulletin/show...95&postcount=4

zander 03-06-09 05:33 PM

Re: For "known issues": Too much memory
 
I apologize for not commenting on this workaround earlier. I did see several reports of this problem, as well as the suggested workaround, and know that one of our SWQA engineers was able to confirm it helps on one of his systems. However, I have not had a chance to determine what the problem is, exactly, and don't feel comfortable documenting the workaround speculatively. We have a bug tracking this issue internally, however, and hope to get to the bottom of it, eventually.


All times are GMT -5. The time now is 12:06 PM.

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