[SOLVED] Cannot resume from suspend but hibernate works fine

Please help me figuring out what can be the issues..
I cannot resume from suspend while "sudo pm-hibernate" works fine..
When I use "sudo pm-suspend", the system (samsung N210 netbook) goes to sleep and I can see the power light blinking as expected. But, when I try to resume the system from suspend by pressing the power button, the screen remains black with no HDD activity. Only thing I can see is the power LED on.
After I do "sudo pm-suspend" and try to resume from suspend but fails. So, I do a HARD reboot and then this is the content of /var/log/pm-suspend.log
Initial commandline parameters:
Thu Dec 16 12:00:27 IST 2010: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux archlinux-N210 2.6.36-ARCH #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010 x86_64 Intel(R) Atom(TM) CPU N450 @ 1.66GHz GenuineIntel GNU/Linux
Module Size Used by
dm_mod 66662 0
rfcomm 34874 4
sco 8828 2
bnep 8726 2
l2cap 42585 16 rfcomm,bnep
ipv6 281833 24
nls_utf8 1288 0
cifs 242984 0
fscache 39915 1 cifs
fuse 64259 3
arc4 1378 2
snd_seq_dummy 1431 0
snd_hda_codec_realtek 275887 1
uvcvideo 61404 0
videodev 64318 1 uvcvideo
v4l1_compat 15578 2 uvcvideo,videodev
ecb 2041 2
snd_seq_oss 28760 0
ath9k 80424 0
joydev 10055 0
btusb 11385 2
v4l2_compat_ioctl32 10212 1 videodev
bluetooth 52419 9 rfcomm,sco,bnep,l2cap,btusb
snd_seq_midi_event 5436 1 snd_seq_oss
mac80211 196159 1 ath9k
ath9k_common 3624 1 ath9k
ath9k_hw 290909 2 ath9k,ath9k_common
snd_hda_intel 22285 1
snd_hda_codec 79384 2 snd_hda_codec_realtek,snd_hda_intel
ath 8822 2 ath9k,ath9k_hw
snd_seq 50082 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 5297 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 39221 0
cfg80211 143110 3 ath9k,mac80211,ath
snd_hwdep 6110 1 snd_hda_codec
uhci_hcd 21926 0
easy_slow_down_manager 3185 0
snd_mixer_oss 17106 2 snd_pcm_oss
snd_pcm 71921 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 19265 2 snd_seq,snd_pcm
cpufreq_powersave 958 0
sky2 46293 0
rfkill 15882 3 bluetooth,cfg80211
led_class 2331 1 ath9k
snd 57562 11 snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_hda_codec,snd_seq,snd_seq_device,snd_pcm_oss,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
psmouse 52592 0
cpufreq_ondemand 8215 2
soundcore 5969 2 snd
ehci_hcd 36988 0
tpm_tis 7928 0
shpchp 26453 0
sg 25652 0
phc_intel 9527 1
battery 10231 0
tpm 10957 1 tpm_tis
samsung_backlight 2844 0
serio_raw 4486 0
snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
usbcore 137570 5 uvcvideo,btusb,uhci_hcd,ehci_hcd
ac 3105 0
pci_hotplug 24319 1 shpchp
tpm_bios 5505 1 tpm
i2c_i801 8550 0
freq_table 2323 2 cpufreq_ondemand,phc_intel
pcspkr 1819 0
thermal 12242 0
evdev 8519 14
processor 25936 1 phc_intel
mperf 1243 1 phc_intel
ext4 313574 1
mbcache 5722 1 ext4
jbd2 69002 1 ext4
crc16 1297 2 l2cap,ext4
sd_mod 25856 4
ahci 20353 3
libahci 17982 1 ahci
libata 156316 2 ahci,libahci
scsi_mod 124891 3 sg,sd_mod,libata
i915 321187 3
drm_kms_helper 25963 1 i915
drm 175314 3 i915,drm_kms_helper
i2c_algo_bit 4911 1 i915
button 4834 1 i915
i2c_core 18726 6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video 19305 1 i915
output 1940 1 video
intel_agp 29459 2 i915
total used free shared buffers cached
Mem: 2046212 603128 1443084 0 11400 258660
-/+ buffers/cache: 333068 1713144
Swap: 2250748 0 2250748
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
/usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /etc/pm/sleep.d/20_samsung-tools suspend suspend:
/etc/pm/sleep.d/20_samsung-tools suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/91wicd suspend suspend:
/usr/lib/pm-utils/sleep.d/91wicd suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Dec 16 12:00:31 IST 2010: performing suspend
Since, the last time I checked about suspend was 1.5 months back, I cant really make out as to what package caused the issue as I had a few upgrades since that time.
I am no expert but it seems like it is the log of suspending the system, it seems like the system didnt even go to initial stage of resuming.
Last edited by shadyabhi (2010-12-27 17:54:19)

Well this is a long shot... But my laptop had some issues with suspending due to low-power governors preventing it from fully working at times.
Because of that I manually suspend with the following script:
#!/bin/bash
clear
cpufreq-set -g performance
cpufreq-info
echo "Continue? y/n? ";read bevestiging
if [ $bevestiging = "y" ]
then
echo "System going down for suspension NOW!"
pm-suspend
else
echo "Exiting..."
exit 0
fi
exit 0
All it really does in the end, is change the governer from which it's currently on to "performance", thus allowing maximum clock speed.
I've also added in a little confirmation dialog to check whether it's properly switched.
Of course, this will only work for you if you're also using laptop-mode and cpufrequtils.
Edit: You need to run this script with sudo or as the root user.
Last edited by Aeva (2010-12-16 14:16:32)

Similar Messages

Satellite Pro A200GE-1F9 cannot resume from Sleep or Hibernate with SP1

Hi,
Laptop Details: [My Laptop|http://uk.computers.toshiba-europe.com/cgi-bin/ToshibaCSG/jsp/SUPPORTSECTION/discontinuedProductPage.do?service=UK&BV_UseBVCook ie=yes&PRODUCT_ID=131911]
I've recently used Windows Update to install vista SP1 on my laptop, however since this install I cannot resume from Sleep or Hibernate. (The service pack had installed successfully - according to Windows anyway).
When resuming from Sleep, I get a blank screen.
When resuming from Hibernation, I get a STOP error: +Stop 0x0000008E (0xC0000005, 0x82F11020, 0x9A9D9714, 0x00000000)+ caused by *Classpnp.sys*.
After checking these forums, I've seen that Toshiba does not currently support SP1 +is that correct?+
+*If so, when/how will we be notified when Toshiba release a "patch" for Vista SP1 compatibility? I'm guessing via the TEMPO service?*.+
Prior to installing SP1, I installed all updates (from both Microsoft and Toshiba) and had no problems; all drivers remain up to date.
Thanks for any replies in advance.

I presume this happens due to a compatibility issue between some drivers and SP1
> After checking these forums, I've seen that Toshiba does not currently support SP1 is that correct?
Yes this is right.
> If so, when/how will we be notified when Toshiba release a "patch" for Vista SP1 compatibility? I'm guessing via the TEMPO service?
I think there should be information on the Toshiba driver page, support page or we will receive some information from Toshiba via Tempo applications.
We will see

After configuring SSL, cannot run Report Manager but ReportServer works fine

I'm using SSRS 2014 as part of SQL Server 2014 Express. I've configured both the Web Service URL and the Report Manager URL to use a Certificate and only allow port 443 traffic. I did this by removing the port 80 identity and adding an SSL Identity.
All is working well for https://myserver.com/ReportServer. But when I try and access report manager, I get the following error when running remote:
The underlying connection was closed: Could not
establish trust relationship for the SSL/TLS secure channel.
When running directly on the server, the server, it just rejects my passwords and asks for it again.
If I remove the SSL Indentity and add back in port 80, it works fine over https.
Any ideas of what might be causing this problem?
Thanks,
Glenn
Please mark this post as Answered if it solved your problem, otherwise you can click Vote if it helped you out. -Glenn Thimmes

Hi Glenn,
Per my understanding that you have added an SSL Identity and you got some errors "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." when you logging remotely to the report manager,
but which work fine when login report server, and it also asked for credential when you login report manager locally, right?
The issue can be caused by many factors. Please check below points one by one to help you clarify:
In rsreportserver.config file(Path like this:C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer), ensure that SecureConnectionLevel is set to the value 2 or 3. If disable the SSL value is set to 0. Corrected
line in your rsreportserver.confiog file should look like:
<Add Key="SecureConnectionLevel" Value="3"/>
In rsreportserver.config, add the correct value to the <URLRoot> element. the ReportServerUrl value must be the name of the server that is registered for that certificate. with a hostname that is valid for your certificate. For example, if the
certificate is registered to https://adventure-works.com.onlinesales, the report server URL would be
https://adventure-works.com.onlinesales/reportserver.
<UrlRoot>
https://adventure-works.com.onlinesales/reportserver.
</UrlRoot>
Ensure that your certificate exists in Trusted Root Certification Authorities in certmgr for the local machine.
http://www.c-sharpcorner.com/uploadfile/anavijai/could-not-establish-trust-relationship-for-the-ssltls-secure-channel/
This is very important. In rsreportserver.config file, add the same value to the <ReportServerUrl> element the same as that you added in step 2.
<ReportServerUrl>
https://adventure-works.com.onlinesales/reportserver.
</ReportServerUrl>
Then restart your report server (stop & then start in Report Server Configuration Manager).
Article related to this issue also contain the troubleshooting for your reference:
http://msdn.microsoft.com/en-us/library/ms345223(v=sql.100).aspx
Similar threads for your reference:
Could not establish trust relationship for the SSL/TLS secure
channel
SSRS 2008- Underlying connection
was closed – could not establish trust relationship for SSL/TLS
If your problem still exists, please try to provide us snapshopt about the setting for the SSL Identity and also the Report Manager URL,etc.
Regards
Vicky Liu

[SOLVED] cancel resume from suspend

Hi,
I have suspended my machine instead of turning it off to boot temporarily into Windows. Now I want to go back to archlinux, but I don't want to resume the session, but restart normally. How can I cancel the resume process in arch? Everytime I reboot, it keeps dropping back into the password prompt to give the password to decrypt the swap file and resume, but I don't want to resume!
Removing resume=/dev/swap from grub does not solve my problem.
Any advice appreciated!
Last edited by awayand (2011-09-18 04:25:06)

yes, I realize that, thanks, lucke, since you mention it, here's why I need it:
I auto-mount my windows partition on my dual-boot machine when running in archlinux, and most of the time, I just hibernate linux by closing the lid of my laptop. Very rarely I boot into windows when turning the laptop back on. However, I am using qbittorrent to download to my windows partition, since it has a lot more space and I don't want to repartition, but I am downloading through archlinux. So when I hibernate, the files on the windows partition are still "open", and the filesystem is still mounted. Now if I boot into windows when I turn the computer back on, I will run into trouble if after that, I resume back into archlinux, because the files on windows will have changed and arch will be confused. In that case, I have to just throw away the resume-image in arch to start from scratch. Hope that made sense.

[SOLVED] After resume from suspend to RAM, system is slow / unstable

Hello,
I have come across some strangeness when trying to suspend my system. The
computer is a lenovo U350. I have read a lot of threads on these subjects,
but I never found one that quite matched the experiences I'm having, so I felt
compelled to make a new post.
Here's what's going on: I boot into the terminal, and then run pm-suspend.
Within a few seconds, the computer goes to sleep, just as I had hoped. The
problem is that my computer seems a little groggy when I wake it back up.
Usually, when running a command like ps aux | less, the screen fills up very
quickly. After I resume from sleep, running ps aux | less is noticeably slow.
It takes a full second (+/- epsilon) to fill the screen. Other symptoms: if I
suspend / resume in the terminal, and then start a window manager (KDE), the
graphics will be slow and choppy, and when I try to exit the window manager, I
usually end up having to perform the dreaded REISUB after getting stuck on a
blank screen with a non-blinking cursor in the upper left hand corner.
Suspend / resume from KDE will result in either the black, non-responsive
screen as soon as I try to resume, or in the choppy graphics, followed by the
non-responsive black screen when I log out.
I looked at the process list before and after, and noticed that when the
system is first resumed, there are around 50-60 additional kworker processes
running than when I put it to sleep. I don't know if this is normal or not.
Also, hci0 has been killed, and a new hci0 process has taken its place. The
same goes for one of the udevd processes. About 40-50 of the kworker
processes finish after a few minutes, but this does not change the slowness of
ps aux | less, nor does it help with my window manager issues.
I ran a few (not so precise) performance tests before and after doing a
suspend, and got the same results (the test was just to compile some LaTeX,
which took about 4-5 seconds either way).
I examined the pm-suspend.log, and everything looked peachy. All of the
hooks returned success for the suspend, as well as the resume. I'm happy to
post this if needed. I did not change any of the default settings for
pm-suspend.
Anyhow, I've read a lot of threads, and seen a lot of suggestions, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=137682
https://bbs.archlinux.org/viewtopic.php?id=136292 (use vbetool?)
https://bbs.archlinux.org/viewtopic.php?id=126174 (suspend tons of modules?)
https://bbs.archlinux.org/viewtopic.php?id=131827 (hpet=disable ?)
However, I'm not that confident in any of them, since no one had quite the
same issue. I was hoping that someone could point me in the right direction
before I start blindly walking through all the candidate fixes and risk
unleashing chaos into my system. Many thanks in advance for your help.
Oh, and in case this post was not yet long enough, here is some system
information:
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
lsmod:
Module Size Used by
aes_x86_64 7508 3
cryptd 8309 0
aes_generic 26138 1 aes_x86_64
coretemp 5590 0
cpufreq_ondemand 6164 2
acpi_cpufreq 5877 1
mperf 1275 1 acpi_cpufreq
freq_table 2515 2 acpi_cpufreq,cpufreq_ondemand
arc4 1410 2
joydev 9895 0
snd_hda_codec_hdmi 24121 1
iwlwifi 248196 0
i915 420018 3
snd_hda_codec_conexant 47300 1
uvcvideo 64311 0
mac80211 228527 1 iwlwifi
videodev 82101 1 uvcvideo
snd_hda_intel 23375 0
snd_hda_codec 89389 3 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
broadcom 7270 0
tg3 134884 0
ideapad_laptop 8534 0
snd_hwdep 6389 1 snd_hda_codec
snd_pcm 74780 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc 7153 2 snd_pcm,snd_hda_intel
snd_timer 19544 1 snd_pcm
snd 59214 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
iTCO_wdt 11885 0
v4l2_compat_ioctl32 8316 1 videodev
i2c_i801 8187 0
i2c_algo_bit 5263 1 i915
drm_kms_helper 26137 1 i915
intel_agp 10904 1 i915
btusb 11385 0
cfg80211 172260 2 mac80211,iwlwifi
bluetooth 151999 1 btusb
sparse_keymap 3120 1 ideapad_laptop
soundcore 6210 1 snd
drm 188499 4 drm_kms_helper,i915
rfkill 15498 3 bluetooth,cfg80211,ideapad_laptop
serio_raw 4429 0
iTCO_vendor_support 1961 1 iTCO_wdt
media 10597 2 videodev,uvcvideo
psmouse 61311 0
libphy 16985 2 tg3,broadcom
i2c_core 20492 6 drm,drm_kms_helper,i2c_algo_bit,i2c_i801,videodev,i915
intel_gtt 14519 3 intel_agp,i915
pcspkr 1819 0
evdev 9530 8
thermal 7799 0
wmi 8475 0
battery 6453 0
ac 2344 0
video 11164 1 i915
button 4470 1 i915
processor 25582 3 acpi_cpufreq
ext4 420412 3
crc16 1359 2 ext4,bluetooth
jbd2 71499 1 ext4
mbcache 5881 1 ext4
sd_mod 28307 5
ahci 20037 4
libahci 19559 1 ahci
libata 166654 2 libahci,ahci
scsi_mod 133676 2 libata,sd_mod
uhci_hcd 23116 0
ehci_hcd 40698 0
usbcore 146113 5 ehci_hcd,uhci_hcd,btusb,uvcvideo
usb_common 954 1 usbcore
Last edited by wes (2012-04-06 21:34:43)

I did try reinstalling, actually. But I did not think to remove the battery and the ram... I'm very curious now: what is the rationale / intuition for that? Or is it just that empirical evidence suggests this may be a good idea?
Anyhow, the reinstall by itself did not help. I tried it out with a pretty bare-bones setup and had the same results. Here are a few other things I noticed:
- After the suspend, one of the cores is always running at the maximum clock frequency, according to powertop (although, according to ps aux, no one is doing any work).
- Even if I ssh to a nearby machine, I get the same experience when running `ls`. The screen fills very slowly. That narrows things down a little bit, but I was already guessing it would be graphics-related.
I have also tried a few random kernel boot parameters after reading things online, but none of those worked, and several stopped the machine from booting at all.
Thanks for your help.

Cannot resume from suspend when done with acpi (close lid)

This is my /etc/acpi/handler.sh
#!/bin/sh
# Default acpi script that takes an entry for all actions
# NOTE: This is a 2.6-centric script. If you use 2.4.x, you'll have to
# modify it to not use /sys
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
ac_adapter)
case "$2" in
AC)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
*) logger "ACPI action undefined: $2" ;;
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000) #echo "offline" >/dev/tty5
00000001) #echo "online" >/dev/tty5
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
#echo "LID switched!">/dev/tty5
/usr/sbin/pm-suspend
logger "ACPI group/action undefined: $1 / $2"
esac
The only thing I added was the /usr/sbin/pm-suspend.
When I run /usr/sbin/pm-suspend from a terminal, the suspend works fine, but when I try to use the close lid suspend I have trouble resuming. When I open the lid, the laptop starts making noises and lights up (as if it were to resume), but after a while it goes and suspends again.
Pushing the power button to try to resume (this is how I successfully resumed from the commandline suspend) causes the same behavior to happen, so I ended up just holding down the power button and rebooting.
I tried commenting the /usr/sbin/pm-suspend, and uncommented the default echo line. This caused "LID switched!" to be displayed 3 times on /dev/tty5; each one on the next line further to the right. I'm not sure if that is supposed to be normal behaviour.

Hi, sorry my fault. I should have been more specific. Here my full handler.sh
#!/bin/sh
# Default acpi script that takes an entry for all actions
# NOTE: This is a 2.6-centric script. If you use 2.4.x, you'll have to
# modify it to not use /sys
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PWRF) logger "PowerButton pressed: $2"
/usr/sbin/pm-suspend ;;
*) logger "ACPI action undefined: $2" ;;
esac
button/sleep)
case "$2" in
SLPB) logger "SleepButton pressed: $2"
/usr/sbin/pm-suspend ;;
*) logger "ACPI action undefined: $2" ;;
esac
ac_adapter)
case "$2" in
AC)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
*) logger "ACPI action undefined: $2" ;;
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000) #echo "offline" >/dev/tty5
00000001) #echo "online" >/dev/tty5
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
#echo "LID switched!">/dev/tty5
logger "ACPI lid switched $1 $2"
if grep -q closed /proc/acpi/button/lid/LID0/state
then
logger "ACPI lid closed"
/usr/sbin/pm-suspend
else
logger "ACPI lid opened"
echo -n 2 > /proc/acpi/video/EGFX/LCD0/brightness
fi
logger "ACPI group/action undefined: $1 / $2"
esac
HTH.

Pm-suspend resumes from suspend, but all other methods don't

Running Arch with xfce. Everything is updated and am on kernal 3.9. Desktop PC, motherboard Gigabyte H61N-USB3 (latest BIOS).
I've been having an issue for a few months with resume not working properly after a suspend. I've tried all sorts of solutions, e.g.:
adding items to my kernal line (hpet=disable, acpi_osi=Linux)
installing acpi, acpid
disabling HPET in the BIOS
editing /etc/mkinitcpio.conf with the resume hook instead of autodetect
installing uswsusp
None worked. Seen a lot of threads here of people having the same issue, but with me, it ALWAYS resumes fine if I suspended with pm-suspend.
If I issue pm-suspend, the computer suspends nicely. I press the power button and everything comes back on. /var/log/pm-suspend.log is always successful.
But, if I use any other method, such as sysctl suspend, or upower, or the suspend option in the Xfce menu (uses xfce4-power-manager), the resume doesn't wake any USB devices (my mouse light stays off) or the monitor (stays in blinking stanby mode). Sometimes it will resume fine, very rarely, but 90% of the time it won't. Only the PC power light will come on but that's it. Even the reset button won't restart the PC. I have to hold the power button for 4 seconds to turn it off.
I'm almost to the point of replacing the motherboard over this as it's driving me up the wall.
pm-suspend (which works great) generates a pm-suspend log. But any of the other methods generate a pm-powersave log. So those other methods must have something in common. I will post the contents later as I'm at work.
I'd like to get the other methods working because if the PC suspends after a set time (through xfce), or if I use the Xfce suspend menu option, I know it won't resume. A workaround would be to make a pm-suspend menu option and some sort of schedule for it to run after a certain idle time, but that's not an answer for the original problem.
Is there any way I can troubleshoot why systemd and other methods don't resume but pm-suspend does resume it fine?
Last edited by nLinked (2013-05-24 13:52:20)

I cleared pm-powersave.log and suspended through the xfce menu > Suspend.
Resume worked fine once.
Suspended again.
Resume worked fine second.
Suspended again, resume didn't work, PC fans on but mouse and display off.
The output of the new pm-suspend.log is here, although it's possible it can't write any errors to the log when resume fails?
http://pastebin.com/ZHDSeG6H

Cannot resume from suspend to ram (fglrx)

Hello,
I have recently installed Catalyst drivers, instead of xf86-video-ati. I have laptop with PowerXPress(Intel/AMD hybrid graphics).
I can't resume after suspend to ram. System freezes with black screen, tty switching doesn't work and I have to shutdown by holding power button.
If I add "nomodeset" to GRUB, X fails to start. xorg.conf generated using "aticonfig --initial". Catalyst driver works fine.
DE/DM: KDE 4/kwin
Graphic cards: Intel HD Graphics 3000; AMD Radeon 7600M.
Laptop: HP pavillion g6 2004er.

Welcome to the forum!
Yes, some Lenovo employees do read and post to this forum. Mark is quite active, and several others post as well. In addition, there are lurkers who just read without making public comments although sometimes they ask the mod team to either gather more information or pass along advice.
However, here are the expectations of their participation from the Welcome message:
These communities have been created to provide a high quality atmosphere in which users of Lenovo products and services may share experiences and expertise. While members from Lenovo may participate at intervals to engage in the discussions and offer advice and suggestions, this forum is not designed as a dedicated and staffed support channel.
The bottom line is there's no guarantee that you will get an answer to a question here directly from Lenovo.
On the other hand, you just might! ;-)
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Jane
2015 X1 Carbon, ThinkPad Slate, T410s, X301, X200 Tablet, T60p, HP TouchPad, iPad Air 2, iPhone 5S, IdeaTab A2107A, Yoga Tablet, Yoga 3 Pro
I am not a Lenovo Employee.
I AM one of those crazy ThinkPad zealots!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!

[SOLVED] Laptop resumes from suspend while lid is still closed

Hi all,
I'm having some weird issue ever since I installed arch on my new laptop (Haswell).
When I put my computer to suspend by closing the lid, all goes well.
But the computer resumes by itself after a while. I have no idea why, WoL is disabled on both ethernet and wifi.
Can someone help figure out what is causing the computer to resume?
For example here is a magic wake up after 1 hour asleep.
Feb 15 00:37:15 jitte systemd[1]: Starting TLP suspend/resume...
Feb 15 00:37:15 jitte tlp[24682]: grep: /sys/devices/platform/dock.?/type: No such file or directory
Feb 15 00:37:15 jitte systemd[1]: Started TLP suspend/resume.
Feb 15 00:37:15 jitte systemd[1]: Starting Sleep.
Feb 15 00:37:15 jitte systemd[1]: Reached target Sleep.
Feb 15 00:37:15 jitte systemd[1]: Starting Suspend...
Feb 15 00:37:15 jitte systemd-sleep[24748]: Suspending system...
Feb 15 00:37:15 jitte kernel: PM: Syncing filesystems ... done.
Feb 15 00:37:15 jitte kernel: PM: Preparing system for mem sleep
Feb 15 00:37:15 jitte kernel: bbswitch: enabling discrete graphics
Feb 15 01:34:26 jitte kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte systemd[1]: Time has been changed
Feb 15 01:34:26 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte kernel: PM: Entering mem sleep
Feb 15 01:34:26 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: suspend
Feb 15 01:34:26 jitte kernel: PM: suspend of devices complete after 220.139 msecs
Feb 15 01:34:26 jitte systemd[607]: Time has been changed
Feb 15 01:34:26 jitte kernel: PM: late suspend of devices complete after 0.115 msecs
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq suspend of devices complete after 66.764 msecs
Feb 15 01:34:26 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 15 01:34:26 jitte kernel: PM: Saving platform NVS memory
Feb 15 01:34:26 jitte kernel: Disabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: CPU 1 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 2 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 3 is now offline
Feb 15 01:34:26 jitte kernel: ACPI: Low-level resume complete
Feb 15 01:34:26 jitte kernel: PM: Restoring platform NVS memory
Feb 15 01:34:26 jitte kernel: Enabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 1
Feb 15 01:34:26 jitte kernel: CPU1 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 2
Feb 15 01:34:26 jitte kernel: CPU2 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 3
Feb 15 01:34:26 jitte kernel: CPU3 is up
Feb 15 01:34:26 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq resume of devices complete after 130.807 msecs
Feb 15 01:34:26 jitte kernel: PM: early resume of devices complete after 0.108 msecs
Feb 15 01:34:26 jitte kernel: i915 0000:00:02.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: irq 57 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: ahci 0000:00:1f.2: setting latency timer to 64
Last edited by jtheoof (2014-03-16 19:15:02)

So here's the update for today: sudo journalctl -amb.
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte systemd-logind[276]: Lid closed.
Feb 25 13:39:00 jitte systemd-logind[276]: Suspending...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleep requested (sleeping: no enabled: yes)
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleeping or disabling...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'sleeping') [37]
Feb 25 13:39:00 jitte dhcpcd[22409]: received SIGTERM from PID 273, stopping
Feb 25 13:39:00 jitte dhcpcd[22409]: wlp2s0: removing interface
Feb 25 13:39:00 jitte dhcpcd[22409]: exited
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 22409
Feb 25 13:39:00 jitte NetworkManager[273]: <info> Removing DNS information from /usr/bin/resolvconf
Feb 25 13:39:00 jitte kernel: wlp2s0: deauthenticating from 00:24:d4:5f:dc:d8 by local choice (reason=3)
Feb 25 13:39:00 jitte kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): taking down device.
Feb 25 13:39:00 jitte NetworkManager[273]: <info> NetworkManager state is now ASLEEP
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): taking down device.
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 25 13:39:00 jitte systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 25 13:39:01 jitte systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 25 13:39:01 jitte gnome-session[1672]: Window manager warning: Log level 16: gsignal.c:2593: instance '0x15b1e20' has no handler with id '468541'
Feb 25 13:39:05 jitte systemd-logind[276]: Delay lock is active but inhibitor timeout is reached.
Feb 25 13:39:05 jitte systemd[1]: Starting Sleep.
Feb 25 13:39:05 jitte systemd[1]: Reached target Sleep.
Feb 25 13:39:05 jitte systemd[1]: Starting Suspend...
Feb 25 13:39:05 jitte systemd-sleep[22893]: Suspending system...
Feb 25 13:39:05 jitte kernel: PM: Syncing filesystems ... done.
Feb 25 13:39:05 jitte kernel: PM: Preparing system for mem sleep
Feb 25 13:39:05 jitte kernel: bbswitch: enabling discrete graphics
Feb 25 17:22:59 jitte kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Feb 25 17:22:59 jitte systemd[1]: Time has been changed
Feb 25 17:22:59 jitte systemd[1666]: Time has been changed
Feb 25 17:22:59 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 25 17:22:59 jitte kernel: PM: Entering mem sleep
Feb 25 17:22:59 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 25 17:22:59 jitte kernel: PM: suspend of devices complete after 1098.028 msecs
Feb 25 17:22:59 jitte kernel: PM: late suspend of devices complete after 0.504 msecs
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq suspend of devices complete after 66.728 msecs
Feb 25 17:22:59 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 25 17:22:59 jitte kernel: PM: Saving platform NVS memory
Feb 25 17:22:59 jitte kernel: Disabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: smpboot: CPU 1 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: smpboot: CPU 2 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: smpboot: CPU 3 is now offline
Feb 25 17:22:59 jitte kernel: ACPI: Low-level resume complete
Feb 25 17:22:59 jitte kernel: PM: Restoring platform NVS memory
Feb 25 17:22:59 jitte kernel: Enabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: x86: Booting SMP configuration:
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 1
Feb 25 17:22:59 jitte kernel: CPU1 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 2
Feb 25 17:22:59 jitte kernel: CPU2 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 3
Feb 25 17:22:59 jitte kernel: CPU3 is up
Feb 25 17:22:59 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq resume of devices complete after 132.766 msecs
Feb 25 17:22:59 jitte systemd[1666]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1666]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Reached target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Reached target Bluetooth.
Feb 25 17:22:59 jitte kernel: PM: early resume of devices complete after 0.347 msecs
Feb 25 17:22:59 jitte kernel: hpet1: lost 2539 rtc interrupts
Feb 25 17:22:59 jitte kernel: mei_me 0000:00:16.0: irq 58 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: usb usb1: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: usb usb2: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: irq 62 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:1b.0: irq 63 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
Feb 25 17:22:59 jitte kernel: PM: Device 00:07 failed to resume: error -19
Feb 25 17:22:59 jitte kernel: usb 3-1: reset high-speed USB device number 2 using ehci-pci
Feb 25 17:22:59 jitte kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: configured for UDMA/133
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Starting disk
Feb 25 17:22:59 jitte kernel: usb 1-5: reset high-speed USB device number 2 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f00
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f40
Feb 25 17:22:59 jitte kernel: usb 1-6: reset full-speed USB device number 3 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143780
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af1437c0
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143800
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0900
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0940
Feb 25 17:22:59 jitte kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Feb 25 17:22:59 jitte kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25300
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25340
Feb 25 17:22:59 jitte kernel: usb 1-7: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
Feb 25 17:22:59 jitte kernel: PM: resume of devices complete after 1355.352 msecs
Feb 25 17:22:59 jitte kernel: PM: Finishing wakeup.
Feb 25 17:22:59 jitte kernel: Restarting tasks ...
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: rtsx_pci 0000:03:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: pci 0000:04:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: done.
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:00: Restoring backlight state
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:01: Restoring backlight state
Feb 25 17:22:59 jitte kernel: bbswitch: disabling discrete graphics
Feb 25 17:22:59 jitte kernel: ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: read Intel version: 370710018002030d00
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Feb 25 17:22:59 jitte bluetoothd[272]: Failed to set mode: Blocked through rfkill (0x12)
Feb 25 17:22:59 jitte systemd-sleep[22893]: System resumed.
Feb 25 17:22:59 jitte systemd[1]: Started Suspend.
Feb 25 17:22:59 jitte systemd[1]: Requested transaction contradicts existing jobs: File exists
Feb 25 17:22:59 jitte systemd[1]: Service sleep.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Stopping Sleep.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Sleep.
Feb 25 17:22:59 jitte systemd[1]: Reached target Suspend.
Feb 25 17:22:59 jitte systemd-logind[276]: Operation finished.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> wake requested (sleeping: yes enabled: yes)
Feb 25 17:22:59 jitte NetworkManager[273]: <info> waking up and re-enabling...
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): bringing up device.
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'managed') [2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> NetworkManager state is now DISCONNECTED
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): bringing up device.
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1 enp3s0f1: link down
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0f1: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): deactivating device (reason 'managed') [2]
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: starting -> ready
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 25 17:23:00 jitte NetworkManager[273]: <warn> Trying to remove a non-existant call id.
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:02 jitte kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
Feb 25 17:23:02 jitte kernel: atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
What's really odd is that the laptop woke up at the exact same time as yesterday. What could be causing that?
I'm using gnome-shell v3.10.3-1, linux-mainline v3.14rc3-1.

Cannot resume from suspend on Asus F5R

Asus F5R laptop
uname -r: 3.1.7-1-ARCH
radeon driver
When using pm-suspend, the computer suspends as it's supposed to do. However, when I try to resume it again, the screen is blank. I can hear the HDD and fans spin up, but the screen is still blank.
pm-suspend.log:
Initial commandline parameters:
Thu Jan 5 00:06:39 CET 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux localhost 3.1.6-1-ARCH #1 SMP PREEMPT Thu Dec 22 08:52:33 UTC 2011 i686 Intel(R) Core(TM) Duo CPU T2450 @ 2.00GHz GenuineIntel GNU/Linux
Module Size Used by
cryptd 6925 0
aes_i586 6940 1
aes_generic 25702 1 aes_i586
ipv6 247457 10
joydev 7439 0
arc4 1086 2
b43 301586 0
mac80211 196411 1 b43
snd_hda_codec_si3054 2866 1
uas 6440 0
usb_storage 35343 0
snd_hda_codec_realtek 211044 1
cfg80211 142604 2 b43,mac80211
bcma 14319 1 b43
radeon 913985 2
ttm 45685 1 radeon
psmouse 56772 0
ssb 41907 1 b43
snd_hda_intel 19293 0
snd_hda_codec 69829 3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 4942 1 snd_hda_codec
snd_pcm 60207 3 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec
drm_kms_helper 22237 1 radeon
ati_agp 4545 0
drm 149266 4 radeon,ttm,drm_kms_helper
agpgart 22287 3 ttm,ati_agp,drm
serio_raw 3390 0
snd_timer 15438 1 snd_pcm
mmc_core 66997 2 b43,ssb
snd 43817 7 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
pcmcia 31534 2 b43,ssb
pcmcia_core 10114 1 pcmcia
atl2 20345 0
soundcore 5018 1 snd
i2c_piix4 7084 0
snd_page_alloc 5869 2 snd_hda_intel,snd_pcm
videodev 77028 0
media 8609 1 videodev
asus_laptop 11994 0
i2c_algo_bit 4423 1 radeon
sp5100_tco 3760 0
sparse_keymap 2660 1 asus_laptop
evdev 7278 7
shpchp 22497 0
pci_hotplug 22072 1 shpchp
processor 21844 2
i2c_core 16816 6 radeon,drm_kms_helper,drm,i2c_piix4,videodev,i2c_algo_bit
rfkill 12470 2 cfg80211,asus_laptop
thermal 6531 0
pcspkr 1375 0
button 3614 0
battery 5053 0
ac 1796 0
video 9716 0
ext4 341420 1
mbcache 4281 1 ext4
jbd2 59633 1 ext4
crc16 1091 1 ext4
sr_mod 13244 0
cdrom 31405 1 sr_mod
sd_mod 26147 3
pata_acpi 2388 0
ahci 17497 2
libahci 16783 1 ahci
pata_atiixp 2920 0
libata 146596 4 pata_acpi,ahci,libahci,pata_atiixp
ohci_hcd 19226 0
ehci_hcd 36074 0
scsi_mod 112473 5 uas,usb_storage,sr_mod,sd_mod,libata
usbcore 120796 5 uas,usb_storage,ohci_hcd,ehci_hcd
total used free shared buffers cached
Mem: 1935344 628024 1307320 0 46344 285940
-/+ buffers/cache: 295740 1639604
Swap: 1048508 0 1048508
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/91wicd suspend suspend:
/usr/lib/pm-utils/sleep.d/91wicd suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Jan 5 00:06:47 CET 2012: performing suspend
dmesg | grep Hibernation (both with and without resume hook enabled):
[ 0.928657] PM: Hibernation image not present or could not be loaded.
So far I've tried passing hpet=disable to the kernel and rebuilding the initramfs with resume hook, all to no avail.
If you need any more info for helping me, please let me know.
PS.
I've viewed all other threads as well, but they're not relevant to me.
PPS.
Resuming has never worked on this laptop, so it's not related to my current kernel version.
Last edited by snufkin (2012-01-07 15:27:29)

Ok, thats bad luck really. Further bits to try:
Have you followed this about vbe tool as well?
How about these bits about acpi also. Maybe you should try that with the LTS kernel.
Further (wild guess) S3 kernel options perhaps to try still (see here?
How about a bios update? asus does such often.

Exchange 2010: New Mailboxes cannot receive external email, but internal works fine. Existing Mailboxes are working properly.

Hello,
I can't seem to figure out what the problem is, but my new mailboxes cannot receive external email. The sender receives an NDR stating the following:
The error that the other server returned was: 550 550 No such user - psmtp (state 13).
Internally, the affected mailboxes can send and receive mail, and the mailboxes have no trouble sending mail out of the organization. I do not see an anti-spam solution installed on the exchange server, and I have confirmed that DNS resolved to the WAN IP
of this server.
Can anyone help me? The message tracker didn't appear to have recorded the NDR's that it sent, but it's possible I didn't view the logs correctly.
Thank you!
Paul
My environment contains two servers:
Server A: Domain Controller, Server 2008 R2, Exchange 2010 Standard
Server B: Domain Controller, Server 2008 R2

On Wed, 30 May 2012 02:01:19 +0000, Relion Support Inc wrote:
>
>
>Hello,
>
>
>
>I can't seem to figure out what the problem is, but my new mailboxes cannot receive external email. The sender receives an NDR stating the following:
>
>The error that the other server returned was: 550 550 No such user - psmtp (state 13).
>
>
>
>Internally, the affected mailboxes can send and receive mail, and the mailboxes have no trouble sending mail out of the organization. I do not see an anti-spam solution installed on the exchange server, and I have confirmed that DNS resolved to the WAN
IP of this server.
>
>
>
>Can anyone help me? The message tracker didn't appear to have recorded the NDR's that it sent, but it's possible I didn't view the logs correctly.
Is your Exchange server exposed to the Internet or do you have some
3rd-party device that does spam filtering? If you have something out
in front of Exchange that only periodically refreshes its cache of
valid SMTP addresses from the AD then you need to adjust the refresh
rate.
That "550 No such user" isn't a status code that Exchange returned.
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

[SOLVED] Failure when loading modules, but everything works fine

I've updated Linux from 2.6 to 3.0, everything seems to be working as before, but I'm getting this when booting:
Loading modules [FAIL]
I don't see anything relevant in dmesg output, everything seems to be loaded fine. Is anybody else getting the same error since the kernel update?
Last edited by Camus (2011-08-08 14:07:56)

What's strange is that Tp smapi's functionality seems to be there anyway... It's a module for battery control in Thinkpads and my battery indeed doesn't charge beyond 80%, the way I want it to be.
I'm having the same issue. I think you will find that the "functionality" isn't provided, as you said, /sys/devices/platform/smapi doesn't exist, and that your battery is actually remembering the last charge limits you sent to it. Try to remove the battery and put it back, I'm nearly sure that it'll lose them. This is what happens to me on my second battery, the ultra-bay one, which I occasionally have to remove to insert my CD drive.
No idea why tp_smapi doesn't load when put in MODULES in rc.conf, but workarounds should be easy. Alternatively, if you only use it to update your charge settings, you can just manually load it each time you need to.
EDIT :
Have just found out that by manually adding thinkpad_ec before tp_smapi in MODULES in rc.conf, everything loads. Strange, since thinkpad_ec should be loaded automatically with tp_smapi. But hey, it works.
Last edited by idx (2011-08-19 11:08:08)

System freeze after resume from suspend to RAM

Hi,
since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
kernel: sas: trying to find task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
kernel: sas: trying to find task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
kernel: sas: ata7: end_device-0:0: cmd error handler
kernel: sas: ata8: end_device-0:1: cmd error handler
kernel: sas: ata7: end_device-0:0: dev error handler
kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
kernel: ata7.00: status { DRDY }
kernel: ata7: hard resetting link
kernel: sas: ata8: end_device-0:1: dev error handler
kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
kernel: ata8.00: status { DRDY }
kernel: ata8: hard resetting link
This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
Here's my setup:
$ lsblk -St
NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Recovery 567437B974379B27
├─sda2 vfat DC2D-099E /boot
├─sda3
├─sda4 ntfs FEBED982BED933BD
├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
└─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
sdb
└─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
sdc
└─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
sdd
└─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
Any ideas on how I could narrow down this issue? Thanks a lot!
EDIT
I just checked and confirmed that this issue is originating from the OCZ Revodrive:
$ dmesg | grep ata7.00 | head
[ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.146442] ata7.00: configured for UDMA/133
$ dmesg | grep ata8.00 | head
[ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.320022] ata8.00: configured for UDMA/133
Last edited by tuttiarch (2015-01-31 15:54:29)

Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

System freeze after resume from suspend

I am running arch for about 5 month now and I always had freezes after resuming from suspend (to ram - systemctl suspend) every once in a while (like once a week or less). The freezes increased massively over the last month or so and for about 2 weeks now it happens 95% of the times I resume from suspend.
The monitor turns on and shows things exactly how I left them, but is completely unresponsible EXCEPT for I can switch to another TTY (Ctrl+Shift+F*), however I cannot type or do anything in it...
It doesnt have anything to do with the X server as it also happens after I suspend from TTY (without any X running).
I also checked journalctl -b -1 (shows previous boot, since I always have to hard-reset the system) but it doesnt show anything after:
Mar 13 17:16:54 Ununhaswellium systemd-sleep[3624]: Suspending system...
(the suspend event before resuming)
Are there any log files that could give a hint on what exactly goes on after the resume?
Im running the latest official 3.13.6-1 kernel and updated my BIOS to the latest beta version yesterday - didnt help either...
Ive read pretty much every thread on the internet by now about freezes after resume from suspend but none really helped
Last edited by CharlieBra7o (2014-03-15 09:58:51)

Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

Office 2013 - Word cannot establish a connection with this document after the system resumed from suspend mode

Hiya!
This issue has been answered numerous times for Office 2010 and Office 2007, but I have yet to any solutions or Hotfixes that work for Office 2013 (x64) on Win7.
How to replicate the issue:
Open a file from a network share.
Edit file.
Leave computer on with file open. Computer goes to sleep or into stand-by mode.
Wait a bit
Wake up computer
CPU opens file in Read-Only mode and gives you the following error "Word cannot establish a network connection with this document after the system resumed from suspend mode. Save the document into a different file to keep any changes."
What I've tried:
http://support.microsoft.com/kb/2434898 - Office 2007 registry fixes. Does not apply.
http://support.microsoft.com/kb/2413659 - Office 2010 problem. This exact issue. Says 'No microsoft products that match this hotfix are installed'
Work Around:
I can saving new versions of these files overrides this issue, but this is sometimes not possible for end-users who only have specific access to ONE SPECIFIC FILE in a particular network share.
Please let me know how I can alleviate this issue!
Thanks
-Chris

Hi,
Are those problematic documents created via previous versions of Office?
Please also try to run a repair of your Office 2013 installtion and check if it helps. See:
http://office.microsoft.com/en-in/excel-help/repair-office-programs-HA010357402.aspx
Regards,
Steve Fan
TechNet Community Support

[SOLVED] Cannot resume from suspend but hibernate works fine

Similar Messages

Maybe you are looking for