[ two FACS tables] Suspend/Resume Fails on Asus K52JT Laptop

This is not a bug in Unity so I am moving the package.

Oops, sorry about that, Omer. I'm not a developer, just trying to make a contribution and help. Thanks for forwarding my bug to the right team.

Hello
Can you please reproduce the bug then attach here, using below button 'Add attachment or patch' these files:
/var/log/kern.log
/var/log/kern.log.1
Thanks
Fabio

Here you go, Fabio. The second file you mentioned "kern.log.1" does not exist in my var/log folder. Thanks for your help.

Apr 8 16:44:52 les-K52JT kernel: [ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20110112/tbfadt-369)
Apr 8 16:44:52 les-K52JT kernel: [ 0.000000] ACPI Warning: 32/64X FACS address mismatch in FADT - 0xBB5B3F40/0x00000000BB5CDD40, using 32 (20110112/tbfadt-486)

[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

Can you please look if your bios is fully updated?
Thanks
Fabio

Can you also try this command in terminal ?

dbus-send --print-reply --system --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend

BIOS is version 204, which is the latest update according to Asus support here:

http://support.asus.com/Download.aspx?SLanguage=en&m=K52JT&p=3&s=245

I pasted the command you supplied above into terminal. It replicated the problem. System went into suspend and wouldn't come out. Blank screen, flashing cursor at top left of screen.

Let's try a last chance:
in terminal

killall gnome-power-manager && gnome-power-manager --verbose 2>&1 | tee ~/gpm.log

reproduce the bug and attach here the generated gpm.log file placed in your home
Fabio

When I paste your command into terminal, it seems to get stuck in a loop, with some error messages (it's been going for about 10-12 minutes so far). Here is some of the output, the part with errors included. Please let me know how to proceed:

*** WARNING ***
TI:11:43:44 TH:0xdfd0a0 FI:gpm-brightness.c FN:gpm_brightness_trust_cache,565
 - using cache for value 0 (probably okay)
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,357
 - values are the same, no action
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_notify_system_idle_changed,421
 - we have just been idle for 8.088603s
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_notify_system_idle_changed,428
 - increasing idle dim time to 160s
TI:11:43:44 TH:0xdfd0a0 FI:gpm-idle.c FN:gpm_idle_set_timeout_dim,296
 - Current idle time=4ms, timeout was 160s, becomes 160s after adjustment
TI:11:43:44 TH:0xdfd0a0 FI:gpm-idle.c FN:gpm_idle_set_timeout_dim,299
 - Setting dim idle timeout: 160s
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_notify_system_idle_changed,446
 - changing powersave idle status to 0
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_brightness_evaluate_and_set,213
 - 1. main brightness 1.000000
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_brightness_evaluate_and_set,233
 - 2. battery scale 0.500000, brightness 0.500000
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_brightness_evaluate_and_set,251
 - 3. idle scale 1.000000, brightness 0.500000
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_brightness_evaluate_and_set,269
 - ERROR: Method "GetBrightness" with signature "" on interface "org.freedesktop.UPower.KbdBacklight" doesn't exist

*** WARNING ***
TI:11:43:44 TH:0xdfd0a0 FI:gpm-backlight-kbd.c FN:gpm_backlight_kbd_brightness_evaluate_and_set,273
 - GetBrightness failed!
TI:11:43:44 TH:0xdfd0a0 FI:gpm-idle.c FN:gpm_idle_evaluate,192
 - X not idle
TI:11:44:06 TH:0xdfd0a0 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,929
 - updating because /org/freedesktop/UPower/devices/battery_BAT0 changed

Fabio, after I posted my last comment, I closed the terminal and closed my laptop lid. When I reopened it, I found it never suspended at all this time. I'm attaching the log file anyway, just in case it's useful.

Just to clarify, when I closed the terminal, it was still stuck in the same loop, so the command never seemed to get fully processed before I killed it.

Okay Fabio, just in case this is what you meant for me to do......

1. Ran your command in terminal (still got caught in loop, but after about 45 seconds, I closed it down, hoping it had done whatever needed to be done by then)
2. Clicked on Suspend under power menu in panel. First, it went to the login screen for a few seconds, but then it went to the blank screen with flashing cursor at top left.

I've attached the new log file for you. Sorry if I misunderstood your instructions. Please advise.

Hello Fabio. It's been a while since my last reply. Just wanted to check on the status of this bug? Thanks.

This bug was reported April 8 and is still undecided as of Apr. 18. I have had no feedback since following the recommended steps. I am requesting that this bug be set to Critical status and fixed before the Natty release.

Sorry, Fabio, but I am not a programmer, just a user trying to make a contribution to Ubuntu. Can you please explain to me what is happening with this bug?

Thanks,
Les.

Hello Les Lamb
this report is actually under developers eyes, but as you are the only reporter, at now, that encounter this problem, it cannot be set as critical.
Sorry
Fabio

I see. Thanks for the explanation, Fabio! Hopefully this will get fixed soon. FYI, since reporting this bug, I have reformatted my drive and installed 11.04 (I was running the beta version when this was reported), and the problem remains.

I can also confirm this bug. I have just installed Ubuntu 11.04 on a brand new Asus K52JT and it also happens.

Whatever I can do to help, please let me know :)

Thanks, Damian! Could you please click on the link near the top that officially indicates that this bug affects you? One of the reasons nothing has been done is because it's showing that only one person (me!) is affected by this, so the more the merrier. :-)

Actually, I found a solution here: http://ubuntuforums.org/showthread.php?t=1460790

Perhaps that fix can be used to make a more permanent fix to include it directly on the Ubuntu's repo.

I hope that helps you too!

Wow, thanks Demian! The fix worked for me. Only problem was Ubuntu Software Center warned me the .deb package was of "inferior quality." But when I clicked on "details" the only reason given was there was "no maintainer address," which makes sense, given that the package was created by a user on the forum, so I ignored & installed. Didn't even have to reboot, it worked immediately. I agree, it would be nice to see this fix included officially, once they can look it over to make sure it's completely safe.

Same prob here with fresh install of 11.04 Ubuttu. The .deb fixed it

Hi,

I have just installed ubuntu 11.04. on MSI NOTEBOOK VR630. It has C77 [GeForce 9100M G] Video card. The symptom is the same. System starts up, suspend works, but after the next startup screen is blank. It is not possible to switch with ctrl-f1 to console.

I have tried the workaround mentioned in the link above, but it does not work for me (it is a different HW).

What should I do? Write a different bug report? Collect logfiles?

thanks,
Regards,
Sandor

I have just tested the resume. After resume I have tried to log in with ssh from an other computer, pings were OK, ssh showed a prompt for password, after typing the password in, the connection was closed.

Same bug on my system.

CPU: AMD Athlon 7750 Dual-Core Black Edition
Mainboard: MSI MA780G-M
Mainboard SB: AMD 780G (ATI 3200HD - Proprietary driver installed)
RAM: 2GB

Same bug on a Toshiba Pro L770: ACPI warning regarding two FACS tables, suspend freezes system with blank screen and flashing cursor in upper left corner.

Anyone found a solution ?

The URL quoted in #22 suggests this little code:

#!/bin/sh
# File: "/etc/pm/sleep.d/20_custom-ehci_hcd".
case "${1}" in
        hibernate|suspend)
              # Unbind ehci_hcd for first device 0000:00:1a.0:
               echo -n "0000:00:1a.0" | tee /sys/bus/pci/drivers/ehci_hcd/unbind
              # Unbind ehci_hcd for second device 0000:00:1d.0:
               echo -n "0000:00:1d.0" | tee /sys/bus/pci/drivers/ehci_hcd/unbind
        ;;
        resume|thaw)
              # Bind ehci_hcd for first device 0000:00:1a.0:
              echo -n "0000:00:1a.0" | tee /sys/bus/pci/drivers/ehci_hcd/bind
              # Bind ehci_hcd for second device 0000:00:1d.0:
              echo -n "0000:00:1d.0" | tee /sys/bus/pci/drivers/ehci_hcd/bind
        ;;
esac

I don't know what this is supposed to do but it actually works. My toshiba L770-12X now suspends/resume perfectly.

Les Lamb, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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'.

Please let us know your results. Thanks in advance.

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

Karma Dorje, 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 Bug Control and Ubuntu Bug Squad 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. Thank you for your understanding.

Status -> Incomplete as action items missing that were requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754192/comments/30 .

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

@Christopher M. Penalver
already filled, please see bug 73805. 6 years passed since the first report of this problem.

Karma Korje, you did not file bug 73805, Hence, it is not already filed.

If you would like the problem you are experiencing addressed, please follow the suggestions noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754192/comments/32 .

Thank you for your understanding.

This is why I usually don't report Ubuntu bugs anymore. It's very discouraging when a legitimate report (with an already known fix) of a significant bug that occurs in 11.04, 11.10 and 12.04 takes a year and a half to get any love. It is now the end of life for 11.04! Since then, I upgraded every 6 months, and with each new release, had to fix it myself with the same simple solution from the forums. Fortunately, I'm trying 12.10 beta 2 right now, and the problem seems to have gone away - although considering the status of this bug, I can only assume that's an accident, rather than someone doing their job.

@Christopher M. Penalver
you can change the status of this bug as invalid or resolved, as it's a vendor problem (buggy acpi tables), not ubuntu.