[nvidia-glx] s2ram followed by s2disk fails unless VBE posting is disabled

Bug #104889 reported by rez
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-restricted-modules-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

On Dell Inspiron E1505 with Nvidia GeForce Go 7300, a s2ram followed by a s2disk causes the screen to flicker endlessly when the system resumes from the s2disk. You have to manually restart the machine in order to bring it to a workable state.

Changed in linux-restricted-modules-2.6.20:
assignee: nobody → ubuntu-kernel-acpi
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

rez:
Are you using the nvidia binary drivers? If so could you include the output of
dpkg -l nvidia\* | grep ii
and upload your
/etc/X11/xorg.conf
file please?

Setting to needsinfo pending reply from rez.

Changed in linux-restricted-modules-2.6.20:
status: Confirmed → Needs Info
Revision history for this message
Ben Collins (ben-collins) wrote :

I confirmed this on a 1505 also with 7300 but only with the nvidia 9755 driver. I think we need to come up with some way to work with nvidia on this issue. See if it's already been reported and link the bug reports.

Changed in linux-restricted-modules-2.6.20:
assignee: ubuntu-kernel-acpi → nobody
status: Needs Info → Confirmed
Revision history for this message
rez (rezwanul-kabir) wrote :

Attaching logs as requested by Sitsofe

Revision history for this message
rez (rezwanul-kabir) wrote :

Attaching logs (xorg.conf) as requested by Sitsofe

Revision history for this message
rez (rezwanul-kabir) wrote : RE: [Bug 104889] Re: s2ram followed by s2disk fails

Ben

   I have updated launchpad with the info that Sitsofe asked..
   Thanks..
      --rez

> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On
> Behalf Of Ben Collins
> Sent: Tuesday, April 24, 2007 12:19 PM
> To: Kabir, Rezwanul
> Subject: [Bug 104889] Re: s2ram followed by s2disk fails
>
> I confirmed this on a 1505 also with 7300 but only with the
> nvidia 9755 driver. I think we need to come up with some way
> to work with nvidia on this issue. See if it's already been
> reported and link the bug reports.
>
> ** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
> Assignee: Ubuntu Kernel ACPI Team => (unassigned)
> Status: Needs Info => Confirmed
>
> --
> s2ram followed by s2disk fails
> https://bugs.launchpad.net/bugs/104889
> You received this bug notification because you are a direct
> subscriber of the bug.
>

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote : Re: [nvidia-glx] s2ram followed by s2disk fails

rez, Ben:
Does using NvAGP "1" as described in Bug #34043 make any difference?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Setting to neesinfo pending reply

Changed in linux-restricted-modules-2.6.20:
status: Confirmed → Needs Info
Revision history for this message
rez (rezwanul-kabir) wrote :

Setting NvAGP "1" does not work.
However, setting SAVE_VBE_STATE=false and POST_VIDEO=false does solve the problem for me..

Changed in linux-restricted-modules-2.6.20:
status: Needs Info → Confirmed
Changed in linux-restricted-modules-2.6.20:
assignee: nobody → ubuntu-kernel-team
Changed in dell:
status: New → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

(Ever so slightly related to Bug #14833 . Also mentioned in https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend but that also makes mention on NvAGP)

Revision history for this message
Jose De la Rosa (jose-de-la-rosa) wrote :

Same workaround for 100.14.19 driver on Gutsy (setting SAVE_VBE_STATE=false and POST_VIDEO=false in /etc/default/acpi-support).

Changed in dell:
importance: Undecided → Medium
Revision history for this message
pauls (paulatgm) wrote :

Should the kernel version be changed to gutsy's?

Revision history for this message
Jose De la Rosa (jose-de-la-rosa) wrote :

Works with workaround.

Changed in dell:
importance: Medium → High
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in linux-restricted-modules-2.6.22 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-restricted-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance.

Changed in linux-restricted-modules-2.6.22 (Ubuntu):
status: Incomplete → Won't Fix
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in somerville:
importance: Undecided → High
status: New → Fix Released
no longer affects: dell
Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305712

no longer affects: somerville
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.