11.10 - Suspend fails on Asus 1215B

[Ben]

Suspend fails 20-50% of the time on an Asus 1215B running the amd64 version of 11.10. When it fails the screen is usually off entirely, though sometimes the backlight is still on.

Kernel 3.0.0.11 AMD64
fglrx-updates (2:8.881-0ubuntu3) - also tried with radeon driver, however it made no difference
I have also tried it with the proprietary wifi driver, again it made no difference.

This is similar to my experience on 11.04, which I have attempted to sort out using the directions here https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and by adding suspect modules (brcmsmac, mac80211, radeon) to a SUSPEND_MODULES="" line in /etc/pm/config.d/modules but the problem continues.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ben 1608 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 43'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0xfeb40000 irq 16'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,1043841c,00100100'
   Controls : 12
   Simple ctrls : 8
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=4c9db147-fccc-4793-afc5-ae8c80067362
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
MachineType: ASUSTeK Computer INC. 1215B
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-11-generic root=/dev/mapper/rock-u1110_root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-11-generic N/A
 linux-backports-modules-3.0.0-11-generic N/A
 linux-firmware 1.60
StagingDrivers: brcmsmac brcmutil
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/17/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 1215B
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd06/17/2011:svnASUSTeKComputerINC.:pn1215B:pvrx.x:rvnASUSTeKComputerINC.:rn1215B:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1215B
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Brad Figg (brad-figg)]

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

apport-collect 856711

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.

[Ben (a0-ben-ch)]

As the system is left in an unaccessible state when suspend fails I am unable to run the apport-collect command. I have attempted logging to the RTC but that seems to only produce useful results for resume issues, not suspend.

I would be happy to troubleshoot / test this further.

[Seth Forshee (sforshee)]

Please go ahead and run apport-collect when your machine is running normally then, as the information will still be useful.

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

Sorry about the delay. Please let me know if I can provide any additional information or other assistance.

[Brad Figg (brad-figg)]

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.

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.

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

[Ben (a0-ben-ch)]

After upgrading all packages to their current versions, including the kernel to linux-image-3.0.0-12-generic 3.0.0-12.19, I retested suspend/resume and found that it still fails to work properly.

I tested twice with the BIOS in it's default settings, with CPU Configuration option C6 enabled, and in both cases the system suspended properly, but failed to resume with the screen and backlight remaining off.

I tested twice with the BIOS CPU Configuration option C6 disabled. On the first cold boot I was able to suspend/resume successfully once, however it failed on the second suspend with the backlight and cpu fan remaining on. On the second cold boot I was able to suspend/resume successfully 4 times, however on the 5th suspend attempt the backlight and cpu fan remained on.

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[Ben (a0-ben-ch)]

apport information

[dreamerchant (dreamerchant)]

It's a BIOS bug, ASUS tech-support doesn't want to contact or comment about this problem. Windows works fine, that's why, I think.

[Martin G (gronslet-deactivatedaccount)]

So, let's slashdot the situation, or somehow make Asus take action by other means.

I think we have a strong case. In Norway, if we can confirm that this is a BIOS bug, I can deliver this laptop back to the shop where I bought it and get a refund. I will probably have to fight for a couple of months, and write some letters, but I am willing to do that.

But, the best would be if Asus could provide a BIOS update.

Asus, if you hear me: I will get a refund and tell the world that your hardware is faulty. I will update every bug report and forum post and tell my story (there are quite a few).

(Yes, suspend/resume IS a core feature for a laptop)

[penalvch (penalvch)]

UrkoM / dreamerchant / Martin G, if you are having a problem in Ubuntu, please file a new report by executing the following in the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[dreamerchant (dreamerchant)]

I posted the result of "ubuntu-bug linux" in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006918
Please merge it with this bug.
Today the russian-speaking (I'm in Russia) tech-support contacted me and told they won't do anything as it is shipped with Windows 7 and all other OS doesn't matter for them.

[Ryan Fugger (rfugger)]

We can't expect Asus to fix this bug unless it's costing them money not to.
We should all take a lesson and never buy Asus again. But like it or not,
this laptop will likely not work properly until Linux contains code to
handle its quirks. I've had two laptops with this same issue (the other was
a compaq - bug #675076), so hopefully it's common enough to bother fixing.
On May 31, 2012 6:56 AM, "dreamerchant" <email address hidden> wrote:

> I posted the result of "ubuntu-bug linux" in
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006918
> Please merge it with this bug.
> Today the russian-speaking (I'm in Russia) tech-support contacted me and
> told they won't do anything as it is shipped with Windows 7 and all other
> OS doesn't matter for them.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/856711
>
> Title:
> 11.10 - Suspend fails on Asus 1215B
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/+subscriptions
>

[Ryan Fugger (rfugger)]

May I ask why this bug is now private?

[penalvch (penalvch)]

Ryan Fugger, if you are having a problem in Ubuntu, please file a new report by executing the following in the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[Ryan Fugger (rfugger)]

Christopher, thanks for your reply. I just wanted to know why this bug is now private. It seems that it is useful to have it public so others with this bug can find it, or those considering purchasing an Asus 1215B for use with Ubuntu can make an informed decision. If it is because of recent anti-Asus discussion, maybe you should just censor those comments so the bug can stay visible. If it's another reason, please let us know. Thanks.

[penalvch (penalvch)]

Ryan Fugger, please stop making comments in this report. If you are having a problem in Ubuntu, please perform the actions already requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/comments/96 .

Thanks!

[Martin G (gronslet-deactivatedaccount)]

Well then, so let me ask the same question: Why is this report marked as private?

Was my comment the reason? If so, and if this report is going to stay private, I'd like to delete all the information provided, and invest my time somewhere else.

Christopher M. Penalver: Please answer this simple question, rather than avoiding it.

[penalvch (penalvch)]

Martin G, please stop making comments in this report. If you are having a problem in Ubuntu, please perform the actions already requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/comments/92 .

Thanks!

[Ryan Fugger (rfugger)]

Christopher has contacted me and informed me that this bug was marked private in an attempt to get people to stop commenting with information not directly helpful to the developers working on this bug.

*** IF YOU HAVE THIS BUG, PLEASE OPEN A NEW BUG REPORT WITH THE COMMAND "ubuntu-bug linux" AND SUBSCRIBE CHRISTOPHER TO IT RATHER THAN COMMENTING HERE. ***

It would have helped immensely if Christopher had just posted this information here himself. It would help even more if there were warnings to this effect built into Launchpad when posting a comment.

I am making this bug public again, since making it private does not achieve what it was intended to achieve, and does plenty of harm.

I'll volunteer to stop commenting and ask everyone else to do the same if we can just consider this minor debacle resolved :)

[Launchpad Janitor (janitor)]

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

[Ryan Fugger (rfugger)]

What is still required to confirm this bug? Thanks.
On Jul 31, 2012 3:25 AM, "Christopher M. Penalver" <
<email address hidden>> wrote:

> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/856711
>
> Title:
> 11.10 - Suspend fails on Asus 1215B
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/+subscriptions
>

[penalvch (penalvch)]

Ryan Fugger, what is required is Ben's response to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/comments/86 . For more on this, please see:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Confirmed_Bugs
https://help.ubuntu.com/community/ReportingBugs

Thank you for your understanding.

[Ben (a0-ben-ch)]

Sorry, didn't realise you were waiting on me. I'm in transit at the moment, but will have time to play with the latest upstream kernel later this week and will repeat my testing for the Suspend / Resume from the link you sent. Do you want me to do this on 11.10 or or 12.04? I have access to both on the machine.

[penalvch (penalvch)]

Ben, regarding your comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/comments/105 :
>" Do you want me to do this on 11.10 or or 12.04?"

As you mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/comments/84 , wifi does not work in 12.04, though the suspend problem no longer exists.

Hence, as you reported the problem initially in 11.10, and presumptuously assuming this is the Ubuntu you use primarily due to working wifi, I recommend performing the requested test, and all future suspend testing regarding this report using 11.10.

[Ryan Fugger (rfugger)]

I can report that the suspend problem still exists in 12.04, although
it might happen less frequently.

[pantas (raoul-erdmann)]

Am 01.08.2012 21:18, schrieb Ryan Fugger:
> I can report that the suspend problem still exists in 12.04, although
> it might happen less frequently.
>
i had to switch to MS since this bug is so fatal. i'd rather like to use
linux again. but this is my working machine, but i'm still following
this bug, so finally i could use linux again.

[Choms (choms)]

Bugfix, imho, for the suspend problem (at least for me is working on fedora, and it may also work on ubuntu, please test it and send feedback):

afaik it seems to be a problem with gaphics driver when suspending, to fix it just add "fglrx" or "radeon" or whatever driver you are using to SUSPEND_MODULES line on /etc/pm/config.d/modules

This is my pm modules file, note I've added both open and privative modules:

[choms@neutrino ~]$ cat /etc/pm/config.d/modules
SUSPEND_MODULES="button uhci_hcd fglrx uvcvideo radeon"
SLEEP_MODULE="uswsusp"
S2RAM_OPTS="-f -a 2"

I hope this helps

[Martin G (gronslet-deactivatedaccount)]

Thanks for the update. I'd like to update this report with the following info, which I noticed when I tried to do the workaround suggested by Choms in comment #109:
(uswsusp did not succeed the configuration, as it could not find a valid swap partition)

# cat /etc/fstab |grep swap

# swap was on /dev/sdb5 during installation
#UUID=2310195d-fb73-41b2-9322-f4510f4233ea none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0

Then:
# ls /dev/mapper/cryptswap1
ls: cannot access /dev/mapper/cryptswap1: No such file or directory

Is this partition mapped during suspend initialization, or is it really missing (sometimes)?

I will try to figure out how to create a swap non-encrypted partition or file, and then test the suggestion in #109.

[Ryan Fugger (rfugger)]

I can confirm that adding "radeon" to my SUSPEND_MODULES seems to fix
this bug on 12.04. I have tested 8 or so suspend/resume cycles with
no problems, where before I could only get zero or one suspend/resume
cycles to work before it failed.

My /etc/pm/config.d/suspend_modules reads:

SUSPEND_MODULES="wl radeon"

Previously, the value had been simply "wl", which still seems to be
required for things to work correctly.

Presumably adding "fglrx" instead of "radeon" would help those using
that driver.

Note that this did not work with uswsusp. It seems to work both with
C6 enabled and disabled in the BIOS.

Thanks Choms!

[Sami Mäkinen (sami-makinen-helsinki)]

Should the file be /etc/pm/config.d/suspend_modules or /etc/pm/config.d/modules ?

Added /etc/pm/config.d/modules containing line SUSPEND_MODULES="wl radeon" and rebooted for good measure, but still suspend failed on the first attempt. Failed so hard I had to remove the battery to shut down - I think usually just keeping the power button pressed for a few seconds is enough.

Also tried adding in the full content from Choms' file, and copied also to /etc/pm/config.d/suspend_modules, but still suspend is failing on the first try.

I do have a crypt swap (and crypt root partition), so perhaps that's why Ryan sees success but I don't, as Martin seems to be suggesting. If everyone else is seeing success with adding radeon to the suspend modules list, then I'll file a separate bug about suspending with a crypto disk.

Unfortunately I don't have enough space to test without my crypt disk, and digging the SSD out is a painful operation.

[Stefan Schindler (cafeschintze)]

@sami

Don't bother. I dont have a crypto disk set up and unfortunateliy I'm experiencing the exact same problems. Tried with /etc/pm/config.d/suspend_modules and /etc/pm/config.d/modules

It crashed pretty hard each time I tried to wake it up. Worse than before. So there IS a change. But not the way I'd hoped.

Hoping for a solution.

Cheers, Stefan

[Ryan Fugger (rfugger)]

I'm attaching the output of "lspci -vvnn" so Sami and Stefan can compare -- maybe they have different hardware? Mine seems to be working without issue. Please let me know if there's anything else I can provide that might help find what the difference is.

[Ben (a0-ben-ch)]

Sorry about the delay, I tried with kernel linux-image-3.6.0-030600rc1-generic (the newest kernel available via https://wiki.ubuntu.com/Kernel/MainlineBuilds) today on ubuntu 11.10 and the bug still exists, so the problem continues to exist upstream.

Suspend / resume failed on the second attempt. It appeared as though the video failed to resume. I was using the radeon driver.

Sometimes the machine can appear to be properly suspended, however it will become warm to the touch over time indicating that it is not actually suspended. This only becomes apparent after 30+ minutes so it isn't particularly easy to test for unless you're unusually patient. The machine never resumes properly in such a case.

Regarding recent posts about unloading the radeon driver before suspending, in the past I have tried that with both the radeon and fglrx drivers as well as the brcmsmac or brcm80211 (depending on kernel version) wifi drivers without any improvement.

[penalvch (penalvch)]

Ben, thank you for testing the mainline kernel. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Ryan Fugger (rfugger)]

I have to report that adding "radeon" to SUSPEND_MODULES doesn't actually fix the problem completely -- I'm still getting crashes on resume (requiring hard reset) about 20% of the time. My sense is the longer it remains suspended, the more likely it is to crash. In my initial testing, it worked fine, but I was only suspending for a few seconds.

Christopher, please note that I have tried the "resume-trace" debugging procedure, and it didn't work for me -- no magic number in dmesg output after resuming. I suspect this is because you have to remove the battery and power supply for the computer to restart properly after crashing on resume, but it's certainly possible I did something wrong.

[Launchpad Janitor (janitor)]

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

[Ben (a0-ben-ch)]

I built kernel 3.6.9 using the attached .config on December 8th and suspend/resume has consistently worked for me ever since. That said, I have noticed some X related issues that seem to be related to dual monitors. If I have been using a 2nd monitor (plugged in via HDML - haven't tried with VGA) and suspend, when I unsuspend without a second monitor attached the display is unresponsive and I have to restart X or plug in a second monitor to get X working again. The work around is to use the Monitors application to disable the second monitor before suspending the laptop.

Note - I hadn't tried any kernels between 3.5.4 and 3.6.9, it is possible that the issue was fixed before 3.6.9.

The BIOS bug noted earlier in this report remains an issue, so if you wish to reboot after using suspend/resume you have to remove the battery and disconnect the power before rebooting or the system will hang after the BIOS splash screen, this is an ASUS/BIOS issue, and not kernel/OS related.

[penalvch (penalvch)]

Ben, as per http://www.asus.com/Eee/Eee_PC/Eee_PC_1215B/#download a BIOS update is available for your computer (0503). Could you please update to this, and then test for the suspend problem in a Raring live environment via http://cdimage.ubuntu.com/daily-live/current/ and comment to the results?

[Ben (a0-ben-ch)]

Updated to that BIOS a long time ago, with no noticeable change from a suspend/resume perspective.

Short-term testing isn't of much value given the nature of the problem, but I'll see what I can do about the Raring testing.

[gRUblo (raznoeg)]

Ставим ядро выше 3.5 (включительно) и всё будет работать, кроме grub. Проверенно, Debian 6.0.6 amd64, ядро 3.6.9, Gnome 2.30.2. Asus 1215b e-450

[penalvch (penalvch)]

gRUblo, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Ryan Fugger (rfugger)]

gRUblo's comment translates to:

Put the core above 3.5 (inclusive) and will work, except grub.
Proven, Debian 6.0.6 amd64, kernel 3.6.9, Gnome 2.30.2. Asus 1215b
e-450

[Sami Mäkinen (sami-makinen-helsinki)]

Just tried the Raring 3.8 kernel on 12.04. System suspended, but died when resuming. Black screen, no response, had to hard poweroff.

[penalvch (penalvch)]

Sami Mäkinen, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Sami Mäkinen (sami-makinen-helsinki)]

Christopher, why are you asking to file a new bug when my testing is relevant to the bug discussed above please? I would think having duplicates would make it more difficult to manage fixes?

BTW I noticed that I do not have the latest BIOS after all, so I will update it and re-test in 12.04 with a few kernels including the raring one. Will test with a full raring live environment as soon as I figure out the easiest way to do that without replacing my working 12.04 installation or opening the computer.

[Launchpad Janitor (janitor)]

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