View Single Post
Old 05-02-08, 06:28 PM   #19
Kirurgs
Registered User
 
Join Date: Jul 2007
Posts: 165
Default Re: nVidia driver + hibernate = no go?

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:
Code:
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.
Code:
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
Kirurgs is offline   Reply With Quote