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

Newegg Daily Deals

Reply
 
Thread Tools
Old 03-26-10, 03:31 AM   #1
vslavik
Registered User
 
Join Date: Oct 2003
Posts: 16
Unhappy X hangs temporarily or completely with GT 220

Hi,

I upgraded from my trusty GeForce 7600 GS card to Zotac GT 220 (lust for full
VDPAU support was the main reason). Result: my previously perfectly
stable Linux system is now unusable.

Within minutes of starting X, it freezes. Either completely (I can't even ssh into the machine and have to reset it) or for couple of seconds, in which case it will happen again soon (eventually leading to full kernel freeze) _and_ content rendered via XRENDER becomes heavily corrupted (see attachment - it's cropped, because you don't allow large image attachments). Every time, a crash is logged in kernel log:
Code:
NVRM: Xid (0001:00): 8, Channel 00000003
and X log shows this
Code:
(WW) Mar 26 08:20:25 NVIDIA(0): WAIT (0, 6, 0x8000, 0x0000502c, 0x0000502c)
(WW) Mar 26 08:20:28 NVIDIA(0): WAIT (2, 6, 0x8000, 0x00005368, 0x0000db84)
(WW) Mar 26 08:20:31 NVIDIA(0): WAIT (0, 6, 0x8000, 0x0000db84, 0x0000db84)
This is with 195.36.15. I experienced same issues with 190.53, 190.42 and all previous 195.* releases, albeit with some differences in the behavior; I will describe these later for completeness. All of these driver versions work perfectly with 7600 GS (not even RENDER artifacts with 195.* drivers).

What I think may be relevant configuration bits:
  • xorg-server 1.7.x with evdev input and minimal xorg.conf
  • x86_64
  • kernel 2.6.31
  • using compiz as my WM, so OpenGL is used all the time


With older versions, it behaved somewhat differently: I got frequent X desktop freezes for couple of seconds, accompanied with this (and occasionally other Xid numbers, too, which I think might have been the ones I'm seeing now):
Code:
NVRM: Xid (0001:00): 13, 0001 00000000 0000502d 00000854 fdffffff 00000004
(Notice that it's different Xid from what I get now)

Usually, it survived <10 of them before locking the computer up
completely, at which point only X restart helped. Most of the time, mouse
cursor continued to work, but not always.

The backtrace in X log looked like this:
Code:
        0: /usr/bin/X (xorg_backtrace+0x31) [0x47d52d]
        1: /usr/bin/X (mieqEnqueue+0xce) [0x477e8e]
        2: /usr/bin/X (xf86PostMotionEventP+0x1f1) [0x493ee6]
        3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f197744f000+0x3781) [0x7f1977452781]
        4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f197744f000+0x39bf) [0x7f19774529bf]
        5: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f197744f000+0x3af6) [0x7f1977452af6]
        6: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f197744f000+0x3d06) [0x7f1977452d06]
        7: /usr/bin/X (0x400000+0x94fff) [0x494fff]
        8: /usr/bin/X (0x400000+0x1543a1) [0x5543a1]
        9: /lib/libpthread.so.0 (0x3e59400000+0xea40) [0x3e5940ea40]
        10: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f19a7cd4000+0x5dd6d) [0x7f19a7d31d6d]
        11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (_nv001018X+0x28b) [0x7f19a7d326eb]
        12: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f19a7cd4000+0xa5ae0) [0x7f19a7d79ae0]
        13: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (_nv001433X+0x92) [0x7f19a7d4e752]
        14: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f19a7cd4000+0x31ea88) [0x7f19a7ff2a88]
        15: /usr/bin/X (0x400000+0xec659) [0x4ec659]
        16: /usr/bin/X (0x400000+0xa9ff1) [0x4a9ff1]
        17: /usr/bin/X (BlockHandler+0x75) [0x46b9f6]
        18: /usr/bin/X (WaitForSomething+0x328) [0x482916]
        19: /usr/bin/X (0x400000+0x265bf) [0x4265bf]
        20: /usr/bin/X (0x400000+0x25f68) [0x425f68]
        21: /lib/libc.so.6 (__libc_start_main+0xfd) [0x3e5881ea3d]
        22: /usr/bin/X (0x400000+0x25959) [0x425959]
This seems to indicate evdev relation.

Hard freezes on the first occurrence started happening with 195.30.

RENDER got occasional corruptions with 190.53 with my old card too, but *occasional*, not within a minute of starting the desktop. And it's not happening with newer drivers anymore.

Playing with UseEvents didn't seem to affect things. But then, the
changelog says this setting is disabled for GeForce >= 8 since sometimes
after 190.42(?).

Thanks,
Vaclav
Attached Thumbnails
Click image for larger version

Name:	Screenshot.png
Views:	117
Size:	81.2 KB
ID:	39873  
Attached Files
File Type: gz nvidia-bug-report.log.gz (47.3 KB, 84 views)
File Type: gz nvidia-bug-report-old-195.30.log.gz (30.3 KB, 77 views)
vslavik is offline   Reply With Quote
Old 04-24-10, 12:54 AM   #2
vslavik
Registered User
 
Join Date: Oct 2003
Posts: 16
Default Re: X hangs temporarily or completely with GT 220

Ping? I reported this by email (as instructed by the README) long before I posted it here. I tried again through the forums, with no reaction from NVIDIA either time -- great support, that :-/
vslavik is offline   Reply With Quote
Old 04-24-10, 01:14 AM   #3
gradinaruvasile
Registered User
 
gradinaruvasile's Avatar
 
Join Date: May 2008
Posts: 199
Default Re: X hangs temporarily or completely with GT 220

Disable compiz, restart X or the computer and see if you still have issues.
Try removing/renaming your xorg.conf and $HOME/.nvidia-settings-rc files. Then reinstall the driver (make sure you let it configure xorg.conf).
gradinaruvasile is offline   Reply With Quote
Old 04-24-10, 01:59 AM   #4
vslavik
Registered User
 
Join Date: Oct 2003
Posts: 16
Default Re: X hangs temporarily or completely with GT 220

Quote:
Disable compiz, restart X or the computer and see if you still have issues.
Try removing/renaming your xorg.conf and $HOME/.nvidia-settings-rc files. Then reinstall the driver (make sure you let it configure xorg.conf).
This is, of course, unrelated to how the driver was installed and crippling the system by not using OpenGL is, of course, not an option (using older HW is a better workaround). Thanks, but I don't need advice on how to work around this.

What I would appreciate is if NVIDIA folks at least acknowledged this crashing and display corruption bug and provided some qualified suggestions on what settings may fix it (short of disabling RENDER, which, again, renders the desktop unusable). But well, two and a half months is probably too short time to expect any reaction (even though I'm not the only one reporting this)...
vslavik is offline   Reply With Quote
Old 04-24-10, 02:16 AM   #5
gradinaruvasile
Registered User
 
gradinaruvasile's Avatar
 
Join Date: May 2008
Posts: 199
Default Re: X hangs temporarily or completely with GT 220

Dude it is a test. To see if this is related to compiz... Also, i dont know what (if any) settings those 2 files might have that *may* interfere with the 220. I had issues with xorg component updates overwriting nvidia driver .so links killing glx extensions etc.
Whatever.
gradinaruvasile is offline   Reply With Quote
Old 04-25-10, 12:05 AM   #6
Dizzle7677
Registered User
 
Dizzle7677's Avatar
 
Join Date: May 2008
Location: Relativity
Posts: 194
Default Re: X hangs temporarily or completely with GT 220

You'll have to add the Xserver Xorg debug symbols to really see where it's hanging.

Check for video/motherboard bios updates also.
__________________
Elephants can fly but they have no reason to.
------------------------------------------
Phenom II X3 720 @ 3.5Ghz | Asus M4A785-M | 2 Gig Crucial DDR2 @ 960 Mhz | GeForce GT 440 1024 MB | Linux 3.6.1 / Ubuntu 12.04 / W.I.N.E v1.5.14
Dizzle7677 is offline   Reply With Quote
Old 05-05-10, 04:31 AM   #7
vslavik
Registered User
 
Join Date: Oct 2003
Posts: 16
Default Re: X hangs temporarily or completely with GT 220

Still there with 195.36.24. Compiz hang is so hard I don't even get log output anymore. Without OpenGL, it doesn't hang, but display corruption still happens, frequently. Switching to VT1 (Ctrl+Alt+F1) and back fixes it (temporarily), so it very much looks like some cache corruption. Disabling glyph and/or pixmap cache has no effect.

The vendor has no newer BIOS updates available. I can try to debug the server properly, but there doesn't seem any point in doing it if a programmer responsible for this code doesn't need/want to see this information.
vslavik is offline   Reply With Quote
Old 05-06-10, 12:36 AM   #8
vslavik
Registered User
 
Join Date: Oct 2003
Posts: 16
Default Re: X hangs temporarily or completely with GT 220

Apparently, this is a serious breakage in the PowerMizer default setting:

https://bugs.launchpad.net/ubuntu/+s...rs/+bug/532111
https://bugs.launchpad.net/ubuntu/+s...80/+bug/456637

The workaround mentioned in there (use nvidia-settings to set it to max performance) seems to work so far. Linking it from there for other unfortunate souls.
vslavik is offline   Reply With Quote

Old 05-06-10, 01:34 AM   #9
Dizzle7677
Registered User
 
Dizzle7677's Avatar
 
Join Date: May 2008
Location: Relativity
Posts: 194
Default Re: X hangs temporarily or completely with GT 220

Quote:
Originally Posted by vslavik View Post
Apparently, this is a serious breakage in the PowerMizer default setting:

https://bugs.launchpad.net/ubuntu/+s...rs/+bug/532111
https://bugs.launchpad.net/ubuntu/+s...80/+bug/456637

The workaround mentioned in there (use nvidia-settings to set it to max performance) seems to work so far. Linking it from there for other unfortunate souls.
Unchecking PowerMizer Monitor under nvidia-settings Configuration would also do the trick.
__________________
Elephants can fly but they have no reason to.
------------------------------------------
Phenom II X3 720 @ 3.5Ghz | Asus M4A785-M | 2 Gig Crucial DDR2 @ 960 Mhz | GeForce GT 440 1024 MB | Linux 3.6.1 / Ubuntu 12.04 / W.I.N.E v1.5.14
Dizzle7677 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 05:19 PM.


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