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.18 driver crash (Wine related?) (http://www.nvnews.net/vbulletin/showthread.php?t=159554)

cheechr1 02-10-11 11:17 PM

270.18 driver crash (Wine related?)
 
1 Attachment(s)
I recently tried running Dead Space 2 in wine, which did not go as well as I hoped. After the game crashed (numerous tries, numerous crashes of course) I began to notice strange desktop behavior, such as program launchers with icons but did not work. After rebooting everything worked normally, but now when I play Call of Duty Black Ops on wine I began to get crashes. Soon those crashes began happening at any time, usually when graphical applications are in use, such as Project M. Now the crashes are very often, a few times a day when just surfing but it gets much worse when I play games or graphical applications, every ~20 minutes or so. Please Help! I have tried re-installing drivers to no avail as well. There are strange errors in my Xlog that lead me to believe nvidia drivers are at fault:

[ 367.252] (II) Power Button: Close
[ 367.252] (II) UnloadModule: "evdev"
[ 367.280] (II) Power Button: Close
[ 367.280] (II) UnloadModule: "evdev"
[ 367.324] (II) Logitech USB Receiver: Close
[ 367.414] (II) UnloadModule: "evdev"
[ 367.448] (II) Logitech USB Receiver: Close
[ 367.448] (II) UnloadModule: "evdev"
[ 367.508] (II) PS/2 Synaptics TouchPad: Close
[ 367.508] (II) UnloadModule: "evdev"
[ 367.705] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 367.705] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 367.705] (WW) xf86OpenConsole: VT_GETSTATE failed: Input/output error
[ 367.705] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 367.705] (WW) xf86CloseConsole: VT_WAITACTIVE failed: Input/output error
[ 367.705] ddxSigGiveUp: Closing log

Licaon 02-11-11 01:10 AM

Re: 270.18 driver crash (Wine related?)
 
Quote:

*** /proc/mtrr
*** ls: -rw-r--r-- 1 root root 0 2011-02-10 21:42:19.288811993 -0700 /proc/mtrr
reg00: base=0x1c0000000 ( 7168MB), size= 1024MB, count=1: uncachable
reg01: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back
reg02: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
reg03: base=0x0bf800000 ( 3064MB), size= 8MB, count=1: uncachable
these can be fixed, read: http://www.nvnews.net/vbulletin/show...8&postcount=39

can you read again http://www.nvnews.net/vbulletin/showthread.php?t=46678 and generate a good report with the debug ( -logverbose 6 ) info as instructed after the issue appears ?

cheechr1 02-11-11 06:36 PM

Re: 270.18 driver crash (Wine related?)
 
Thank you Licaon, I did not notice the MTRR issue I had. I do not consider myself an expert in linux, but I have been using it for about 3 years. How do I do the -logverbose 6? Can I do it via grub? Just to be a little more precise, these hard locks started only a few days ago, when trying to run games using wine, which I thought was strange. It was even stranger when the hard locks began outside of graphical applications. Ive never had an issue with such little report in the Xlog. I an currently using enable_mtrr_cleanup via grub in ubuntu 10.10 and cat /proc/mtrr has changed to this now:

Quote:

reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
reg02: base=0x0bf800000 ( 3064MB), size= 8MB, count=1: uncachable
reg03: base=0x100000000 ( 4096MB), size= 2048MB, count=1: write-back
reg04: base=0x180000000 ( 6144MB), size= 1024MB, count=1: write-back
Is it normal to see uncachable memory addresses after using MTRR cleanup? I have tested just a little bit after and the computer seems stable, no more hard lock ups. Not ready to declare this issue fixed quite yet tho. Thanks again.

Edit: Ok i figured out the verbose option, will also try ssh, pointers for ssh would be nice tho never usid it before, will start googling for it soon.

cheechr1 02-11-11 11:51 PM

Re: 270.18 driver crash (Wine related?)
 
1 Attachment(s)
Ok I was able to ssh into the machine while crashed. Luckily when it crashed I had -logverbose 6 active as well. Crashed while playing Call of Duty Black Ops.

cheechr1 02-19-11 06:49 PM

Re: 270.18 driver crash (Wine related?)
 
Just tried the 270.26 driver, with the same results. Random crashes seem to only happen during CoD Black Ops after about 20 minutes of play. Please help me Nvidia team!

Licaon 02-19-11 07:35 PM

Re: 270.18 driver crash (Wine related?)
 
does this happen on native Linux games too?

say Nexuiz or Warsow or Regnum or Amnesia: The Dark Descent Demo ?

cheechr1 02-20-11 01:41 PM

Re: 270.18 driver crash (Wine related?)
 
I just tried playing almost an hour of Nexuiz without a crash, next I will try a few hours of a native installation of UT2004. I am beginning to think this is a CoD issue....

Edit: I decided to play a bit more Nexuiz, and experienced the freeze again...

OliW 02-20-11 07:07 PM

Re: 270.18 driver crash (Wine related?)
 
I also get freezes in COD:BO. Mine last a minute at most (X completely freezes, but still accessible via SSH) but it comes back to life after that.

Have you tried just waiting?

cheechr1 02-21-11 12:56 AM

Re: 270.18 driver crash (Wine related?)
 
I just tried waiting out a crash for almost ten minutes to no avail. The screen artifacted for a few frames here and there and audio still works but glitches out from time to time during the crashes. Had to reboot :(. It seems these crashes only happen during 3d applications. ProjectM has almost never caused a crash though and it is fairly 3d intensive. I will try to post a new bug report with the 270.26 driver.

Licaon 02-21-11 01:47 AM

Re: 270.18 driver crash (Wine related?)
 
Quote:

Originally Posted by cheechr1 (Post 2394678)
I will try to post a new bug report with the 270.26 driver.

with a native Linux app right?

cheechr1 02-21-11 02:10 AM

Re: 270.18 driver crash (Wine related?)
 
2 Attachment(s)
So I just started Ubuntu in logverbose 6 to generate a new bug report and decided to try my hand at nexuiz first. I experienced a crash which lasted about ten seconds, surprisingly. So then I decided to try CoD:BO and experienced short crashes about every 5-10 min. After about twenty minutes of play I decided to check the logs and found some interesting things so I generated a new report. Will keep playing CoD to see if it crashes hard and try to ssh in to generate another report.

Edit: Just played more nexuiz followed by some good old UT2004. UT2004 ran flawlessly but nexuiz showed short crashes. Then I tried CoD which also had short lockups followed by a hard lockup. I SSH'ed in and generated another report, but it appears corrupted.

Licaon 02-21-11 05:45 AM

Re: 270.18 driver crash (Wine related?)
 
You also are affected by http://www.nvnews.net/vbulletin/showthread.php?t=157499 :(

Stuff like:

Quote:

[ 1762.317478] NVRM: Xid (0000:02:00): 8, Channel 00000010
[ 2529.007594] NVRM: Xid (0000:02:00): 8, Channel 00000012
[ 2851.456658] NVRM: Xid (0000:02:00): 8, Channel 00000012
[ 7576.283494] NVRM: Xid (0000:02:00): 8, Channel 00000012
and

Quote:

[ 877.980] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00006b6c, 0x00007464)
[ 884.980] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00006b6c, 0x00007464)
[ 1759.041] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004250, 0x000060b8)
[ 1765.418] (WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x000060b8, 0x000060b8)
[ 2316.424] GetModeLine - scrn: 0 clock: 148350
[ 2316.424] GetModeLine - hdsp: 1920 hbeg: 2008 hend: 2052 httl: 2200
[ 2316.424] vdsp: 1080 vbeg: 1084 vend: 1089 vttl: 1125 flags: 5
[ 2329.369] (II) NVIDIA(0): Setting mode "1920x1080_60i_0"
[ 2528.289] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 2528.289]
Backtrace:
[ 2528.289] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef31b]
[ 2528.289] 1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80ecb5b]
[ 2528.289] 2: /usr/bin/X (xf86PostMotionEventP+0xd2) [0x80bd662]
[ 2528.289] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4e60000+0x4911) [0xb4e64911]
[ 2528.289] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4e60000+0x4a06) [0xb4e64a06]
[ 2528.289] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4e60000+0x5246) [0xb4e65246]
[ 2528.289] 6: /usr/bin/X (0x8048000+0x62e7f) [0x80aae7f]
[ 2528.289] 7: /usr/bin/X (0x8048000+0x121b4e) [0x8169b4e]
[ 2528.289] 8: (vdso) (__kernel_sigreturn+0x0) [0xb78a6400]


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

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