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

Newegg Daily Deals

Reply
 
Thread Tools
Old 10-07-08, 05:40 PM   #1
dionua
Registered User
 
Join Date: Aug 2006
Posts: 35
Default 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Just tried this "release". Same X blocking just after resuming from hibernate as reported a few times.

Code:
[284594.200091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[284594.200150] Xorg          D f4d1f810     0 26968  26966
[284594.200266]        c2010c80 00003082 00000000 f4d1f810 0000154b 00000000 c019b021 f7840030
[284594.200580]        d2b7c015 c04df080 d2f0c000 f4d1f98c 00000000 00005c54 c2010c80 be2d4c34
[284594.200927]        000102af f9dc2b12 cb6f4800 f9ecac9c f7e83008 c8d62c80 f4d1f98c ca201000
[284594.201317] Call Trace:
[284594.201407]  [<c019b021>] do_lookup+0xa1/0xd0
[284594.201493]  [<f9dc2b12>] _nv008580rm+0x52/0x9c [nvidia]
[284594.201789]  [<f9ecac9c>] _nv004539rm+0x24/0x70 [nvidia]
[284594.202067]  [<f9ecacc8>] _nv004539rm+0x50/0x70 [nvidia]
[284594.202346]  [<f9ecac9c>] _nv004539rm+0x24/0x70 [nvidia]
[284594.202622]  [<c03984ad>] schedule_timeout+0xbd/0xf0
[284594.202707]  [<f9ecad4d>] _nv004537rm+0x28/0x43 [nvidia]
[284594.202983]  [<f9ecad5b>] _nv004537rm+0x36/0x43 [nvidia]
[284594.203260]  [<c039794c>] wait_for_common+0x8c/0x130
[284594.203343]  [<c0122450>] default_wake_function+0x0/0x10
[284594.203427]  [<f9f8a987>] os_acquire_sema+0x77/0x80 [nvidia]
[284594.203706]  [<f9edc3a0>] _nv004221rm+0x9/0xd [nvidia]
[284594.203987]  [<f9ee5d13>] rm_check_pci_config_space+0x1a8/0x80e [nvidia]
[284594.204292]  [<f9f867a6>] nv_kern_ioctl+0x96/0x380 [nvidia]
[284594.204565]  [<c0104648>] irq_entries_start+0x664/0x840
[284594.204647]  [<f9f86ac8>] nv_kern_unlocked_ioctl+0x18/0x20 [nvidia]
[284594.204911]  [<f9f86ab0>] nv_kern_unlocked_ioctl+0x0/0x20 [nvidia]
[284594.205180]  [<c019feeb>] vfs_ioctl+0x2b/0x90
[284594.205262]  [<c012d3b4>] __do_softirq+0xe4/0xf0
[284594.205341]  [<c01a00c7>] do_vfs_ioctl+0x67/0x200
[284594.205420]  [<c01a02c6>] sys_ioctl+0x66/0x70
[284594.205502]  [<c0103e29>] sysenter_do_call+0x12/0x21
[284594.205584]  [<c0104648>] irq_entries_start+0x664/0x840
[284594.205664]  =======================
I've already reported this a few times for different driver releases. And yes, this is really regression, since all 173.xx versions works well here (including 173.14.12).

Still same performance regression in KDE4 Konsole. It just _very_ slow during scrolling. I've read all performance tricks and tried adding required options to xorg.conf as well as IPP an GlyphCache. This is NOT about powermizer since power suply is plugged and nvidia-settings reports maximum level of "performance".

IPP=2 is very slow. IPP=1 is a bit better but still unusable. IPP=0 is better than IPP=1 but opensource 2D-only NV is better. Even nouveau is better than nvidia.

History/changelog:
http://www.nvnews.net/vbulletin/showthread.php?t=118156
http://www.nvnews.net/vbulletin/showthread.php?t=118157
http://www.nvnews.net/vbulletin/showthread.php?t=118686

Differnt kernels, different nvidia versions but same issues. I've stopped reporting these issues since 177.70 since it looks like reports are useless and nobody cares about this.

Anyway I think that this was my last nvidia-based laptop.

PS: Can anybody with working TuxOnIce with nvidia >= 177.67 bump here?
Attached Files
File Type: log nvidia-bug-report.log (127.6 KB, 194 views)
dionua is offline   Reply With Quote
Old 10-27-08, 10:24 AM   #2
csbac
Registered User
 
Join Date: Oct 2008
Posts: 14
Angry Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Hi!
I have the same problem - no way to resume after hibernate w/o crashing X.
Does not work with any of the 177.xx drivers, including 177.80.
Works without any problems with 173.14.12 and 173.14.05.

OpenSUSE 11.0 x86_64; PhenomX4; 4GB RAM
ASUS M3N H/HDMI w/ GeForce 8300 on board

It's opensuse, so, I'm not sure what version of software suspend2 or tuxonice they base their stuff on.

a) Switch to a console, hibernate the system, resume; system runs OK.
switch back to X screen - TFT goes into sleep mode, no graphics signal until next POST.
b) Terminate X, hibernate the system, resume; system runs OK.
Start X, crashes as above.

On the other side:
c) Terminate X, hibernate the system, resume; system runs OK.
unload nvidia kernel module, then reload.
Start X, works flawlessly.
(doesn't matter wheter modules is unloaded before or after hibernate)

My guess - the drivers expects some information to be stored in graphics memory and does not notice the "reset" ...

dmesg/SysRQ-T after crash:

X D ffff81003789a1d0 0 4938 4295
ffff8101248c5c68 0000000000000086 0000000000000000 ffffffff887b330c
0000000049016dc1 ffffffff807e6280 ffffffff807e6280 ffff810108d062c0
ffff810127b64340 ffff810108d06600 0000000300000001 ffff810108d06600
Call Trace:
[<ffffffff80448020>] schedule_timeout+0x22/0xb4
[<ffffffff80447ecd>] wait_for_common+0x108/0x180
[<ffffffff80447fcf>] wait_for_completion+0x18/0x1a
[<ffffffff88475b81>] :nvidias_acquire_sema+0x3f/0x65
[<ffffffff887c58ab>] :nvidia:_nv004221rm+0x9/0xe
DWARF2 unwinder stuck at _nv004221rm+0x9/0xe [nvidia]

Leftover inexact backtrace:

[<ffffffff88750a3d>] ? :nvidia:_nv005488rm+0x59/0xa9
[<ffffffff885e9a55>] ? :nvidia:_nv003064rm+0x1b5/0x6fd
[<ffffffff887cd5e7>] ? :nvidia:rm_ioctl+0x2f/0x67
[<ffffffff884724b8>] ? :nvidia:nv_kern_ioctl+0x2ba/0x31f
[<ffffffff8020a71f>] ? __switch_to+0xf2/0x34b
[<ffffffff88472559>] ? :nvidia:nv_kern_unlocked_ioctl+0x1c/0x20
[<ffffffff802ac956>] ? vfs_ioctl+0x2a/0x78
[<ffffffff802acbeb>] ? do_vfs_ioctl+0x247/0x261
[<ffffffff802acc5a>] ? sys_ioctl+0x55/0x77
[<ffffffff8020bffa>] ? system_call_after_swapgs+0x8a/0x8f

final messages of Xorg-log:
...
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): kernel module enabled successfully
(II) NVIDIA(0): GPU initialized
(II) NVIDIA(0): Created acpid client socket 15.
(II) NVIDIA(0): Interrupts enabled

The lines which usually follow yet don't come are
(II) NVIDIA(0): Setting mode "1400x1050"
(II) NVIDIA(0): First mode initialized
(II) NVIDIA(0): Using built-in logo image.
(II) NVIDIA(0): Logo is 744x537 with depth 24.

I will attach nvidia-bug-report.log tomorrow.

Yours,
Sebastian

PS: dionua, I still have a lot of performance problems with the new drivers, same as you.
OpenSource nvidia does not support GeForce 8300, so, I'm using VESA driver for working and a second X server for 3D Gaming ;-)
csbac is offline   Reply With Quote
Old 10-27-08, 03:15 PM   #3
csbac
Registered User
 
Join Date: Oct 2008
Posts: 14
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Attaching nvidia-bug-report.log to the above post.
Unfortunately, when running nvidia-bug-report.sh, one of the first commands,
cat /proc/drivers/nvidia/cards/0
just hung. Obviously, the driver is not in a fit state to answer the query ;-(

So, I ran the bug reporter after a reboot - the Xorg.0.log evaluated is (should be?) the one that hung. Dmesg, on the other hand, is the one after the reboot. Thus, I also attach part of the /var/log/messages from the hang situation.
This also includes a SysRQ-T stack trace dump ... the following is nvidia-related:

Code:
Oct 27 20:46:45 aluro kernel: X             D ffff810125eefbd0     0  3556   3492
Oct 27 20:46:45 aluro kernel:  ffff8101234a5c68 0000000000000086 ffff8101234a5bb8 0000000000000092
Oct 27 20:46:45 aluro kernel:  ffff8101234a5c08 ffffffff807e6280 ffffffff807e6280 ffff8101264025c0
Oct 27 20:46:45 aluro kernel:  ffff81012702a540 ffff810126402900 0000000100000001 ffff810126402900
Oct 27 20:46:45 aluro kernel: Call Trace:
Oct 27 20:46:45 aluro kernel:  [<ffffffff80448020>] schedule_timeout+0x22/0xb4
Oct 27 20:46:45 aluro kernel:  [<ffffffff80447ecd>] wait_for_common+0x108/0x180
Oct 27 20:46:45 aluro kernel:  [<ffffffff80447fcf>] wait_for_completion+0x18/0x1a
Oct 27 20:46:45 aluro kernel:  [<ffffffff88482b81>] :nvidia:os_acquire_sema+0x3f/0x65
Oct 27 20:46:45 aluro kernel:  [<ffffffff887d28ab>] :nvidia:_nv004221rm+0x9/0xe
Oct 27 20:46:45 aluro kernel: DWARF2 unwinder stuck at _nv004221rm+0x9/0xe [nvidia]
Oct 27 20:46:45 aluro kernel: 
Oct 27 20:46:45 aluro kernel: Leftover inexact backtrace:
Oct 27 20:46:45 aluro kernel: 
Oct 27 20:46:45 aluro kernel:  [<ffffffff8875da3d>] ? :nvidia:_nv005488rm+0x59/0xa9
Oct 27 20:46:45 aluro kernel:  [<ffffffff885f6a55>] ? :nvidia:_nv003064rm+0x1b5/0x6fd
Oct 27 20:46:45 aluro kernel:  [<ffffffff887da5e7>] ? :nvidia:rm_ioctl+0x2f/0x67
Oct 27 20:46:45 aluro kernel:  [<ffffffff8847f4b8>] ? :nvidia:nv_kern_ioctl+0x2ba/0x31f
Oct 27 20:46:45 aluro kernel:  [<ffffffff8022b2b2>] ? hrtick_start_fair+0x156/0x163
Oct 27 20:46:45 aluro kernel:  [<ffffffff8847f559>] ? :nvidia:nv_kern_unlocked_ioctl+0x1c/0x20
Oct 27 20:46:45 aluro kernel:  [<ffffffff802ac956>] ? vfs_ioctl+0x2a/0x78
Oct 27 20:46:45 aluro kernel:  [<ffffffff802acbeb>] ? do_vfs_ioctl+0x247/0x261
Oct 27 20:46:45 aluro kernel:  [<ffffffff802acc5a>] ? sys_ioctl+0x55/0x77
Oct 27 20:46:45 aluro kernel:  [<ffffffff8020bffa>] ? system_call_after_swapgs+0x8a/0x8f


Oct 27 20:46:46 aluro kernel: nvidia-bug-re S 0000000000000001     0  4031   3585
Oct 27 20:46:46 aluro kernel:  ffff81012702de28 0000000000000086 0000000000000000 ffffffff802480d3
Oct 27 20:46:46 aluro kernel:  0000000000000fcb ffffffff807e6280 ffffffff807e6280 ffff8101249ec380
Oct 27 20:46:46 aluro kernel:  ffff810127b2c280 ffff8101249ec6c0 0000000200000001 ffff8101249ec6c0
Oct 27 20:46:46 aluro kernel: Call Trace:
Oct 27 20:46:46 aluro kernel:  [<ffffffff8023ab67>] do_wait+0xae7/0xbaa
Oct 27 20:46:46 aluro kernel:  [<ffffffff8023acc0>] sys_wait4+0x96/0xb1
Oct 27 20:46:46 aluro kernel:  [<ffffffff8020bffa>] system_call_after_swapgs+0x8a/0x8f
Oct 27 20:46:46 aluro kernel:  [<00007f8013495b55>]
Oct 27 20:46:46 aluro kernel: 
Oct 27 20:46:46 aluro kernel: cat           D ffff810125eefbd0     0  4043   4031
Oct 27 20:46:46 aluro kernel:  ffff810123c97c18 0000000000000086 0000000000000000 00000000000412d0
Oct 27 20:46:46 aluro kernel:  ffff810123c97c38 ffffffff807e6280 ffffffff807e6280 ffff8101249704c0
Oct 27 20:46:46 aluro kernel:  ffff810127b64340 ffff810124970800 0000000300000000 ffff810124970800
Oct 27 20:46:46 aluro kernel: Call Trace:
Oct 27 20:46:46 aluro kernel:  [<ffffffff80448020>] schedule_timeout+0x22/0xb4
Oct 27 20:46:46 aluro kernel:  [<ffffffff80447ecd>] wait_for_common+0x108/0x180
Oct 27 20:46:46 aluro kernel:  [<ffffffff80447fcf>] wait_for_completion+0x18/0x1a
Oct 27 20:46:46 aluro kernel:  [<ffffffff88482b81>] :nvidia:os_acquire_sema+0x3f/0x65
Oct 27 20:46:46 aluro kernel:  [<ffffffff887d28ab>] :nvidia:_nv004221rm+0x9/0xe
Oct 27 20:46:46 aluro kernel: DWARF2 unwinder stuck at _nv004221rm+0x9/0xe [nvidia]
Oct 27 20:46:46 aluro kernel: 
Oct 27 20:46:46 aluro kernel: Leftover inexact backtrace:
Oct 27 20:46:46 aluro kernel: 
Oct 27 20:46:46 aluro kernel:  [<ffffffff887dbb4f>] ? :nvidia:rm_get_device_name+0x11f/0x1ad
Oct 27 20:46:46 aluro kernel:  [<ffffffff884810ba>] ? :nvidia:nv_kern_read_cardinfo+0x7a/0x2b0
Oct 27 20:46:46 aluro kernel:  [<ffffffff802dec3b>] ? proc_reg_open+0x65/0x71
Oct 27 20:46:46 aluro kernel:  [<ffffffff802e2d5d>] ? proc_file_read+0xf6/0x23e
Oct 27 20:46:46 aluro kernel:  [<ffffffff802dee5b>] ? proc_reg_read+0x7e/0x98
Oct 27 20:46:46 aluro kernel:  [<ffffffff802a0dc1>] ? vfs_read+0xab/0x154
Oct 27 20:46:46 aluro kernel:  [<ffffffff802a0f2e>] ? sys_read+0x47/0x70
Oct 27 20:46:46 aluro kernel:  [<ffffffff8020bffa>] ? system_call_after_swapgs+0x8a/0x8f
By the way
Video BIOS: 62.77.1e.00.05
(this is shown as ??....?? in the bug report)

The kernel version is 2.6.25.16-0.1-sbr b/c I had to compile one of my own with some USB/HID/OHCI debug flags set (raised USB debug level is visible in dmesg and messages.txt). Apart from this, it uses exactly the same kernel config as the current opensuse 11.0 kernel.
Also, the bug was produced first with the current distribution/update kernel.
(for further reasons about the OHCI/USB/HID compile, please see https://bugzilla.novell.com/show_bug.cgi?id=419250)

Yours,
Hopefully,
Sebastian
Attached Files
File Type: gz nvidia-bug-report-afterReboot-2.log.gz (42.4 KB, 111 views)
File Type: gz messages.txt.gz (19.5 KB, 109 views)

Last edited by csbac; 10-27-08 at 03:17 PM. Reason: code formatting, unclear formulations
csbac is offline   Reply With Quote
Old 10-27-08, 05:58 PM   #4
kcrudup
Registered User
 
Join Date: Apr 2004
Location: Los Angeles, CA 90034
Posts: 96
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

I've been plagued with this since around 176.67 or thereabouts, too. (I have an 8600 GS.)

I've attached a nvidia-bug-report, as well as the compressed relevant parts of the syslog with the SysRq-T and SysRq-W output before I had to shut it down.
Attached Files
File Type: gz nvidia-bug-report.log.gz (31.8 KB, 115 views)
File Type: gz nvidia-toi-crash.gz (2.3 KB, 112 views)
__________________
8600M GS 512MB (HP Pavilion dv9000 CTO)
kcrudup is offline   Reply With Quote
Old 11-17-08, 06:01 AM   #5
csbac
Registered User
 
Join Date: Oct 2008
Posts: 14
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Seems to be fixed in 177.82 ... I'm not sure, b/c I changed the graphics card to a GeForce 6600 at the same time as the driver.
(Switch of graphics card necessary due to "GeForce 8300: up to 5 secs hang on focus change with firefox and video"
Sebastian
__________________
ASUS M3N-H/HDMI GeForce 8300 PhenomX4 9750 4GB opensuse 11.1/x86_64
Using GeForce 6600 b/c 8300/Linux as good as unsupported by nvidia.
csbac is offline   Reply With Quote
Old 11-17-08, 06:08 AM   #6
kcrudup
Registered User
 
Join Date: Apr 2004
Location: Los Angeles, CA 90034
Posts: 96
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Quote:
Originally Posted by csbac View Post
Seems to be fixed in 177.82
Not for me, it isn't. Kernel 2.6.27.6, 8600M GS, X86_64, 4GB RAM (which is why I care; without ToI's compression support resumes take forever).

It won't make one bit of difference, but I've futively attached a bug report (I'm running the non-ToI suspend/resume now, of course).
Attached Files
File Type: gz nvidia-bug-report.log.gz (34.6 KB, 103 views)
__________________
8600M GS 512MB (HP Pavilion dv9000 CTO)
kcrudup is offline   Reply With Quote
Old 11-17-08, 06:23 AM   #7
dionua
Registered User
 
Join Date: Aug 2006
Posts: 35
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

2nvidia: Any news about this issue? Will it be fixed in future.. It looks like a lot of users are affected. And this is _very_ important for laptop users with integrated NVIDIA GPU. All 177.xx versions are affected.
dionua is offline   Reply With Quote
Old 11-17-08, 06:33 AM   #8
csbac
Registered User
 
Join Date: Oct 2008
Posts: 14
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

So, it's a shared mem problem ... great, b/c mobile cards hibernate /a bit/ more often than PC ones ...
My 6600 has memory of its own, while the 8300 was a mGPU with shared memory. Not a mobile one, though.

Ah, kcrudup, I just noticed ... you first reported with an 8600 GS, but you have an 8600M GS, so shared memory there, also.
Taking myself out of this thread until nvidia creates a working 8300 Linux driver ...
Sebastian
__________________
ASUS M3N-H/HDMI GeForce 8300 PhenomX4 9750 4GB opensuse 11.1/x86_64
Using GeForce 6600 b/c 8300/Linux as good as unsupported by nvidia.
csbac is offline   Reply With Quote

Old 11-17-08, 10:42 AM   #9
dionua
Registered User
 
Join Date: Aug 2006
Posts: 35
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

My one is GeForce Go 7400 (just integrated laptop one)
dionua is offline   Reply With Quote
Old 11-17-08, 01:22 PM   #10
kcrudup
Registered User
 
Join Date: Apr 2004
Location: Los Angeles, CA 90034
Posts: 96
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Quote:
Originally Posted by csbac View Post
Ah, kcrudup, I just noticed ... you first reported with an 8600 GS, but you have an 8600M GS
That was a reporting error, sorry- (but it's in a laptop so I haven't actually changed the card).
__________________
8600M GS 512MB (HP Pavilion dv9000 CTO)
kcrudup is offline   Reply With Quote
Old 07-06-09, 02:29 AM   #11
csbac
Registered User
 
Join Date: Oct 2008
Posts: 14
Default Re: 177.80: [Regression] ToI hibernate troubles with GeForce Go 7400

Hi!
Seems the hibernation problem is fixed in the 185 series.
185.18.14 on GeForce 8300 mGPU on opensuse 11.1 x64

Yours,
Sebastian
__________________
ASUS M3N-H/HDMI GeForce 8300 PhenomX4 9750 4GB opensuse 11.1/x86_64
Using GeForce 6600 b/c 8300/Linux as good as unsupported by nvidia.
csbac 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


Similar Threads
Thread Thread Starter Forum Replies Last Post
What You Can Expect From GeForce GRID News Archived News Items 0 06-04-12 04:20 PM
Nvidia GeForce 301.42 WHQL drivers DSC NVIDIA Windows Graphics Drivers 5 05-29-12 10:12 PM
Enhance Max Payne 3, Diablo III with GeForce R300 Drivers News Archived News Items 0 05-22-12 06:30 PM
New GPU from Nvidia Announced Today, the GeForce GTX 670 News Archived News Items 0 05-10-12 01:50 PM
Gainward Unleashes the Sexy GeForce GTX 670 Phantom Graphics Card, Also launches the News Archived News Items 0 05-10-12 09:28 AM

All times are GMT -5. The time now is 08:51 AM.


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