[Dell Inc. Studio 1535] suspend/resume failure

[Peter Whittaker]

May be realted to Zydas WiFi device. Will debug later.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Studio 1535
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=972391a9-cb6f-40d2-b3b1-ebb475951d21 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [Dell Inc. Studio 1535] suspend/resume failure
UserGroups:

* Occured on my Studio 17, same issue (64bit Jaunty)

[Andy Whitcroft (apw)]

Could you please follow the triage and debugging guide (https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume) and report back here.

[Leann Ogasawara (leannogasawara)]

Hi Peter,

I'm going to mark this as a duplicate of bug 349985 for now. Let's focus on that bug for the suspend/resume issues you are seeing.

[Leann Ogasawara (leannogasawara)]

Bah, I meant bug 348757. Thanks.

[Peter Whittaker (pwwnow)]

I undupped this as it is not related to the fglrx driver but is in fact related to the use of the Zydas WiFi antennae. I've just reproduced this - complete crash details are attached to bug #356307, which I've marked as a duplicate of this one.

Crash reproduction methodology:

1. logrotate/savelog all log files

2. Disable all proprietary/restricted drivers

3. Reboot

4. Verify network connection over wired ethernet

5. Unplug wired ethernet, insert Zydas WiFi antenna

6. Connect to WAP, verify network connection

7. Remove Zydas

8. Suspend, resume. All OK.

9. Insert Zydas, connect to WAP, verify network connection

10. Suspend with Zydas inserted. FAIL.

Failure description: Light on Zydas goes out (indicating at least partial attempt to shutdown USB), system appears to start suspend, but "freezes" part way: Can still toggle numlock/capslock, reinserting Zydas makes its light come on (so USB still has power), but system is unresponsive. Or at least, the display never resumes - so perhaps the system is responsive but I cannot see it.

Press and hold the power button, reboot, all is well, but system detects a crash and we end up with this auto-generated bug report, and bug #356307.

I've also attached clean messages file that covers the entire sequence, and will attach a few others as well.

[Peter Whittaker (pwwnow)]

Few more things:

There was no flashing capslock during the test sequence - but at the next reboot the system did detect the crash, hence bug #356307.

Re the DebuggingKernelSuspendHibernateResume Qs:

Is this really a failure? I would think so, yes. I should be able to close the lid and have the system suspend cleanly (providing there are no hardware or driver bugs).

Is this a repetition of a previous failure? No AFAIK; I'm treating this report as the master report for this failure.

Did the machine break while going to sleep or waking up? While suspending - it never made to a suspended state.

Is it reproducible? At will. Refer to comment #5 and bug #356307

Did it work before? No. I've only had this machine a short while and have not tried this with another machine.

Suspend was to-RAM, not to-disk, so the hibernate Qs don't apply.

As a side note, when I was attempting to get the withZydas lspci and lsusb output, I had for the first time a kernel panic as soon as I plugged the Zydas in - but I am unable to reproduce and can find no relevant information in the log files.

[Peter Whittaker (pwwnow)]

I no longer have this machine and can no longer test the problem, so I am marking this as invalid and moving on.