|
Bugzilla – Full Text Bug Listing |
| Summary: | nvidia: s2ram problems with newer versions of the Nvidia driver | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Elmar Stellnberger <estellnb> |
| Component: | X11 3rd Party | Assignee: | Roland Hui <rohui> |
| Status: | RESOLVED WONTFIX | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
s2ram log of failed s2ram
log before successful and toublefree s2ram-wake nvlog after failed s2ram attempt |
||
|
Description
Elmar Stellnberger
2008-03-05 10:03:27 UTC
Created attachment 198715 [details]
s2ram log of failed s2ram
Created attachment 198729 [details]
log before successful and toublefree s2ram-wake
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.
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. |