nVidia driver + hibernate = no go?

[shaidtan]

Here are my config files. Hope they help.

[Kirurgs]

I'll try TuxOnIce...
Now I'm using standard swsusp that comes with F8.

[Kirurgs]

I tried to update BIOS, hibernate (s2disk) still doesn't work. Suspend (s2ram) seem to stabilize, it doesn't hang up after resume - it did this with WinXP too (I'll update this after some time if BIOS update didn't fix this completely).

Well, still, I would like to hear smth from nVidia people, some feedback or so...

P.S. I'll still update post after my further findings... Even small ones to bump this up, coz I still hope nVidia staff will post some news...

[NvFuchs]

On a Thinkpad R61, which is +/- the same hardware
in a different shell, I had to modifiy the extra_pages_allowance
in TOI.

Please read

http://www.thinkwiki.org/wiki/Instal...ad_R61#Suspend

hth,

Fuchs

[Kirurgs]

Hey, I can't believe the thing! I got hibernate working with the new beta 173.08 driver!!!
This is the first time ever I got successful wakeup from hibernate on my T61 with nVidia driver, but please remember, this happened just once!
I'll report on stability of the thing, but for those interested, this is my config:
[xx@xx ~]$ X -version

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora 8 Red Hat, Inc.
Current Operating System: Linux xx@xx 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:15:49 EDT 2008 x86_64
Build Date: 14 March 2008
Build ID: xorg-x11-server 1.3.0.0-44.fc8
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
[xx@xx ~]$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module 173.08 Wed Apr 2 07:55:48 PST 2008
GCC version: gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)

[Kirurgs]

Ok, I have done some tests and it seems that wakeup from hibernate works. It might be slower (2.5 mins wakeup with 2Gb RAM (used: max 300Mb)) than vesa, but it works with standart swsusp for F8.

To me 173.08 seems to be best driver released so far, I've enabled GylphCache too and it feels a little faster...

Good work, really...

[Kirurgs]

As I promised, some feedback

So the latest news: s2ram (suspend) works (with exception - below), s2disk (hibernate) works (with errors in syslog - below). Everything with 173.08, 2.6.24 kernel, standard swsusp2 for F8, no compiz or other composite w/ managers.
With 173.08 and GylphCache it's faster (really noticeable) with AA fonts, subpixel rendering and so on, no crashes, except wakeup from suspend when certain Wine windows are active.

So when having Oracle Forms6 Designer/Developer open while suspending, upon resume X dies and starts fresh gdm on next available tty. As far as I tested, only mentioned apps are causing trouble. Message in X log is:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x47fe0d]
1: /lib64/libc.so.6 [0x3101e30f30]
2: /usr/lib64/xorg/modules/drivers//nvidia_drv.so [0x2aaaac6d31f8]

Fatal server error:
Caught signal 11.  Server aborting

This seem to happen with latest stable driver and latest beta.

Also, wakeup from hibernate gives strange messages in syslog but it's resuming and working fine afterward. This is logged like 5 times or so.

May  2 22:01:23 test kernel: BUG: soft lockup - CPU#1 stuck for 11s! [pm-hibernate:3114]
May  2 22:01:23 test kernel: CPU 1:
May  2 22:01:23 test kernel: Modules linked in: << bunch of module names >>
May  2 22:01:23 test kernel: Pid: 3114, comm: pm-hibernate Tainted: P        2.6.24.5-85.fc8 #1
May  2 22:01:23 test kernel: RIP: 0010:[<ffffffff886fe914>]  [<ffffffff886fe914>] :nvidia:os_io_read_byte+0x4/0x8
May  2 22:01:23 test kernel: RSP: 0018:ffff81005c083c50  EFLAGS: 00000292
May  2 22:01:23 test kernel: RAX: 000000000000005c RBX: ffff810031ecef38 RCX: ffffffff88ab4640
May  2 22:01:23 test kernel: RDX: 00000000000003d5 RSI: 00000000000003d5 RDI: ffff810075030000
May  2 22:01:23 test kernel: RBP: ffff8100000c655d R08: 0000000000000000 R09: 0000000000000001
May  2 22:01:23 test kernel: R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
May  2 22:01:23 test kernel: R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000000
May  2 22:01:23 test kernel: FS:  00002aaaaaac7f50(0000) GS:ffff81007e801680(0000) knlGS:0000000000000000
May  2 22:01:23 test kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May  2 22:01:23 test kernel: CR2: 0000000000000000 CR3: 000000005c151000 CR4: 00000000000006a0
May  2 22:01:23 test kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May  2 22:01:23 test kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May  2 22:01:23 test kernel: 
May  2 22:01:23 test kernel: Call Trace:
May  2 22:01:23 test kernel:  [<ffffffff886dbd83>] :nvidia:_nv000016rm+0x13/0x1b
May  2 22:01:23 test kernel:  [<ffffffff88635c59>] :nvidia:_nv000217rm+0x11/0x26
May  2 22:01:23 test kernel:  [<ffffffff8841f5b6>] :nvidia:_nv000310rm+0x83/0xa4
May  2 22:01:23 test kernel:  [<ffffffff886dc3ad>] :nvidia:_nv004713rm+0x1b1/0x1f4
May  2 22:01:23 test kernel:  [<ffffffff8863b45f>] :nvidia:_nv004040rm+0xc7/0x365
May  2 22:01:23 test kernel:  [<ffffffff8863fab4>] :nvidia:_nv002971rm+0x2fd/0x568
May  2 22:01:23 test kernel:  [<ffffffff8863fa70>] :nvidia:_nv002971rm+0x2b9/0x568
May  2 22:01:23 test kernel:  [<ffffffff88640336>] :nvidia:_nv003109rm+0x46d/0x6fe
May  2 22:01:23 test kernel:  [<ffffffff8863cf34>] :nvidia:_nv002966rm+0x71/0x79
May  2 22:01:23 test kernel:  [<ffffffff8863d16a>] :nvidia:_nv002978rm+0x22e/0x24a
May  2 22:01:23 test kernel:  [<ffffffff8864204d>] :nvidia:rm_power_management+0x1cd/0x269
May  2 22:01:23 test kernel:  [<ffffffff886fc113>] :nvidia:nv_power_management+0x138/0x19f
May  2 22:01:23 test kernel:  [<ffffffff811a2910>] dpm_resume+0xc9/0x167
May  2 22:01:23 test kernel:  [<ffffffff811a29d9>] device_resume+0x2b/0x38
May  2 22:01:23 test kernel:  [<ffffffff8105a8fd>] hibernation_snapshot+0xd4/0xe0
May  2 22:01:23 test kernel:  [<ffffffff8105aab0>] hibernate+0xe3/0x1b7
May  2 22:01:23 test kernel:  [<ffffffff810595b2>] state_store+0x4c/0xb5
May  2 22:01:23 test kernel:  [<ffffffff810e2982>] sysfs_write_file+0xd2/0x110
May  2 22:01:23 test kernel:  [<ffffffff810a0cf7>] vfs_write+0xc6/0x16f
May  2 22:01:23 test kernel:  [<ffffffff810a12b2>] sys_write+0x45/0x6e
May  2 22:01:23 test kernel:  [<ffffffff8100c005>] tracesys+0xd5/0xda

Apart from that - it's really fine

[dickeywang]

Originally Posted by Kirurgs

As I promised, some feedback

So the latest news: s2ram (suspend) works (with exception - below), s2disk (hibernate) works (with errors in syslog - below). Everything with 173.08, 2.6.24 kernel, standard swsusp2 for F8, no compiz or other composite w/ managers.
With 173.08 and GylphCache it's faster (really noticeable) with AA fonts, subpixel rendering and so on, no crashes, except wakeup from suspend when certain Wine windows are active.

So when having Oracle Forms6 Designer/Developer open while suspending, upon resume X dies and starts fresh gdm on next available tty. As far as I tested, only mentioned apps are causing trouble. Message in X log is:
Apart from that - it's really fine

hoho, thanks for the feedback Kirurgs. I'm trying to get hibernate work on my T61p with Ubuntu 8.04 for days now, and it's good to know there IS a solution. Too bad that EnvyNG doesn't include 173.08 because it is not a "stable" driver (I guess i could just install the driver manually).

Anyway idea when will the next stable Nvidia driver (assuming to be 173.xx) be released?

[arsenix]

I also have a T61p and am having the same issue you mention. It takes a longgg time to resume due to the "soft lockups" (which did not occur under Gutsy).

I have found that sometimes the machine will resume with screen on but keyboard inactive. Switching to the console with <CTRL><ALT><1> and back to X causes it to come back. (usually when this happens the moon light is still flashing)


James

[Kirurgs]

Ok, some feedback and findings again

s2ram don't work quite well with 173.08. First I thought it was Oracle + Wine stuff, really it wasn't or was just a part of the issue. Symptoms are as I described previously: fresh GDM login and errors in Xorg log and system messages.
Smth like this:

May 20 20:15:24 xxx gdm-binary[2707]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x47fe0d]
1: /lib64/libc.so.6 [0x3101e30f30]
2: /usr/lib64/xorg/modules/drivers//nvidia_drv.so [0x2aaaab3431f8]

Fatal server error:
Caught signal 11.  Server aborting

I'll try to fugure out what is causing these crashes, but I hope new driver will there soon...
I's being a while since last one came out

[krionius]

I find it kind of sad that nvidia people don't show up in this thread. Previously they were more responsive. Anyway it's nice to see that there's some kind of improvement.

[yopyop]

I just received a new T61P and well I have the same problem than you guys: no suspend and no hibernate working. And no solution than wait for better drivers from NVidia...