Bug 367252 - nvidia: s2ram problems with newer versions of the Nvidia driver
Summary: nvidia: s2ram problems with newer versions of the Nvidia driver
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X11 3rd Party (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.1
: P5 - None : Major with 5 votes (vote)
Target Milestone: ---
Assignee: Roland Hui
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-05 10:03 UTC by Elmar Stellnberger
Modified: 2008-05-28 14:32 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
s2ram log of failed s2ram (5.64 KB, text/plain)
2008-03-05 10:06 UTC, Elmar Stellnberger
Details
log before successful and toublefree s2ram-wake (149.29 KB, text/plain)
2008-03-05 10:57 UTC, Elmar Stellnberger
Details
nvlog after failed s2ram attempt (208.73 KB, text/plain)
2008-03-06 10:49 UTC, Elmar Stellnberger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger 2008-03-05 10:03:27 UTC
** S2ram has already been working reliable around the x86-1.0-9746 releases. **

  However on from the 100-series (specifically tested for x86-169.07) the previously known wakeup delays have occurred again: machine works under full power&fan speed for several minutes (instead of the trickle of a second), the screen stays dark and the network interface does not respond; happens every now and then.
  Even worse now at the x86-169.12 release s2ram and s2disk can start to fail completely: 's2ram_do: Resource temporarily unavailable' (see also: http://lists.opensuse.org/opensuse-mobile/2007-05/msg00019.html).
  The problems may be related due to ceasing support for 2.6.16 kernels or perhaps even to the particular bios of this machine (for acpi post see Bug #295083). The support for 10.1 should probably be continued until the next major release(11.0).
Comment 1 Elmar Stellnberger 2008-03-05 10:06:31 UTC
Created attachment 198715 [details]
s2ram log of failed s2ram
Comment 2 Elmar Stellnberger 2008-03-05 10:57:11 UTC
Created attachment 198729 [details]
log before successful and toublefree s2ram-wake
Comment 3 Elmar Stellnberger 2008-03-06 10:49:02 UTC
Created attachment 199090 [details]
nvlog after failed s2ram attempt 

This time it took several s2ram & s2disk cycles to evoke this error. Another time it has occurred directly after booting the machine.
Comment 4 Stefan Dirsch 2008-05-28 14:32:40 UTC
I finally decided to no longer track proprietary NVIDIA driver bugs
against openSUSE. Therefore I'm closing these now as WONTFIX.

In case you're using our SLES/SLED products and can reproduce this
issue also on thesed products feel free to reopen. These are still
tracked, since customers of these products depend on the proprietary
driver for newer NVIDIA hardware.

Be aware that you need a privilleged account to track anything against
our SLES/SLED products. So if this not an option for you I suggest to
report the problem to the official NVIDIA driver feedback channels
(forum/email; see NVIDIA driver download site) and refer to this
bugreport.