suspend/resume failure reported -- seems to be a false trigger

[gnudoc]

 (Only user activity at the time was synaptic upgrade in process)

ProblemType: KernelOops
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
FlagFile: suspend

InterpreterPath: /usr/bin/python2.5
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 046a:0052 Cherry GmbH
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
OopsText: Suspend/Resume or hibernate problem

Originator: Steve Conklin <email address hidden>
Package: linux-image-2.6.28-5-generic 2.6.28-5.15
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=09747723-d750-476e-abc0-42001e574a92 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-5.15-generic
SourcePackage: linux
Tags: suspend resume hibernate
Title: Suspend/Resume or hibernate problem
UserGroups:

[Leann Ogasawara (leannogasawara)]

Thanks gnudoc.

So it's safe to assume you haven't had any suspend/resume or hibernate issues? Some hooks were added to apport to try to automatically detect suspend/resume issues and it's likely incorrectly detecting an error and filing a false bug report. Thanks.

[gnudoc (gnudoc)]

Never done any suspend/resuming actually, it's a desktop machine. I can
certainly try. Do you want suspend-to-ram, suspend-to-disk or both?

On 27 Jan 2009, 1:55 AM, "Leann Ogasawara" <email address hidden>
wrote:

Thanks gnudoc.

So it's safe to assume you haven't had any suspend/resume or hibernate
issues? Some hooks were added to apport to try to automatically detect
suspend/resume issues and it's likely incorrectly detecting an error and
filing a false bug report. Thanks.

** Changed in: linux (Ubuntu)
      Status: New => Incomplete

-- kernel bug reported by apport - no obvious crash or undesired activity.
https://bugs.launchpad....

[Leann Ogasawara (leannogasawara)]

Heh, then I'd definitely consider this an issue with the apport bug reporting functionality. I'll notify the kernel team. Thanks.

[Andy Whitcroft (apw)]

Thats truly strange. Apport picked up a failed suspend. There really was a suspend _marked_ as in progress on this machine when this apport script was run. We can tell this because of the entry below which is simply the contents of the flag file. As to why that file would ever exist if there was no suspend done ever I am not sure:

    FlagFile: suspend

I wonder if the upgrade was installing the version of apport which supports this. Perhaps you could attach your /var/log/apport.log* files if they have anything in them, and your /var/log/apt/term.log files, as well as pasting in an ls -l of those same files.

[gnudoc (gnudoc)]

$ ls -l /var/log/apport.log*
-rw-r----- 1 root adm 0 2009-02-11 09:02 /var/log/apport.log
-rw-r----- 1 root adm 1230 2009-02-11 01:01 /var/log/apport.log.1
-rw-r----- 1 root adm 251 2009-02-09 04:47 /var/log/apport.log.2.gz
-rw-r----- 1 root adm 405 2009-02-06 20:36 /var/log/apport.log.3.gz
-rw-r----- 1 root adm 712 2009-02-02 21:32 /var/log/apport.log.4.gz
-rw-r----- 1 root adm 246 2009-01-29 18:47 /var/log/apport.log.5.gz
-rw-r----- 1 root adm 202 2009-01-22 22:34 /var/log/apport.log.6.gz
-rw-r----- 1 root adm 284 2009-01-21 20:41 /var/log/apport.log.7.gz

$ ls -l /var/log/apt/term.log
-rw------- 1 root root 108453 2009-02-12 15:15 /var/log/apt/term.log

files attached as requested.

[gnudoc (gnudoc)]

$ ls -l /var/log/apt/term.log*
-rw------- 1 root root 108453 2009-02-12 15:15 /var/log/apt/term.log
-rw------- 1 root root 86083 2009-01-31 22:40 /var/log/apt/term.log.1.gz

[Cruncher (ubuntu-wkresse)]

Recently, there are *many* "suspend/resume failure" reports submitted via apport. Should they all be marked as a duplicate of this one, or is it possible they are all independend and one has to look individually into each report?

Examples: bug #345915, bug #345913, bug #345996, bug #346052, bug #345923, bug #345903, bug #345894, bug #345735...and about 150 more...just search for "resume failure" in Ubuntu bugs to find them.

[Andy Whitcroft (apw)]

On Sat, Mar 21, 2009 at 05:55:46AM -0000, Cruncher wrote:
> Recently, there are *many* "suspend/resume failure" reports submitted
> via apport. Should they all be marked as a duplicate of this one, or is
> it possible they are all independend and one has to look individually
> into each report?
>
> Examples: bug #345915, bug #345913, bug #345996, bug #346052, bug
> #345923, bug #345903, bug #345894, bug #345735...and about 150
> more...just search for "resume failure" in Ubuntu bugs to find them.

There are a class of false-triggers caused (I believe) by attempts to
suspend while you have a kernel update pending. But it is hard to sift
those from the real ones. We have a lot of these reports now as they
were not reported at all before. We are planning to do a pass over them
early next week, and then to get a process in place for early triage.

-apw

[Andy Whitcroft (apw)]

The false trigger here was tracked to a series of late-resume bugs which are now detected correctly by apport. Closing this off.