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

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-16-08, 01:28 PM   #37
zim2dive
Registered User
 
Join Date: Dec 2008
Posts: 145
Default Re: 180.* graphical corruption and freezes system

Quote:
Originally Posted by bendley View Post
Hi,
although giving me a performance boost for KDE4 , the new 180.* nvidia drivers are unusable to me.
After a random time my WHOLE screen becomes corrupted, the picture flickers and i can no longer use the system, cant even forcefully restart X , i have to kill the whole system by force.
This happend to me on a x86 and a amd64 installation on the same notebook.
with the 177.* drivers i doesnt happen to me and i can use my notebook for hours without any problems.
I can;t say for sure this is 180.16, but the only thing else I changed was alsa... anyway, while trying to enable HDMI audio, I installed the 180.16 beta to my Ubuntu 8.10 box and so far Firefox has gone in the toilet... if I try to quit, I get graphics corruption and seemingly a system hang (must reboot). Even w/o quitting FF, I tried to load cnn.com and got a hang (which made me think Flash).

I don't think I need 180.16 for my hdmi audio (looks like the issue was alsa), so I'm going back to 177, but thought I'd add in my experience.

my nvidia settings report was attached to the 1st post in http://www.nvnews.net/vbulletin/showthread.php?t=124742
zim2dive is offline   Reply With Quote
Old 12-16-08, 01:46 PM   #38
gary987
Registered User
 
Join Date: Jun 2008
Posts: 3
Default Re: 180.* graphical corruption and freezes system

okay.. 180.16...

Hmm what seemed like a hard lock could be remedied by reselecting a tty.

X: symbol lookup error: /usr/lib64/xorg/modules/extentsions//libglx.so: undefined symbol: _mv000002gl
gary987 is offline   Reply With Quote
Old 12-16-08, 02:01 PM   #39
mgs
Registered User
 
Join Date: Dec 2008
Posts: 3
Default Re: 180.* graphical corruption and freezes system

Experiencing the same problem. Can't really find a pattern in the triggering of the bug. Sometimes I can still see the mouse move under all the noise on the screen, at other times the system locks up completely. At times, the system respond to the power button (IE, one click and it shuts down), but most often I have to forcefully powercycle the system.

The bug report is attached, however there seem to be some small difference between this and what I can read from the kernel log. The following is taken from the kernel log:

Code:
Dec 16 20:05:52 Magnus kernel: [  433.796073] CE: hpet increasing min_delta_ns to 15000 nsec
Dec 16 20:06:09 Magnus kernel: [  450.681079] CE: hpet increasing min_delta_ns to 22500 nsec
Dec 16 20:07:40 Magnus kernel: [  541.629319] CE: hpet increasing min_delta_ns to 33750 nsec
Dec 16 20:10:03 Magnus kernel: [  684.657832] NVRM: Xid (0001:00): 6, PE0003
Dec 16 20:10:03 Magnus kernel: [  684.722241] NVRM: Xid (0001:00): 3, C 0000007e SC 00000001 M 00001f3c Data ffe1e1e0
Couldn't see the Xid messages in the attached report, but I might just have missed them. I don't know if the CE part is related at all, but I included it just in case.
Attached Files
File Type: gz nvidia-bug-report.log.gz (35.8 KB, 138 views)
mgs is offline   Reply With Quote
Old 12-16-08, 02:18 PM   #40
adamorjames
Registered User
 
adamorjames's Avatar
 
Join Date: Oct 2008
Posts: 39
Default Re: 180.* graphical corruption and freezes system

Yeah sometimes the cursor can still be moved and other times nothing can be done.

Arch Linux 32 bit
adamorjames is offline   Reply With Quote
Old 12-16-08, 02:50 PM   #41
mgs
Registered User
 
Join Date: Dec 2008
Posts: 3
Default Re: 180.* graphical corruption and freezes system

Just had another chrash which responded to the power button as well. I've attached yet another bug report, but once more there is a difference between the messages seen in the attached report and what is written in the kernel log.

Thus, at least on my system (Based on Ubuntu 8.10), there is a difference of what gets logged into /var/log/messages and /var/log/kern.log. Here are the 2 sections in question:

/var/log/messages
Code:
Dec 16 20:17:33 Magnus kernel: [  379.416005] CE: hpet increasing min_delta_ns to 15000 nsec
Dec 16 20:25:48 Magnus kernel: [  874.184092] CE: hpet increasing min_delta_ns to 22500 nsec
Dec 16 20:51:53 Magnus -- MARK --
Dec 16 21:11:53 Magnus -- MARK --
Dec 16 21:31:53 Magnus -- MARK --
Dec 16 21:39:37 Magnus kernel: [ 5302.952722] ACPI Exception (evregion-0419): AE_TIME, Returned by Handler for [EmbeddedControl] [20080609]
Dec 16 21:39:37 Magnus kernel: [ 5302.952756] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_._Q63] (Node ffff8$
Dec 16 21:39:44 Magnus kernel: [ 5307.698790] ip6_tables: (C) 2000-2006 Netfilter Core Team
/var/log/kern.log
Code:
Dec 16 20:17:33 Magnus kernel: [  379.416005] CE: hpet increasing min_delta_ns to 15000 nsec
Dec 16 20:25:48 Magnus kernel: [  874.184092] CE: hpet increasing min_delta_ns to 22500 nsec
Dec 16 21:39:17 Magnus kernel: [ 5283.337915] NVRM: Xid (0001:00): 62, CMDre 00000000 0000089c 0100cb18 00000004 00000084
Dec 16 21:39:27 Magnus kernel: [ 5293.361076] NVRM: Xid (0001:00): 62, CMDre 00000000 0000089c 0100cb18 00000004 00000084
Dec 16 21:39:27 Magnus kernel: [ 5293.362341] NVRM: Xid (0001:00): 62, CMDre 00000000 0000089c 0100cb18 00000004 00000084
Dec 16 21:39:27 Magnus kernel: [ 5293.363529] NVRM: Xid (0001:00): 62, CMDre 00000000 0000089c 0100cb18 00000004 00000084
Dec 16 21:39:37 Magnus kernel: [ 5302.952722] ACPI Exception (evregion-0419): AE_TIME, Returned by Handler for [EmbeddedControl] [20080609]
Dec 16 21:39:37 Magnus kernel: [ 5302.952756] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_._Q63] (Node ffff8$
Dec 16 21:39:44 Magnus kernel: [ 5307.698790] ip6_tables: (C) 2000-2006 Netfilter Core Team
Note how the NVRM: Xid messages do not appear.

At the time this lockup occured, I was scrolling in a firefox window and listening to music in Amarok 2. The music continued after the screen corruption. Running KDE 4.2 Beta 1 on a AMD64 system based on Ubuntu 8.10.
Attached Files
File Type: gz nvidia-bug-report.log.gz (35.8 KB, 146 views)

Last edited by mgs; 12-16-08 at 02:53 PM. Reason: Added what I was doing at the time of the bug
mgs is offline   Reply With Quote
Old 12-16-08, 04:53 PM   #42
xin44
Registered User
 
Join Date: Dec 2006
Posts: 72
Default Re: 180.* graphical corruption and freezes system

hi Plagman,

the "NVRM: Xid" comes with every white flashes - then the corruption appears.

* if the first flash comes when nothing is do for somes minutes :

- If i do not use my keyboard or the mouse after the first flash, things stays like that, no overheat,cpu 5-10%, little areas corrupted but no lock (tested 5 mn).

- if i click or type a key during this period, other flashes comes, more freq (2 per sec when fast) but randomly (ctrl+alt+bcksp is the issue)

* if the flash comes at a busy moment, 1 sec max to ctrl-alt-bcksp, but a single clik or key press locks definitively the display and the keyboard (power off only), the same after 1 sec delay.

sometimes, after 30 sec hang :

-all recover, but some minutes after, another hang comes (often not recoverable)
or
-"composite was too slow and has been desactivated" but all fine (except composite).

hope that helps !

NB:
* the corruption do not look like i have seen on these thread - ex: the konsole is fill (transparent background normally) with a part of the image that appears repeatedly when x starts (after the first logon, this image is a mosaic of a little part of the desktop).
* it's similar under compiz (perhaps a little more frequent).
xin44 is offline   Reply With Quote
Old 12-16-08, 09:48 PM   #43
walmartshopper
Registered User
 
Join Date: Dec 2008
Posts: 23
Default Re: 180.* graphical corruption and freezes system

I have already emailed my bug report to linux-bugs@nvidia.com, but I'll post it here also. I'm not using 180.*, but I have the same exact problem with all versions of the driver. As noted before, I was able to completely eliminate the problem by switching to a single channel memory configuration.

Another interesting thing that I forgot to mention is that I was running the exact same setup before with no problems. I had been running 177.80 with no problems for weeks, and then the problem started suddenly, even though I had done nothing to the nvidia driver. Once the problem started, I tried reverting back to the 173 and 169 series, and I continued to have the problem, even though those same drivers on the same setup had worked perfectly before (even with dual channel memory). I know it sounds like a hardware problem, but after all the testing I've done, I'm about 99% sure there's nothing wrong with the card.

So I'm starting to wonder if a recent Xorg or Compiz update broke something? Since the problem only occurs when running compositing and/or openGL, I'm suspecting that maybe Compiz is the culprit. Looking back at the slackware-current changelog, I think the problem started happening after the Compiz package was upgraded from 0.7.6 to 0.7.8 and several xf86 packages were upgraded. Here's the relevant section of the changelog from 11/19/08:

x/compiz-0.7.8-i486-1.tgz: Upgraded to compiz-0.7.8.
x/xf86-input-acecad-1.2.2-i486-1.tgz: Added xf86-input-acecad-1.2.2.
x/xf86-input-calcomp-1.1.2-i486-1.tgz:
Upgraded to xf86-input-calcomp-1.1.2-i486-1.tgz.
x/xf86-input-digitaledge-1.1.1-i486-1.tgz:
Upgraded to xf86-input-digitaledge-1.1.1.
x/xf86-input-dmc-1.1.2-i486-1.tgz: Added xf86-input-dmc-1.1.2.
x/xf86-input-dynapro-1.1.2-i486-1.tgz: Upgraded to xf86-input-dynapro-1.1.2.
x/xf86-input-elo2300-1.1.2-i486-1.tgz: Upgraded to xf86-input-elo2300-1.1.2.
x/xf86-input-elographics-1.2.3-i486-1.tgz:
Upgraded to xf86-input-elographics-1.2.3.
x/xf86-input-evdev-2.0.8-i486-1.tgz: Upgraded to xf86-input-evdev-2.0.8.
x/xf86-input-fpit-1.2.0-i486-1.tgz: Upgraded to xf86-input-fpit-1.2.0.
x/xf86-input-hyperpen-1.2.0-i486-1.tgz: Upgraded to xf86-input-hyperpen-1.2.0.
x/xf86-input-jamstudio-1.2.0-i486-1.tgz:
Upgraded to xf86-input-jamstudio-1.2.0.
x/xf86-input-joystick-1.3.3-i486-1.tgz: Upgraded to xf86-input-joystick-1.3.3.
x/xf86-input-keyboard-1.3.1-i486-1.tgz: Upgraded to xf86-input-keyboard-1.3.1.
x/xf86-input-magellan-1.2.0-i486-1.tgz: Upgraded to xf86-input-magellan-1.2.0.
x/xf86-input-microtouch-1.2.0-i486-1.tgz:
Upgraded to xf86-input-microtouch-1.2.0.
x/xf86-input-mutouch-1.2.1-i486-1.tgz: Upgraded to xf86-input-mutouch-1.2.1.
x/xf86-input-palmax-1.2.0-i486-1.tgz: Upgraded to xf86-input-palmax-1.2.0.
x/xf86-input-penmount-1.3.0-i486-1.tgz: Upgraded to xf86-input-penmount-1.3.0.
x/xf86-input-summa-1.2.0-i486-1.tgz: Upgraded to xf86-input-summa-1.2.0.
x/xf86-input-synaptics-0.15.2-i486-1.tgz: Added xf86-input-synaptics-0.15.2.
x/xf86-input-tek4957-1.2.0-i486-1.tgz: Upgraded to xf86-input-tek4957-1.2.0.
x/xf86-input-vmmouse-12.5.2-i486-1.tgz: Upgraded to xf86-input-vmmouse-12.5.2.
x/xf86-input-void-1.1.1-i486-1.tgz: Added xf86-input-void-1.1.1.
x/xf86-video-cirrus-1.2.1-i486-1.tgz: Upgraded to xf86-video-cirrus-1.2.1.
x/xf86-video-glint-1.2.1-i486-1.tgz: Upgraded to xf86-video-glint-1.2.1.
x/xf86-video-i128-1.3.1-i486-1.tgz: Upgraded to xf86-video-i128-1.3.1.
x/xf86-video-intel-2.4.3-i486-1.tgz: Upgraded to xf86-video-intel-2.4.3.
x/xf86-video-mga-1.4.9-i486-1.tgz: Upgraded to xf86-video-mga-1.4.9.
x/xf86-video-neomagic-1.2.1-i486-1.tgz: Upgraded to xf86-video-neomagic-1.2.1.
x/xf86-video-nv-2.1.12-i486-1.tgz: Upgraded to xf86-video-nv-2.1.12.
x/xf86-video-openchrome-0.2.903-i486-1.tgz:
Added xf86-video-openchrome-0.2.903.
x/xf86-video-radeonhd-1.2.3-i486-1.tgz: Upgraded to xf86-video-radeonhd-1.2.3.
x/xf86-video-s3virge-1.10.1-i486-1.tgz: Upgraded to xf86-video-s3virge-1.10.1.
x/xf86-video-savage-2.2.1-i486-1.tgz: Upgraded to xf86-video-savage-2.2.1.
x/xf86-video-vmware-10.16.5-i486-1.tgz: Upgraded to xf86-video-vmware-10.16.5.
Attached Files
File Type: gz nvidia-bug-report.log.gz (30.0 KB, 150 views)
walmartshopper is offline   Reply With Quote
Old 12-17-08, 06:17 AM   #44
kernelOfTruth
Gentoo Linux addict
 
Join Date: Nov 2007
Location: Vienna, Austria; Germany; hello world :)
Posts: 202
Default Re: 180.* graphical corruption and freezes system

anyone of you guys launches their kernel with

pci=nomsi ?

does that make a change ?
__________________
2.6.30-rc3-zen0+ w. compcache, reiser4 + ccreg40 (lzo-compression + checksumming)
gcc version 4.4.0-pre9999 built 20090425 (prerelease) rev. 146764 (Gentoo SVN)
gcc version 4.4.0 (Gentoo Hardened 4.4.0-r1, espf-0.2.1)
Ubuntu Jaunty/9.04 x86_64 Dell XPS M1330
kernelOfTruth is offline   Reply With Quote

Old 12-17-08, 02:52 PM   #45
walmartshopper
Registered User
 
Join Date: Dec 2008
Posts: 23
Default Re: 180.* graphical corruption and freezes system

Unfortunately, pci=nomsi didn't change anything for me.

I'm considering switching to Bluewhite64 (64bit Slackware) and trying out the 64bit nvidia driver, but I won't have time to do that until January. And who knows, there might be a solution before then anyway.

I'm going to try installing the older Compiz 0.7.4 and 0.7.6 packages from slackware 12.1 and see if that changes anything.
walmartshopper is offline   Reply With Quote
Old 12-17-08, 03:37 PM   #46
mgs
Registered User
 
Join Date: Dec 2008
Posts: 3
Default Re: 180.* graphical corruption and freezes system

I've tried the pci=nomsi option as well, which didn't change anything. Also, I wonder if this is a Compiz related error, as I get this running kwin under a 64 bit system. Think I'll revert to the 177 series for now.
mgs is offline   Reply With Quote
Old 12-17-08, 04:12 PM   #47
spectred
Registered User
 
Join Date: Jun 2008
Posts: 51
Default Re: 180.* graphical corruption and freezes system

Quote:
Originally Posted by walmartshopper View Post
Unfortunately, pci=nomsi didn't change anything for me.
...
Quote:
Originally Posted by mgs View Post
I've tried the pci=nomsi option as well, which didn't change anything...
same here
spectred is offline   Reply With Quote
Old 12-17-08, 05:36 PM   #48
rockman1981
Registered User
 
Join Date: Dec 2008
Posts: 34
Default Re: 180.* graphical corruption and freezes system

I have this issue too..
Trying setting GlyphCache at zero
nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=0 &

Seems more stable (and even faster!)
Will keep an eye on it
rockman1981 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 06:17 AM.


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