Toshiba 550D erratic sleep / hibernate behaviour

[joeyc]

I had been using Gnome for some time but recently stopped because Mageia started going to sleep (suspend to RAM) and I seemed to have no way of waking it up. I tried hitting the power button, "Fn" and power + Fn but nothing would wake the screen up. The power light however came back to green suggesting that it had woken up but there was no response from the screen.

I switched to KDE recently hoping to get more control and for the first few attempts it seemed pretty good. So I started using Sleep (suspend to RAM) and Hibernate (suspend to Disk) more often. However, I am finding that sometimes when I send it to Hibernate I can't always rely on it to suspend properly. And sometimes, when it seems to suspend properly, I can't get it to resume its normal state. I use Sleep less often in KDE but I have encountered similar problems with screen not waking up.

Please let me know what other information you need and sorry if this is vague to start out with.

Regards,
Joey

[djennings]

To diagnose sleep/suspend problems start off with looking at the log file.
/var/log/pm-suspend.log

[doktor5000]

Also can you please post the full model number of your laptop, as "550D" is not the complete model number.

[joeyc]

Also can you please post the full model number of your laptop, as "550D" is not the complete model number.

Is Toshbia NB550D Netbook better? Not sure what other detail to add to it. Can't find any other related numbers on the base either

[joeyc]

To diagnose sleep/suspend problems start off with looking at the log file.
/var/log/pm-suspend.log

This morning when I tried to suspend to disk the thing wouldn't suspend and I couldn't wake it up. The power button was on but it seems that the screen would not wake up

I scanned through the logs and these are the suspect lines that I can see. If you like I can dump the whole thing or please advise what I should be looking for.

Code: Select all

/usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01bootloader hibernate hibernate:


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub> savedefault --default=0 --once
grub> quit

/usr/lib/pm-utils/sleep.d/01bootloader hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/06mysqld hibernate hibernate:
Cannot find mysqld service

/usr/lib/pm-utils/sleep.d/06mysqld hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/10network hibernate hibernate:
Cannot find nfs service
Configured devices:
lo eth0 wlan0
Currently active devices:
lo wlan0
Stopping network (via systemctl):  [  OK  ]

/usr/lib/pm-utils/sleep.d/10network hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/15sound hibernate hibernate:

Not sure why there are so many "hibernate: success" messages either. AFAIK, this is only one hibernation operation.

Thanks again for your help!

[djennings]

The way hibernate/suspend works is there are a number of files in the folder /usr/lib/pm-utils/sleep.d/ ( or /usr/lib64/pm-utils/sleep.d/06mysqld )
Each file suspends/restores a particular part of your system. During hibernate/sleep they are processed starting from the highest numbered file downwards, on restore they are processed from the lowest number up. So those messages you see are telling you about the success of each stage of the process. Do not worry about the messages about nfs and mysqld. They simply mean you do not have those services installed on your computer.

We are interested in messages concerning services 98 and 99, video and video quirks. In particular the video quirks section tries to recognise if you have hardware that needs to be handled in a particular way to avoid a blank screen on restore, which is precisely your problem.
If you could post the log entries for services 98 and 99 on sleeping and on restore, that would be useful. It would also be useful if you tell us what the video hardware is, and which driver you are using. The hardware GUI in Mageia Control Centre will tell you this.

If you are using the nvidia driver you could try switching to the nouveau driver to see if it behaves any differently.

Finally it is a good idea to stick to testing with sleep rather than sleep and hibernate just so you have a consistent test environment. (Plus in my experience it is almost as quick to boot from cold than to restore from hibernate)

[isadora]

Is Toshbia NB550D Netbook better? Not sure what other detail to add to it. Can't find any other related numbers on the base either

Installing the inxi-package, gives great possibilities showing a nice inventory.
After installing, try for example:

Code: Select all

inxi -b

[djennings]

OK Google tells me the 550D has ATI graphics so you should be using fglrx driver.

Reports of 550D failing to restore from sleep on Ubuntu were found to be due to the fglrx driver not being recent enough. That should not be an issue with Mageia because you are already using a newer version of the ATI Catalyst driver ( version 12.0)

According to the ATI wiki http://wiki.cchtml.com/index.php/Troubleshooting it may help to toggle between the laptop screen and the attached CRT monitor using Fn+F8 (maybe a different key on your Tosh)
You could also try switching to a console with Ctl+Alt+F2 and then back to video with Ctl+Alt+F1
Finally you may be able to restore the video system with Ctl+Alt+Backspace twice

[joeyc]

Thanks very much. These sound like useful keys to know anyway so thanks very much!

[joeyc]

Hi djennings - when I tried to wake my machine up I used all three key combinations but could not bring the screen back.

I guess the best we can do for now is to just look out for those service errors and post it here when it does?

[joeyc]

I came across an intermittent failure to hibernate (have always been hibernating because I find that mode to be most useful) - that is, the system did not shut down but continued on as if I didn't issue the command.

Whenever I switch to console with Ctrl + Shift + F2 - the following message is displayed (and I can't type anything)

Code: Select all

Looking for splash system...could not open renderer /dev/fb
could not initialize plymouth : error 0
none
s2disk: Snapshotting system
s2disk: snapshot done
s2disk: returned to userspace


I can still hibernate and wake the system up successfully (so far).

[joeyc]

Does this tell anyone anything helpful?

[joeyc]

Could I get some assistance on this after the festivities have died down?

[doktor5000]

Seems this also drowned :/

Please post the full output of

Code: Select all

lspcidrake -v

and

Code: Select all

rpm -qa | grep firmware

and please
show the output of

Code: Select all

cat /proc/cmdline

when you've booted normally.

Also please verify if it's only the Xserver or the whole screen is dead after resuming, i.e. when the laptop has woken up again,
try to switch to another tty via Ctrl+Alt+ F1 to F8 and see if you get a login or if nothing happens. Another way to check would be to access
the box via ssh login, and see if it's still alive. Or maybe press the NumLock button and see if it still reacts.
And also have a look at /var/log/pm-suspend.log for errors.

Some related links:

https://bugs.launchpad.net/ubuntu/+sour ... bug/738776
http://ubuntuforums.org/showthread.php?t=1799003
Seems it's only about the proprietary fglrx video driver, works without problems for some without it.

You may also want to go through https://help.ubuntu.com/community/BootO ... el_Options

[joeyc]

Code: Select all

lspcidrake -v

ath9k : Atheros Communications Inc.|AR9285 Wireless Network Adapter (PCI-Express) [NETWORK_OTHER] (vendor:168c device:002b subv:11ad subd:6613) (rev: 01)
r8169 : Realtek Semiconductor Co., Ltd.|RTL8101E/RTL8102E PCI Express Fast Ethernet controller [NETWORK_ETHERNET] (vendor:10ec device:8136 subv:1179 subd:fdc0) (rev: 05)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 7 [BRIDGE_HOST] (vendor:1022 device:1719)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 5 [BRIDGE_HOST] (vendor:1022 device:1716)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 6 [BRIDGE_HOST] (vendor:1022 device:1718)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 4 [BRIDGE_HOST] (vendor:1022 device:1704)
k10temp : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 3 [BRIDGE_HOST] (vendor:1022 device:1703)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 2 [BRIDGE_HOST] (vendor:1022 device:1702)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 1 [BRIDGE_HOST] (vendor:1022 device:1701)
unknown : Advanced Micro Devices [AMD]|Family 12h/14h Processor Function 0 [BRIDGE_HOST] (vendor:1022 device:1700) (rev: 43)
unknown : ATI Technologies Inc|SBx00 PCI to PCI Bridge [BRIDGE_PCI] (vendor:1002 device:4384) (rev: 40)
unknown : ATI Technologies Inc|SB7x0/SB8x0/SB9x0 LPC host controller [BRIDGE_ISA] (vendor:1002 device:439d subv:1179 subd:fdc0) (rev: 40)
snd_hda_intel : ATI Technologies Inc|SBx00 Azalia (Intel HDA) (vendor:1002 device:4383 subv:1179 subd:fdc0) (rev: 40)
sp5100_tco : ATI Technologies Inc|SBx00 SMBus Controller [SERIAL_SMBUS] (vendor:1002 device:4385) (rev: 42)
ehci_hcd : ATI Technologies Inc|SB7x0/SB8x0/SB9x0 USB EHCI Controller [SERIAL_USB] (vendor:1002 device:4396 subv:1179 subd:fdc0)
ohci_hcd : ATI Technologies Inc|SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [SERIAL_USB] (vendor:1002 device:4397 subv:1179 subd:fdc0)
ehci_hcd : ATI Technologies Inc|SB7x0/SB8x0/SB9x0 USB EHCI Controller [SERIAL_USB] (vendor:1002 device:4396 subv:1179 subd:fdc0)
ohci_hcd : ATI Technologies Inc|SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [SERIAL_USB] (vendor:1002 device:4397 subv:1179 subd:fdc0)
ahci : ATI Technologies Inc|SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:1002 device:4391 subv:1179 subd:fdc0) (rev: 40)
shpchp : Advanced Micro Devices [AMD]|Family 14h Processor Root Port [BRIDGE_PCI] (vendor:1022 device:1513)
shpchp : Advanced Micro Devices [AMD]|Family 14h Processor Root Port [BRIDGE_PCI] (vendor:1022 device:1512)
snd_hda_intel : ATI Technologies Inc|Wrestler HDMI Audio [Radeon HD 6250/6310] (vendor:1002 device:1314 subv:1179 subd:fdc0)
Card:ATI Radeon HD 2000 to HD 6300 (radeon/fglrx): ATI Technologies Inc|Device 9807 [DISPLAY_VGA] (vendor:1002 device:9807 subv:1179 subd:fdc0)
unknown : Advanced Micro Devices [AMD]|Family 14h Processor Root Complex [BRIDGE_HOST] (vendor:1022 device:1510 subv:1179 subd:fdc0)
hub : Linux 3.3.8-desktop586-2.mga2 ohci_hcd|OHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
btusb : Atheros Communications, Inc.|AR3011 Bluetooth [Wireless|Radio Frequency|Bluetooth] (vendor:0cf3 device:3005)
hub : Linux 3.3.8-desktop586-2.mga2 ohci_hcd|OHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub : Linux 3.3.8-desktop586-2.mga2 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
uvcvideo : Sonix Technology Co., Ltd.|CNF9055 [Video|Video Control] (vendor:04f2 device:b1d6)
hub : Linux 3.3.8-desktop586-2.mga2 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
Module:toshiba : TOSHIBA|TOSHIBA
Pkg:toshutils : TOSHIBA|TOSHIBA

Code: Select all

rpm -qa | grep firmware

kernel-firmware-nonfree-20120421-3.mga2.nonfree
kernel-firmware-20120219-1.mga2
bluez-firmware-1.2-6.mga1
atmel-firmware-1.3-4.mga1
speedtouch-firmware-0.1-9.mga2.nonfree
zd1211-firmware-1.4-5.mga1
radeon-firmware-20120322-3.mga2.nonfree
ipw2100-firmware-1.3-4.mga1
ralink-firmware-20120421-3.mga2.nonfree
rtlwifi-firmware-20120421-3.mga2.nonfree
ipw2200-firmware-3.1-2.mga1
carl9170-firmware-1.9.4-1.mga2

Code: Select all

cat /proc/cmdline

BOOT_IMAGE=linux root=UUID=4a1c6965-ef69-4de3-b390-b2cdf87e8f53 splash quiet resume=UUID=31bb104e-ccb6-4ed2-b6d7-2c1cd1123bf2 vga=788

when you've booted normally.

Not sure what constitutes as normal, sorry. Please give more details.

Also please verify if it's only the Xserver or the whole screen is dead after resuming, i.e. when the laptop has woken up again,
try to switch to another tty via Ctrl+Alt+ F1 to F8 and see if you get a login or if nothing happens.

Have tried Ctrl + Alt + F1 and Ctrl + Alt + F2 and nothing has happened. I will try the other fn keys as well as num lock and report back. Thanks

[joeyc]

Also please verify if it's only the Xserver or the whole screen is dead after resuming, i.e. when the laptop has woken up again,
try to switch to another tty via Ctrl+Alt+ F1 to F8 and see if you get a login or if nothing happens.

Would you believe I actually don't have a num lock key?

Also, have tried Ctrl + Alt + F1 through F8 and the system does not respond.

I should note that the power light indicating that it is discharging is glowing, as is the the wi-fi light.
However, the "disc working" indicator is off. I can also feel / hear the slight vibrations from the cooling fans. Not sure if that helps or not.

Thanks for your help!

[joeyc]

Could I get a hand with this please? Anymore helpful info I can provide from the logs?

[doktor5000]

I still have your thread open in a tab, but didn't get around to looking at it again, as it requires a bit more research.
I'll try to take a look at the weekend - sounds familiar, no? :/

[joeyc]

That's OK! I am sure you are trying your best and I appreciate that

[joeyc]

Hi there - I have noticed that when I just have libre, dolphin and freemind (a java app) open that mostly it will hibernate without too much drama.

If I have vue, another java app it will usually not hibernate properly.

If I shut down all java processes it will usually hibernate and wake up no problem.

[doktor5000]

That sounds more like an application specific problem, not like a generic problem with hibernation/suspend.

Can you take a look in /var/log/pm-suspend.log / /var/log/pm-powersave.log if you see anything suspicious/problematic?
Also please have a look into /var/log/syslog directly after hibernation, back to the time where you sent it to sleep.
You can also try to send it to sleep manually in a terminal via pm-hibernate / pm-suspend.

Apart from that, i've found http://thecodecentral.com/2011/01/18/fi ... orking-bug and https://bugs.launchpad.net/ubuntu/+sour ... bug/738776 and also maybe http://memebeam.org/toys/ToshibaAcpiDriver

What i'd like to know, what does Vue do, or what is that application about, which hardware access does it require?

[joeyc]

VUE is a mind-mapping / graphing type tool http://vue.tufts.edu/index.cfm

In terms of hardware access - I'm not sure how to find the answer to that question. I can't find any sus requirements on their website unfortunately.

[joeyc]

I tried this one ( http://thecodecentral.com/2011/01/18/fi ... orking-bug ) with no success (erratic behaviour still occurs)

I can also confirm that vue is not the issue as the behaviour still occurs when vue is not open. It seems to happen most often when I have many apps open. Not sure how much that helps.