Suspend with Asus P8P67-M PRO motherboard fails (upstream patch included)

Bug #968016 reported by Aleksi Hankalahti
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The computer appears to go down normally but then it tries immediately start again and crashes. Keeps fans on and doesn't react anything.

I tested this patch from the upstream kernel and it fixes the issue:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=8931d9ea78848b073bf299594f148b83abde4a5e

Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :

Sorry, the affected system is Ubuntu Precise.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 968016

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :

I don't think this needs those logs etc. But please ask if you really want them.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc?

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: patch precise
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-20.33)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-20.33
Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :

The patch is in the Linus' vanilla kernel 3.3.

Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :

Suspend still fails with the kernel 3.2.0-20.33.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Upstream question to see if the patch will make it into linux-stable:
https://lkml.org/lkml/2012/3/1/243

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'll build a precise(12.04) test kernel with the upstream patch, and post a link to it shortly.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I posted a 12.04 test kernel at the following location:
http://people.canonical.com/~jsalisbury/lp968016/

This test kernel has the patch mentioned in the bug description. Can folks affected by this bug test the test kernel and report back if it fixes this bug?

Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :

Like I mentioned in bug #969576 Salisbury's test kernel does not work. When suspending the machine does not even try to shutdown (so the behaviour is completely different than is described in this bug report).

It appears that patches [1] and/or [2] produces a completely new problem.

Currently I am running kernel compiled from source [3] where I removed patches [1] and [2], and applied patch [4]. With this kernel no bug #969576 appears and the machine suspends (and resumes) without any problems.

[1] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=commit;h=4b9161676f4507209b9871f9358421c512b20534

[2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=commit;h=d725ae12539389eb502c6257ccedd2a0bf6025da

[3] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=tag;h=refs/tags/Ubuntu-3.2.0-21.34

[4] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=8931d9ea78848b073bf299594f148b83abde4a5e

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-21.34)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-21.34
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bot-stop-nagging
Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :
tags: added: kernel-fixed-upstream
tags: added: kernel-da-key
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Hi Aleksi,

Do you still require upstream patch [3] in addition to the patches already applied to Precise in bug 969576 ?

[3] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=8931d9ea78848b073bf299594f148b83abde4a5e

Revision history for this message
Herton R. Krzesinski (herton) wrote :

Joseph, from comment #13 I understand that we still require 8931d9ea78848b073bf299594f148b83abde4a5e in Precise.

It seems also that this acpi fix should have gone to stable (http://marc.info/?l=linux-acpi&m=131675442503494&w=2). I asked on stable mailing list for the patch to be applied. Once I get feedback, I'll see it to get applied at least on Precise.

Revision history for this message
Aleksi Hankalahti (aleksi-hankalahti) wrote :

Yes, the 8931d9ea78848b073bf299594f148b83abde4a5e is needed (everything else is already in the Precise's kernel).

Thank you Herton and Joseph!

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Aleksi,
the required commit has landed in precise-updates (with 3.2.0-24.38) - please update to the latest kernel and see if this issue is fixed.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
idokibovito (idokibovito) wrote :

I seem to have the same issue on almost the same motherboard. Mine is the -EVO Version instead of the Pro.
The issue still exists in current official ubuntu builds.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
idokibovito (idokibovito) wrote :

Way to resolve bugs! Just let them expire :)

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.