Take a look at our
ThinkPads.com HOME PAGE
For those who might want to contribute to the blog, start here: Editors Alley Topic
Then contact Bill with a Private Message
ThinkPads.com HOME PAGE
For those who might want to contribute to the blog, start here: Editors Alley Topic
Then contact Bill with a Private Message
Suspend to RAM problem
Suspend to RAM problem
Hello!
I have a new Thinkpad R50e (UROSYxx, 1834SYG) with a fresh Suse Linux 9.3 and XP Home on it. I'm trying to set up the suspend to RAM mode on linux. The system has ACPI and ibm-acpi package of course, but it still doesn't work. I had set the Power management in Yast and follow the instructions on thinkwiki.org about ACPI and suspend to ram. When i close the the lid it goes to Suspend mode but after that when i open, it shows:
"Stopping Tasks:================"
and doesn't respond to anything (i can't switch to console mode, either), i can only shut down it by pushing the main shut-down button. I have been searcing for the correct proved solution for 4 hours now, but still no results. Any ideas?
I have a new Thinkpad R50e (UROSYxx, 1834SYG) with a fresh Suse Linux 9.3 and XP Home on it. I'm trying to set up the suspend to RAM mode on linux. The system has ACPI and ibm-acpi package of course, but it still doesn't work. I had set the Power management in Yast and follow the instructions on thinkwiki.org about ACPI and suspend to ram. When i close the the lid it goes to Suspend mode but after that when i open, it shows:
"Stopping Tasks:================"
and doesn't respond to anything (i can't switch to console mode, either), i can only shut down it by pushing the main shut-down button. I have been searcing for the correct proved solution for 4 hours now, but still no results. Any ideas?
Looks like something with the ACPI system is waiting for an event that never happens. I spent a long time on a similar issue with my Thinkpad 600X. See http://bugzilla.kernel.org/show_bug.cgi?id=5989 and then lots of further emails on the linux-acpi mailling list.
Some things to try to perhaps debug it are:
1. unload as many modules as possible and see if it still hangs. In the old days (six months ago), I had to unload usb_uhci though it now suspends fine. Other likely culprits are network-interface drivers, though in my case they don't prevent the sleep/wake, they just return in a mangled state.
2. Try suspending without closing the lid, so you can see what's going on:
3. In combination with 2, turn on ACPI debugging to give an idea of what stage in the sleep it's hanging in:
then try #2 above.
4. Capture the debugging output across a serial console.
5. Did it ever work? Try a more recent kernel. Lots of ACPI bugs are fixed in each one. Perhaps try this change before anything else. You didn't say what kernel you are using.
5. The linux-acpi list was very helpful for me, and they want to make ACPI work as well as possible in Linux. People there will probably want to know at least:
a. Kernel version
b. ACPI-related message at boot: e.g.
c. Does it hang when you do or only when you close the lid? What steps does the lid-closing do?
-Sanjoy
Some things to try to perhaps debug it are:
1. unload as many modules as possible and see if it still hangs. In the old days (six months ago), I had to unload usb_uhci though it now suspends fine. Other likely culprits are network-interface drivers, though in my case they don't prevent the sleep/wake, they just return in a mangled state.
2. Try suspending without closing the lid, so you can see what's going on:
Code: Select all
echo mem > /sys/power/state
Code: Select all
echo 0x10 > /proc/acpi/debug_level
echo 0x10 > /proc/acpi/debug_layer
4. Capture the debugging output across a serial console.
5. Did it ever work? Try a more recent kernel. Lots of ACPI bugs are fixed in each one. Perhaps try this change before anything else. You didn't say what kernel you are using.
5. The linux-acpi list was very helpful for me, and they want to make ACPI work as well as possible in Linux. People there will probably want to know at least:
a. Kernel version
b. ACPI-related message at boot: e.g.
Code: Select all
dmesg | grep ACPI
Code: Select all
echo mem > /sys/power/state"
-Sanjoy
Sorry to hi-jack this thread, but I have a problem with suspend-to-ram on my new ThinkPad T60 as well. I get the following:
# echo mem > /sys/power/state
bash: echo: write error: Operation not permitted
The device is there:
# ls -al /sys/power/state
-rw-r--r-- 1 root root 0 2006-05-20 11:27 /sys/power/state
# cat /sys/power/state
standby mem
This is with a 2.6.16 kernel:
# uname -a
Linux io 2.6.16 #1 SMP PREEMPT Mon May 8 21:16:54 CEST 2006 i686 GNU/Linux
I have not found a solution to that problem yet. Anybody any ideas?
# echo mem > /sys/power/state
bash: echo: write error: Operation not permitted
The device is there:
# ls -al /sys/power/state
-rw-r--r-- 1 root root 0 2006-05-20 11:27 /sys/power/state
# cat /sys/power/state
standby mem
This is with a 2.6.16 kernel:
# uname -a
Linux io 2.6.16 #1 SMP PREEMPT Mon May 8 21:16:54 CEST 2006 i686 GNU/Linux
I have not found a solution to that problem yet. Anybody any ideas?
Just some additional info:
1. make sure the ACPI code on your R50e doesn't need fix
Ref. http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
2. hang when suspending offten indicates that you try to force to remove a kernel module which is in use or some kernel built-in drivers don't like to be disconnected. Try to recompile your kernel and build all the drivers into modules. Then after the new kernel is installed, remove all the modules (remember the order) and try suspend when there is no modules on the system and see how it goes.
sbellon: Check if you have sysfs mounted. You might need to recompile the kernel to have sysfs support. Try # cat /proc/mounts and see if sysfs is there.
1. make sure the ACPI code on your R50e doesn't need fix
Ref. http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
2. hang when suspending offten indicates that you try to force to remove a kernel module which is in use or some kernel built-in drivers don't like to be disconnected. Try to recompile your kernel and build all the drivers into modules. Then after the new kernel is installed, remove all the modules (remember the order) and try suspend when there is no modules on the system and see how it goes.
sbellon: Check if you have sysfs mounted. You might need to recompile the kernel to have sysfs support. Try # cat /proc/mounts and see if sysfs is there.
hotpluggable CPUs needed for suspend on core duo
I had this same problem on my Thinkpad T60p with 2.6.16 FC5:
# echo mem > /sys/power/state
bash: echo: write error: Operation not permitted
This didn't happen with the stock kernel, but only after I had
customized it for the machine. So I went back to the stock version
and selectively made sets of changes to the config until I narrowed
it down to a single option that made the difference:
Hotpluggable CPUs.
This is listed as an experimental option, but it appears to be
necessary to get suspend to work with the Core Duo.
I'm guessing the second CPU needs to be shutdown as
if it were unplugged prior to suspending.
Unfortunately, upon returning from suspend my machine locks up,
which I think is the SATA problem. So I'm on to finding what patches
I need to fix that next...
# echo mem > /sys/power/state
bash: echo: write error: Operation not permitted
This didn't happen with the stock kernel, but only after I had
customized it for the machine. So I went back to the stock version
and selectively made sets of changes to the config until I narrowed
it down to a single option that made the difference:
Hotpluggable CPUs.
This is listed as an experimental option, but it appears to be
necessary to get suspend to work with the Core Duo.
I'm guessing the second CPU needs to be shutdown as
if it were unplugged prior to suspending.
Unfortunately, upon returning from suspend my machine locks up,
which I think is the SATA problem. So I'm on to finding what patches
I need to fix that next...
Standby.
Great. The hotplug CPU helped. This was only problem in my case. I do not observer the problem with the SATA after resuming. I know that there was problem with the SATA in older kernels - 2.6.12 - and special SATA patch was needed, but with the recent 2.6.17 I have no problem with the SATA at all.
Hi. I have a problem with ArchLinux and IBM R50e (suspend-to-ram).
I use this script:
And i use kde with Xorg 7.0.
Then notebook go to sleep well, but he can't wake-up. Notebook power "on", but display and usb don't wake-up.
What I can doing?
Thanks.
I use this script:
Code: Select all
#!/bin/sh
# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0
# remove USB 1.1 driver
rmmod uhci_hcd
touch /root/video_state
cat /proc/bus/pci/00/02.0 > /root/video_state
# sync filesystem and clock
/opt/kde/bin/dcop --all-users --all-sessions kdesktop KScreensaverIface lock
sync
/sbin/hwclock --systohc
FGCONSOLE=`fgconsole`
chvt 6
# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state
/sbin/hwclock --adjust
/sbin/hwclock --hctosys
modprobe uhci_hcd
cat /root/video_state > /proc/bus/pci/00/02.0
echo -n "lcd_enable" > /proc/acpi/ibm/video
chvt $FGCONSOLE
rm /root/video_state
Then notebook go to sleep well, but he can't wake-up. Notebook power "on", but display and usb don't wake-up.
What I can doing?
Thanks.
What driver do you use? The one from X.org or propietary from ATI? I am using ATI and there is no problem with that drivers and also OpenGL is running fine ...
Malcolm wrote:Hi. I have a problem with ArchLinux and IBM R50e (suspend-to-ram).
I use this script:And i use kde with Xorg 7.0.Code: Select all
#!/bin/sh # if launched through a lid event and lid is open, do nothing echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0 # remove USB 1.1 driver rmmod uhci_hcd touch /root/video_state cat /proc/bus/pci/00/02.0 > /root/video_state # sync filesystem and clock /opt/kde/bin/dcop --all-users --all-sessions kdesktop KScreensaverIface lock sync /sbin/hwclock --systohc FGCONSOLE=`fgconsole` chvt 6 # go to sleep sleep 5 && echo -n "mem" > /sys/power/state /sbin/hwclock --adjust /sbin/hwclock --hctosys modprobe uhci_hcd cat /root/video_state > /proc/bus/pci/00/02.0 echo -n "lcd_enable" > /proc/acpi/ibm/video chvt $FGCONSOLE rm /root/video_state
Then notebook go to sleep well, but he can't wake-up. Notebook power "on", but display and usb don't wake-up.
What I can doing?
Thanks.
I use xf-video-i810 package, i810 driver. In my notebook integrated video card. 852GM/855GMwalkerd wrote:What driver do you use? The one from X.org or propietary from ATI? I am using ATI and there is no problem with that drivers and also OpenGL is running fine ...
that my section in xorg.conf
Code: Select all
Section "Device"
Identifier "Card0"
Driver "i810"
BusID "PCI:0:2:0"
VendorName "All"
BoardName "All"
Option "VBERestore" "true"
EndSection
daemons: bluetooth network netfs crond alsa powersaved laptop-mode kdm cpufreqd
Aha, this is intel, with this kind card I have no experience
sorry.
Jozef

Jozef
Malcolm wrote:I use xf-video-i810 package, i810 driver. In my notebook integrated video card. 852GM/855GMwalkerd wrote:What driver do you use? The one from X.org or propietary from ATI? I am using ATI and there is no problem with that drivers and also OpenGL is running fine ...
that my section in xorg.conf
Archlinux, 2.6.16-beyond, modules: nvram i810 speedstep_centrino cpufreq_conservative ibm_acpiCode: Select all
Section "Device" Identifier "Card0" Driver "i810" BusID "PCI:0:2:0" VendorName "All" BoardName "All" Option "VBERestore" "true" EndSection
daemons: bluetooth network netfs crond alsa powersaved laptop-mode kdm cpufreqd
I still have the SATA resume problem after suspending to RAM, even with the latest 2.6.18 kernel. Would any kind soul who got it working please mind posting their output of
# grep "CONFIG_SCSI_[SP]\?ATA" /usr/src/linux/.config
?
I suspect it's just a wrong kernel configuration setting, perhaps even only a "module instead of builtin" or vice versa problem. Thanks a lot!
# grep "CONFIG_SCSI_[SP]\?ATA" /usr/src/linux/.config
?
I suspect it's just a wrong kernel configuration setting, perhaps even only a "module instead of builtin" or vice versa problem. Thanks a lot!
-
- Similar Topics
- Replies
- Views
- Last post
-
-
W510: What is the maximum RAM supported? And what type of RAM?
by favonian » Thu Jun 02, 2022 9:38 am » in ThinkPad W500/W510/W520 and W700/W701 Series - 1 Replies
- 642 Views
-
Last post by SAIYAN48
Thu Jun 02, 2022 5:21 pm
-
-
-
W500 RAM upgrade problem
by Marto181 » Fri Feb 04, 2022 9:45 am » in ThinkPad W500/W510/W520 and W700/W701 Series - 1 Replies
- 1361 Views
-
Last post by jldr_2
Wed Feb 16, 2022 1:11 am
-
-
-
X61 weird RAM problem
by CPC464 » Sun Feb 27, 2022 7:09 am » in Thinkpad X60/X61 Series incl. Tablets - 4 Replies
- 1097 Views
-
Last post by CPC464
Mon Feb 28, 2022 6:30 am
-
-
-
T25 can take ANY T470 motherboard and 64GB RAM
by RealBlackStuff » Fri Jan 14, 2022 2:07 am » in Thinkpad T25 Anniversary/Retro - 3 Replies
- 4069 Views
-
Last post by mikemex
Fri Jan 14, 2022 11:54 pm
-
Who is online
Users browsing this forum: No registered users and 9 guests