[Intel DP35DP] Ubuntu 13.04 fails to resume from suspend

[Dāniels Brūvers]

When I suspend the PC everything seems Ok. The computer goes to sleep, screen turns off. When I try to resume the computers seems to get stuck in the first seconds of waking from suspend and doesn't resume. The fans start to spin and the screen turns on but stays black. Nothing else happens and the only way to start the computer is by pressing the Reset button.

Using Ubuntu 13.04 64bit, Kernel 3.8.0-26-generic, Motherboard: Intel DP35DP, Graphics: ATI 1950Pro (Gallium 0.4 on ATI RV570).

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-26-generic 3.8.0-26.38
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: danis 2163 F.... pulseaudio
 /dev/snd/controlC0: danis 2163 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Wed Jul 24 15:56:25 2013
HibernationDevice: RESUME=UUID=e28297d0-bf42-4f58-b4a5-e3b6773a841e
InstallationDate: Installed on 2013-05-07 (77 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=e75c9bc3-c45b-4585-8e7c-66f9bfcbf6b0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-26-generic N/A
 linux-backports-modules-3.8.0-26-generic N/A
 linux-firmware 1.106
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP35DP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81073-207
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/

[Dāniels Brūvers (dbruvers)]

I tested it with the latest kernel. It did not fix the bug.

The was just a minor difference with the upstream kernel. The screen didn't turn on at all when before it turned on but stayed black. I guess this isn't important though, is it.

[penalvch (penalvch)]

Dāniels Brūvers, did this problem not occur in a release prior to Raring?

[Dāniels Brūvers (dbruvers)]

It did occur in 12.10.

With 12.04 everything worked but the machine had another motherboard and less RAM installed.

[penalvch (penalvch)]

Dāniels Brūvers, could you please test for this in Precise via http://releases.ubuntu.com/precise/ and advise if this is still not reproducible with the hardware you reported against?

[Dāniels Brūvers (dbruvers)]

Hello Christopher! Can you please tell me if I can test it with a live version or do I have to do a regular system install?

[penalvch (penalvch)]

Dāniels Brūvers, live version would be fine here.

[Dāniels Brūvers (dbruvers)]

I tested it with a live version of Precise. Unfotunately it did not work. The system failed to resume from suspend as with 13.04.

[penalvch (penalvch)]

Dāniels Brūvers, thank you for testing Precise. For regression purposes, could you please test Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

[Dāniels Brūvers (dbruvers)]

OK, I will test it later this evening or tomorrow.

[Dāniels Brūvers (dbruvers)]

I tested Lucid today and the system still couldn't resume from suspend.

[penalvch (penalvch)]

Dāniels Brūvers, thank you for testing Lucid. Could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/ ?

[Dāniels Brūvers (dbruvers)]

Kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/ didn't fix it.

[penalvch (penalvch)]

Dāniels Brūvers, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/ ?

[Dāniels Brūvers (dbruvers)]

Tested kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/. It also didn't fix it.

[penalvch (penalvch)]

Dāniels Brūvers, using the latest mainline kernel, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Dāniels Brūvers (dbruvers)]

Hello Christoper! The guide says that the debugging procedure "requires a linux kernel with the capability of /sys/power/pm_trace". There is no file pm_trace in my /sys/power directory. What can I do?

[penalvch (penalvch)]

Dāniels Brūvers, you could try with the Ubuntu kernel instead.

[Dāniels Brūvers (dbruvers)]

Alright, so I booted up using the default Ubuntu kernel but I still have no pm_trace. Here are the contents of /sys/power/

disk
image_size
pm_async
reserved_size
resume
state
wake_lock
wake_unlock
wakeup_count

No pm_trace!

[penalvch (penalvch)]

Dāniels Brūvers, sounds like that article would need to be updated. :) Let us skip that part for now. The issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

[Dāniels Brūvers (dbruvers)]

I followed the instructions and reported the problem to the maintainer list of SUSPEND TO RAM.

[Dāniels Brūvers (dbruvers)]

Christopher, I received an email from bugs.launchpad.net saying:

The message you sent included commands to modify the bug report,
but you didn't sign the message with an OpenPGP key that is
registered in Launchpad.

How can I fix this or should I just ignore it? Well, the first mail I sent to the Kernel mailing list got rejected because some HTML got in. I sent another but this time didn't CC it to Launchpad. Could this be the cause of the error? Thank you for your assistance.

[penalvch (penalvch)]

Dāniels Brūvers, could you please provide a direct URL to your mailing list post?

As well, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty/ and advise on if this is reproducible?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]