logout at resume and swap usage (suspend to ram)

Bug #505915 reported by bruno
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-173 (Ubuntu)
Fix Released
Undecided
Unassigned
nvidia-graphics-drivers-180 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: pm-utils

I use Ubuntu 9.10 64 bits with pm-utils 1.2.5-2ubuntu7. I don't talk about hibernation here.
I can suspend to ram and resume, but sometimes, I have to do a new login (my session is not always saved). I didn't have this problem in Hardy 64 bits.

I'm not sure, but It seems to be related to swap partition. I have 2 Gb RAM. Initially, I had 1 Gb swap. The problem was reproducible when more RAM was used (say VBox+other things for about 1.5 Gb usage) but happened more randomly even with low ram usage. Then I had the idea to increase the swap to 2 Gb. Magic: the problem disappeared... until I started to use "fast user switch". With 2 or 3 sessions opened (even with few applications) I often loose one of them (mine...) after a resume. I tried to add another 1 Gb swap partition (3 Gb total). The problem is still present and I'm not sure if it's better with 3 Gb than with 2 Gb.

Conclusion:
1) swap seems to be used with suspend to ram, which seems abnormal
2) logout happen sometimes at resume, at least for the admin user, even with a decent swap partition.

ProblemType: Bug
Architecture: amd64
Date: Mon Jan 11 08:40:06 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: pm-utils 1.2.5-2ubuntu7
PackageArchitecture: all
ProcEnviron:
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: pm-utils
Uname: Linux 2.6.31-17-generic x86_64

Revision history for this message
bruno (brunob) wrote :
Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 505915] [NEW] logout at resume and swap usage (suspend to ram)

On Monday 11,January,2010 10:19 PM, bruno wrote:
> Public bug reported:
>
> Binary package hint: pm-utils
>
> I use Ubuntu 9.10 64 bits with pm-utils 1.2.5-2ubuntu7. I don't talk about hibernation here.
> I can suspend to ram and resume, but sometimes, I have to do a new login (my session is not always saved). I didn't have this problem in Hardy 64 bits.
>
> I'm not sure, but It seems to be related to swap partition. I have 2 Gb
> RAM. Initially, I had 1 Gb swap. The problem was reproducible when more
> RAM was used (say VBox+other things for about 1.5 Gb usage) but happened
> more randomly even with low ram usage. Then I had the idea to increase
> the swap to 2 Gb. Magic: the problem disappeared... until I started to
> use "fast user switch". With 2 or 3 sessions opened (even with few
> applications) I often loose one of them (mine...) after a resume. I
> tried to add another 1 Gb swap partition (3 Gb total). The problem is
> still present and I'm not sure if it's better with 3 Gb than with 2 Gb.
>
> Conclusion:
> 1) swap seems to be used with suspend to ram, which seems abnormal
Swap is never used for suspend to ram. You must have been accidentally
hibernating. Try turning all your swaps off and then suspending to ram. If you
really are, then it will still work.
> 2) logout happen sometimes at resume, at least for the admin user, even with a decent swap partition.
You're probably noticing a crash in X (the display server) upon resume, or
perhaps even X getting OOM-killed, the common factor being X dying after a
suspend/resume cycle. Please post your /var/log/Xorg.*.log.old after this
happens, and also your /var/log/kern.log

  status incomplete

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Contributing Developer

Changed in pm-utils (Ubuntu):
status: New → Incomplete
Revision history for this message
bruno (brunob) wrote :

It happened agin this noon, so I post my Xorg.1.log.old and /var/log/kern.log as asked. Also, I must reject the "accidental hibernation" theory because I never see the BIOS and GRUB steps after a resume; I drop directly to the lock screen (if it's work as supposed) or to the login screen with my session not open (if not, but other sessions can be still opened). Thank you for your time.

Revision history for this message
bruno (brunob) wrote :
Revision history for this message
Chow Loong Jin (hyperair) wrote :

Xorg.1.log.old shows a X server crash. I'm reassigning this to X.

affects: pm-utils (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Incomplete → New
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Revision history for this message
bruno (brunob) wrote :

I think I have found something.

First, I use nvidia-173 (not 180) since I have an old FX5200. Second, the problem happened frequently with a dual screen xorg.conf (separate X screen). With a standard (single screen) configuration, the problem seems to disappear (10 resumes in a row...).

I will investigate soon with twinview to see if I can have a correct dual screen setup without the logout on resume bug. I don't understand why it was related to memory and swap usage, from my observations.

Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in nvidia-graphics-drivers-173 (Ubuntu):
status: New → Incomplete
Revision history for this message
bruno (brunob) wrote :

I have upgraded my system, so I don't know if it's still an issue. As I said in post #6 a possible workaround at that time was to disable the dual-screen (separate X at least). So I will change the status to "fix released" as you suggest.

Changed in nvidia-graphics-drivers-173 (Ubuntu):
status: Incomplete → Fix Released
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.