ATK0110 ACPI not working

Bug #75507 reported by Jonathan Caum
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned
Nominated for Karmic by swaaye
Nominated for Lucid by Andy
linux-source-2.6.17 (Ubuntu)
Won't Fix
Medium
Unassigned
Nominated for Karmic by swaaye
Nominated for Lucid by Andy
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned
Nominated for Karmic by swaaye
Nominated for Lucid by Andy

Bug Description

I believe that any motherboard that uses the ATK0110 ACPI Utility device will not be able to go to Standby/Suspend/Hibernate.

My personal motherboard is an ASUS P5L-MX, with a Maxtor ATA 250gb HDD, a Pentium D 2.67 processor, and 1 Gb of Kingston DDR2 RAM.

I had this same problem with Windows Vista RC1, but I believe ACPI worked with Windows XP.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

With what version of Ubuntu did this fail? Do you get an error message? Please describe the problem and attach the output of 'lspci -vv', 'lspci -vvn' and 'dmesg'.

Revision history for this message
Jonathan Caum (bsalt1313) wrote :

It is on Ubuntu Edgy 6.10, and no error was received; the computer just appeared to be going to standby, and then the hardware turned back on with no video - so I had to press the reset button.

I have attached the text files of each output.

Revision history for this message
vvlist (vvlist) wrote :

My ethernet for this motherboard is not recognized in Ubuntu 6.10. Does anyone else have this problem?

Revision history for this message
Jonathan Caum (bsalt1313) wrote :

I posted another bug report for this issue here:

https://launchpad.net/bugs/77725

It is for the same motherboard - if you are using an onboard Attansic Gigabit Ethernet device.

Revision history for this message
Jonathan Caum (bsalt1313) wrote :

I forgot to update this yesterday, but I had told the power management tool to put my computer in hibernate after a while, and when I turned my computer back on, I'm guessing it was resuming from hibernate, and it came back with video... but no sound. But I'm sure support for this will get better in time.

Revision history for this message
_tom_ (tom-gufler) wrote :

Suspend/Hibernate doesn't work with Ubuntu 7.10 (Gutsy, ~Tribe 6). Motherboard is a Asus P5L-MX.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

tom, thanks for testing with gutsy. Could you also provide the output described on https://wiki.ubuntu.com/KernelTeamBugPolicies and https://wiki.ubuntu.com/DebuggingKernelSuspend ? Thanks!

Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Closing old kernel task.

Changed in linux-source-2.6.17:
status: New → Won't Fix
Revision history for this message
Jonathan Caum (bsalt1313) wrote :

Hey guys, I'm just letting you know that Hibernate works for me now. Standby is still an issue though.

I still have an ASUS P5L-MX.

Revision history for this message
_tom_ (tom-gufler) wrote :

Same with Ubuntu Hardy 8.04 Alpha 4. Suspend (power saving mode) doesn't work at all.

Revision history for this message
_tom_ (tom-gufler) wrote :
Revision history for this message
_tom_ (tom-gufler) wrote :
Revision history for this message
_tom_ (tom-gufler) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Just adding a note that I'm reassigning the Ubuntu Hardy kernel source package from 'linux-source-2.6.24' to just 'linux'. Beginning with the Hardy release the package naming convention changed from linux-source-2.6.x to just linux. Sorry for any confusion.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Tom,

Can you confirm this is still an issue against the latest 2.6.24-7.12 kernel? If this issue still exists, care to attach your dmesg output after a failed suspend/resume cycle as outlined here: https://wiki.ubuntu.com/DebuggingKernelSuspend . Thanks!

Changed in linux:
status: New → Incomplete
Revision history for this message
_tom_ (tom-gufler) wrote :

Hi,

I can confirm that suspend doesn't work with linux-2.6.24-7 (made an update of my ubuntu hardy system 10 min ago). I attach the dmesg.txt file, created as described in https://wiki.ubuntu.com/DebuggingKernelSuspend

Changed in linux:
assignee: nobody → ubuntu-kernel-acpi
importance: Undecided → Medium
status: Incomplete → Triaged
Changed in linux-source-2.6.22:
status: Incomplete → Won't Fix
Revision history for this message
_tom_ (tom-gufler) wrote :

Bug still exists in linux 2.6.24-12-generic

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
eagsalazar (eagsalazar) wrote :

I also have the ASUS P5L-MX board and cannot suspend/resume. I am running Intrepid with all updates applied. I have attached outputs of 'lspci -vv', 'lspci -vvn' and 'dmesg'

Revision history for this message
eagsalazar (eagsalazar) wrote :
Revision history for this message
eagsalazar (eagsalazar) wrote :
Revision history for this message
eagsalazar (eagsalazar) wrote :

A little more info on the observed behavior: When doing either suspend or hibernate (either from shutdown menu or from cli using pm-suspend or pm-hibernate) everything seems to work, the computer in both cases makes all the right sounds but then in both cases it just immediately wakes back up (and successfully everything works afterward). So it seems like I am very close, it is almost like some wakeup event happens right as it is shutting down or suspending (whatever that is when doing hibernate, anyway...).

Revision history for this message
eagsalazar (eagsalazar) wrote :

I have also found that I get this exact same sleep then immediately wake up behavior if I use s2both or sudo /etc/acpi/sleep.sh force (as suggested somewhere on ubuntu forums).

Revision history for this message
vvlist (vvlist) wrote :

I have the ASUS P5L-MX board and cannot suspend/resume, and I'm fully dist-upgraded in Intrepid. I think my problem might be that I use a Nvidia 8600GT video card. Is there anything I can post that may help fixing this or should I just blame the video card?

Revision history for this message
vvlist (vvlist) wrote :

In that last message I meant to say Jaunty not Intrepid.

Revision history for this message
Andy Whitcroft (apw) wrote :

It sounds like there is trouble with suspend on these boards. It sounds like we are getting very close to shutdown and then aborting and resuming. This is normally triggered by a single driver failing to suspend. It would be worth following the suspend/resume debugging guide and reporting back here:

     https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

After 2 months and no response to comment https://bugs.edge.launchpad.net/ubuntu/+bug/75507/comments/26 I'm closing this bug for now. If you are able to provide the requested information, please do so and then reopen the bug by setting the status back to New)

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
x (xyzx-deactivatedaccount) wrote :

I'm experiencing the same behaviour as already mentioned above.

I followed the debugging instructions but there was no additional output from "sudo pm-suspend", so I continued with pm_trace (as per https://wiki.ubuntu.com/DebuggingKernelSuspend). Find attached the relevant logs.

Changed in linux (Ubuntu):
status: Won't Fix → New
Revision history for this message
swaaye (swaaye-gmail) wrote :

I've found that fully disabling USB in the BIOS allows the board to suspend properly. So the problem is related to USB somehow. Also, I have had this standby/suspend problem with Windows XP as well.

Revision history for this message
x (xyzx-deactivatedaccount) wrote :

I can confirm that disabling USB in the BIOS fixes suspend.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

unassigned ACPI team.

Jonathan Caum,
        Please verify if this issue is still present in the latest Lucid build and, should you encounter the issue there, please also test the mainline kernel build to verify if the issue exists there as well.

Thanks!

~JFo

Changed in linux (Ubuntu):
assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) → nobody
status: New → Incomplete
Revision history for this message
Andy (and-codeispoetry) wrote :

Same problems with ATK on Asus X50SL notebook on 9.10 Karmic. I cannot say that suspend doesn't work but Hibernate exactly doesn't work. I got a feeling that it wake up right after hibernate. What I should provide to make it more clear and maybe to make this bug fixed further?

Revision history for this message
Andy (and-codeispoetry) wrote :

I checked it again, suspend works like people said before, I'm confirming same behaviour, PC is just wake up right after suspend.

Revision history for this message
x (xyzx-deactivatedaccount) wrote :

I can confirm this bug is still present in the latest Lucid build.
Same behaviour for both, the Ubuntu kernel
- Linux lucid-desktop 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:52 UTC 2010 i686 GNU/Linux
and the mainline build
- Linux lucid-desktop 2.6.32-02063209-generic #02063209 SMP Wed Feb 24 10:58:08 UTC 2010 i686 GNU/Linux

Revision history for this message
Anakin Starkiller (sunrider) wrote :

I came to the same conclusions of ALexander...(on a ASUS P5L-VM motherboard)
- disabling USB in the bios is a workaround
- this bug is still there on Lucid

Revision history for this message
Anakin Starkiller (sunrider) wrote : apport-collect data

Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: francoise 7802 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xcfcf8000 irq 19'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043c603,00100002'
   Controls : 38
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfffc000 irq 17'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f895630f-c01c-48b8-a458-7a74b9175d69
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-020632-generic root=UUID=c8fb40fa-9562-4a99-af60-15a7c1d62a7c ro quiet splash
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/zsh
RfKill: Error: [Errno 2] No such file or directory
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 2.6.32-020632-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
dmi.bios.date: 10/29/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5L-VM GB
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 2.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.:bvr0302:bd10/29/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5L-VMGB:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Anakin Starkiller (sunrider) wrote : AlsaDevices.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : AplayDevices.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : ArecordDevices.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : BootDmesg.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : Card0.Amixer.values.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : Card1.Codecs.codec.0.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : CurrentDmesg.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : Lspci.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : Lsusb.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : PciMultimedia.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : ProcCpuinfo.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : ProcInterrupts.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : ProcModules.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : UdevLog.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : WifiSyslog.txt
Revision history for this message
Anakin Starkiller (sunrider) wrote : XsessionErrors.txt
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Triaged
Revision history for this message
swaaye (swaaye-gmail) wrote :

I recently discovered that with this board you must set two jumpers to non-default positions for S3 sleep to properly function. The changes alter USB power when in standby. If you don't change them, the board will instantly come back on after entering standby.

Revision history for this message
swaaye (swaaye-gmail) wrote :

Oops, I should say I am referring to the ASUS P5L-MX board. The ASUS P5B is affected as well as are probably other boards with this USB power jumper setup.

Revision history for this message
Anakin Starkiller (sunrider) wrote :

swaaye >> I have a P5L-VM motherboard...do you think it is possible to change those jumpers settings as well ? Have you got any more details about how to do this ?

Revision history for this message
swaaye (swaaye-gmail) wrote :

I looked up the manual for your board and the same USB power jumpers are there. Just go check out the manual on ASUS's site. It's described in there as the "USB device wake-up" jumpers.

These boards come jumpered for S1 sleep instead of S3 sleep.

Revision history for this message
Anakin Starkiller (sunrider) wrote :

Dude, That did the tricks !!!! I've got this "bug" for so many years now !! Thanks !

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

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.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.