Asus P4P800 motherboard doesn't suspend

[Alexander Jones]

Instantly after suspending, my PC resumes.

[Dave Bowman (dave-abspacken)]

same here. s3 does not work, comes back immediately. s1 and hibernate work fine. i have an asus p4p800e motherboard and edgy.

[Peter Whittaker (pwwnow)]

Thanks for this bug report. To make progress, some more information will be needed. Please attach (by commenting on the bug) to the bug report the output of the following commands:

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

It would also be helpful if you could try to hibernate/suspend and after that fails, restart your system and attach /var/log/kern.log.0 as well.

Thanks again!

[Peter Whittaker (pwwnow)]

Alex, Dave, sorry forgot to tailor the "Stock reply": Some of the required information has been provided, some is still needed.

Also, Alex, does your machine support ACPI? Try booting with acpi=off and seeing if that helps (it should default to APM). I suggest this because of ACPI errors in the dmesg output.

Dave, there are a number of suspend reports on asus machines (e.g., bug #76503, bug #71839, bug #63435) that may be closer to your issue, since you and Alex are running very different hardware - you might want to track one or more of those instead.

[Wietse Koopmans (wietse-koopmans-deactivatedaccount)]

I am running on an Asus P4P800 motherboard and for me, after I press suspend, the system powers off, immediately resumes and comes up in a locked state.
After I unlock the system, a crash report is waiting...

apport suggests the following bug summary: "[apport] vbetool crashed with SIGFPE"

[Alexander Jones (alex-weej)]

Peter - has everything now been provided?

[Peter Whittaker (pwwnow)]

Marking as confirmed based on availability of requested logs. Assigned to ubuntu-kernel-team as per https://wiki.ubuntu.com/KernelTeamBugPolicies

Importance not set as field open to QA/devs/+ only.

[Alexander Jones (alex-weej)]

*wishes he could put a bounty on this*

[Alexander Jones (alex-weej)]

Still happening in Feisty. Quite disheartening. :(

This exact behaviour was present in pre-release Feisty when issuing a halt. The exact being a flicker off of power followed by an immediate resume. I urge anyone who can to take a look at what was done to fix that and apply it here.

[Tom Black (organica)]

Everyone needs to read the Asus P4P800 user's manual. There is a jumper that needs to be switched on the motherboard. The machine will suspend after you change this. At least it worls on mine with Gutsy.

However, the machine will NOT repost video and resume properly. Gutsy just bounces me back to the Login screen and destroys everything I had open while logged in before the suspend.

[Tom Black (organica)]

Ok, so this is not in the downloadable user manual. It's got to be in the printed one. I will check back and repost the jumper settings.

[Alexander Jones (alex-weej)]

Machine suspends fine in Windows XP for years and years. I have checked the manual and the only thing related to suspend is the SMI pair, which is for connecting a case mounted switch. This isn't what you want.

[Tom Black (organica)]

Check out page 56 (or Chapter 2 page 22). The jumpers are the USB S1/S2 and S3 settings. Move the two sets of USB jumpers to the +5VSB configuration.

In the BIOS, set the ACPI to S3 ONLY.

You should get the machine to power down just fine in S3 mode.

The problem is, gutsy resumes to the login screen. The only kernel that works flawlessly for this motherboard is Feisty's vanilla install kernel. After you install Feisty LOCK THE KERNEL UPGRADES. You will have great suspend/resume after that.

[Alexander Jones (alex-weej)]

Did Gutsy resume to GDM even with those jumpers unchanged?

Mine just takes me back to screensaver, as expected. Also, those jumpers control whether USB devices are allowed to wake the machine. If this is really the cause, then there is still a bug in Linux.

To reiterate, this exact same problem was present in pre-Dapper, but for halt situations too. Halt, being far from an edge case, was fixed. Suspend, however, didn't get the same love. I am still suspicious of this.

[Tom Black (organica)]

Yes, Gutsy resumed to the GDM with the jumpers changed or unchanged (however you see it). No screensaver resume here.

[Tom Black (organica)]

Kernel version 2.6.20-15 WORKS perfectly in suspend/resume (at least on my ASUS P4P800...there's no telling your ASUS P4P800 will do the same). Change the USB jumpers and set BIOS to suspend S3 only. Your machine should work.

Yes, I beleive there still is a bug. What was changed from 2.6.20-15 to the current kernel??

[Alexander Jones (alex-weej)]

Still affecting 2.6.24.

[Samant Maharaj (samboneym)]

I can also confirm on 2.6.24-17-generic on Hardy.

[ecepez (ecepez)]

I have an ASUS P4P800 Deluxe Motherboard. I'm not quite sure of the difference between the Deluxe and regular P4P800 versions.

Anyways, I've been battling the suspend issue for a while now. I just stumbled upon this thread, and I had some success.

Suspend to ram to works fine (even after multiple back-to-back suspends). However, I have yet to get suspend to disk to work. The shutdown and memory image is written to disk, but I just get a blank screen upon the resume.

This is after a clean install of Hardy with all the relevant updates.

Here's what I did.

I set USB jumpers to +5VSB as suggested, and changed the BIOS settings as follows:

Under the "Power" menu:
   Suspend Mode => "S3 Only"
   Repost Video on S3 Resume => No
   ACPI 2.0 Support => No
   ACPI APIC Support => Enabled
   Bios->AML ACPI table => Disabled

  > APM Configuration
     Power Management/APM => Enabled
     Video Power Down Mode => Suspend
     Hard Disk Power Down Mode => Suspend
     Suspend Time Out => Disabled

I hope this helps. I have no ideas as far as the Suspend issues go... I can attach a relevant dmseg log if that would help.

[ecepez (ecepez)]

Here's the dmesg log. Let me know if anything else would be helpful, and I'll post.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Leann Ogasawara (leannogasawara)]

Alexander, can you comment if this issue remains in Intrepid's final release? If so, care to give the latest Alpha release of Jaunty a test - http://cdimage.ubuntu.com/releases/jaunty/ . Please let us know your results. Thanks.

[zanny (zanny)]

I confirm, this issue remains in the intrepid final release and in jaunty beta too. Thanks

[Tom Black (organica)]

I have been able to suspend since 2007 with this motherboard. Read my post above, if you change the jumper settings on the motherboard to force S3(?), it works. Read the motherboard's manual before messing with this jumper, I mistakenly flashed my BIOS.

Again, PLEASE give the jumper change a try. This issue was history for my in 2007.

Tom Black

[Alexander Jones (alex-weej)]

Except it works fine in Windows.

[zanny (zanny)]

I can't find the manual right now... I hope, I will find it in the next days. BTW, the suspension works fine for me in windows too, so I am not inclined to think it could be a matter of jumpers. Moreover, I have a vague memory of suspension and hibernation working for a while, so I'll test some old Ubuntu versions (6.06, 6.10, 7.04).

[zanny (zanny)]

I have made some testing with the live version of ubuntu 6.06, 6.10, 7.04, and with each of these live versions the suspension seems not possible (no suspension button available). I fear, suspension is not provided without installing, in such versions. I have not found the manual yet, I will let you know. Thanks

[Peter Whittaker (pwwnow)]

Marking as confirmed based on recent reports that behavior occurs with Jaunty beta.

[DRracer (drracer)]

I have just changed the four jumpers on my Asus P4C800-E motherboard as noted here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/75497/comments/25 .

Many thanks for the advice, my machine running Jaunty with current default kernel 2.6.28-12-generic finally finished the hibernation. No immediate power up as before (even on the 2.6.28-12-generic).

I'm using uswsup's s2disk, the hibernation and resume process itself was working ok before too, but the machine always refused to stop and powered immediately up after S4, I had to manually switch it off before. Now finally ok.

[Peter Whittaker (pwwnow)]

Folks, no new information has been added to this report in almost a year. Could someone please try this with Karmic, or perhaps the Lucid beta?

If the bug continue to occur, please run the command

    apport-collect -p linux 75497

in a terminal window.

If anyone is experiencing a similar problem - but not this exact problem - please attempt first to find a bug report that matches the problem you are experiencing; if you find such a report, please attempt to provide any information by the developers, including possibly running "apport-collect -p linux theBugNumber".

If you do not find such a report the behavior your are experiencing, please open a new report as described in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies

If the behavior no longer occurs or if no new information is provided, I will close this in about two weeks.

[Alexander Jones (alex-weej)]

My P4P system sadly died a death a long time ago, this bug took so long to
be dealt with.

On 25 March 2010 12:30, Peter Whittaker <email address hidden> wrote:

> Folks, no new information has been added to this report in almost a
> year. Could someone please try this with Karmic, or perhaps the Lucid
> beta?
>
> If the bug continue to occur, please run the command
>
> apport-collect -p linux 75497
>
> in a terminal window.
>
> If anyone is experiencing a similar problem - but not this exact problem
> - please attempt first to find a bug report that matches the problem you
> are experiencing; if you find such a report, please attempt to provide
> any information by the developers, including possibly running "apport-
> collect -p linux theBugNumber".
>
> If you do not find such a report the behavior your are experiencing,
> please open a new report as described in
> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
>
> If the behavior no longer occurs or if no new information is provided, I
> will close this in about two weeks.
>
> --
> Asus P4P800 motherboard doesn't suspend
> https://bugs.launchpad.net/bugs/75497
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[DRracer (drracer)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: drracer 2378 F.... knotify4
                      drracer 2593 F.... pulseaudio
                      drracer 2649 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Audigy2'/'SB Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0xdf00, irq 22'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 202
   Simple ctrls : 37
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x300, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=c62df753-b05b-4964-ad7a-21cea4b300d6
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=771d1aa5-febd-452c-925e-283103a8c979 ro xforcevesa quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
RelatedPackageVersions: linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 02/23/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1016.001
dmi.board.name: P4C800-E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1016.001:bd02/23/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4C800-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[DRracer (drracer)]

... it is still the very same. You can see the requested detailed data in the messages above.
... now I'm going to switch the jumpers on my motherboard back to a position, where it works ok

[thomascblack (thomascblack)]

My P4P System is still running strong. I'll get back to you after I test the Lucid Beta1 Live CD.

Tom

---- On Thu, 25 Mar 2010 07:30:30 -0500 Peter Whittaker &lt;<email address hidden>&gt; wrote ----

Folks, no new information has been added to this report in almost a
year. Could someone please try this with Karmic, or perhaps the Lucid
beta?

If the bug continue to occur, please run the command

 apport-collect -p linux 75497

in a terminal window.

If anyone is experiencing a similar problem - but not this exact problem
- please attempt first to find a bug report that matches the problem you
are experiencing; if you find such a report, please attempt to provide
any information by the developers, including possibly running "apport-
collect -p linux theBugNumber".

If you do not find such a report the behavior your are experiencing,
please open a new report as described in
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies

If the behavior no longer occurs or if no new information is provided, I
will close this in about two weeks.

--
Asus P4P800 motherboard doesn't suspend
https://bugs.launchpad.net/bugs/75497
You received this bug notification because you are a direct subscriber
of the bug.

[zanny (zanny)]

I am still affected by this bug too. 2.6.31-21-generic of karmic koala

Zan

[zanny (zanny)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gab 2053 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with AD1985 at irq 5'
   Mixer name : 'Analog Devices AD1985'
   Components : 'AC97a:41445375'
   Controls : 50
   Simple ctrls : 35
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=d85b9955-ce08-478b-8848-69dc47257370
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcCmdLine: root=UUID=c7f52f44-dc04-4df4-8997-e434d1a7a978 ro quiet splash locale=it_IT
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-21-generic N/A
 linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-21-generic i686
UserGroups: adm admin audio cdrom dialout floppy lpadmin netdev plugdev powerdev sambashare scanner video
WpaSupplicantLog:

dmi.bios.date: 10/14/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1019.005
dmi.board.name: P4P800
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1019.005:bd10/14/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[zanny (zanny)]

Upgraded to lucid. The issue persist. Shall I run "apport-collect -p linux 75497" again?

[Steve Langasek (vorlon)]

No. Please don't run 'apport-collect' against bugs you haven't filed unless requested by a developer.

[Tiago Alves (tiagoadalves)]

After years of trying to get Suspend to RAM to work, I've finally managed to thanks to Tom Black (comments #22 and #25) and ecepez (comment #31).

I have an Asus P4P800 Deluxe motherboard and the issue was indeed the USB Power Jumper settings. Just to make sure I also set up my bios according to ecepez's settings. I have the latest bios available for my motherboard (1021.006)

My system info:

Ubuntu 10.04

$ uname -r
2.6.32-24-generic

$ sudo dmidecode -s bios-version
1021.006

[thomascblack (thomascblack)]

Tiago,

I'm glad it worked for you!

Tom

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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