Desktop and S3 suspend the Holy Grail of ACPI?

I am new to ACPI but I have searched the archives, looked at the MAN pages used Google to the best of
my abilities and I still have some questions about ACPI. My basic goal is to be able
to suspend my desktop machine to S3 when not in use. I need to use the machine several times throughout the day, and feel it is a waste to leave it on continuously. The system spec are: Intel D875PBZ, Intel P4 3GHZ, Radeonm 9700 pro, Sounblaster Live, Debian unstable with 2.4.23 and 2.6.2 kernels available, both with ACPI compiled as modules. Pressing the power button once gracefully shuts down the machine running either kernel.

After reading the documentation, I am still not sure how to try to suspend to S3. Is there anyone with this motherboard succesfully using S3 suspend? Is it reliable and stable, suspend after suspend. Is S3 suspend with Linux on the desktop the Holy Grail of ACPI? The machines suspends to S3 in Windows 2000 Pro, also shuts all the fans down too, totally silent.

Any advice would be appreciated.
Can anyone recommend any Pentium 3/4 desktop motherboard that will S3 reliably in Linux?

If this is not possible yet, are there any other Linux hardware problems where S3 works reliably?

There is at least one problem for which I don't think that you will have S3 working even in the near future.
You do have a radeon 9700 and due to lack of supports by ATI those days, I don't see how a developper can include power management codes in any drivers other than by a cycle of guess, then try and guess again what happens on errors.
Note that S3 may work though if you do not have AGPGART compiled, and you do not use any kind of binary-only drm drivers from ATI.

Cheers,

Quoted 10 lines · Bruno Ducrot

There is at least one problem for which I don't think that you will have S3 working even in the near future.
You do have a radeon 9700 and due to lack of supports by ATI those days, I don't see how a developper can include power management codes in any drivers other than by a cycle of guess, then try and guess again what happens on errors.
Note that S3 may work though if you do not have AGPGART compiled, and you do not use any kind of binary-only drm drivers from ATI.

Quoted 4 lines

Cheers,

Would an older ATI card, like a Rage 128 Pro or original Radeon (7000 I believe) work?

I am new to ACPI but I have searched the archives, looked at the MAN pages used Google to the best of
my abilities and I still have some questions about ACPI. My basic goal is to be able
to suspend my desktop machine to S3 when not in use. I need to use the machine several times throughout the day, and feel it is a waste to leave it on continuously. The system spec are: Intel D875PBZ, Intel P4 3GHZ, Radeonm 9700 pro, Sounblaster Live, Debian unstable with 2.4.23 and 2.6.2 kernels available, both with ACPI compiled as modules. Pressing the power button once gracefully shuts down the machine running either kernel.

After reading the documentation, I am still not sure how to try to suspend to S3. Is there anyone with this motherboard succesfully using S3 suspend? Is it reliable and stable, suspend after suspend. Is S3 suspend with Linux on the desktop the Holy Grail of ACPI? The machines suspends to S3 in Windows 2000 Pro, also shuts all the fans down too, totally silent.

Any advice would be appreciated.
Can anyone recommend any Pentium 3/4 desktop motherboard that will S3 reliably in Linux?

If this is not possible yet, are there any other Linux hardware problems where S3 works reliably?

Quoted 2 lines

I've got a laptop running Fedora Core 2 out of the box, and all I do is

# echo 3 >/proc/acpi/sleep
and I use the power button to wake it up.

I've also got a D875PBZ, however

[[email protected] /]# echo -n 3 >/proc/acpi/sleep Stopping tasks: ==============================
stopping tasks failed (1 tasks remaining)
Restarting tasks...<6> Strange, katad-1 not stopped done
[[email protected] /]#

which I guess is due to its SATA boot drive.
Do you have a regular PATA drive?

cheers,
-Len

Quoted 1 line

...D875PBZ...

Quoted 3 lines

Quoted 3 lines

...D875PBZ...

On this box S1 works for me, but S3 doesn't resume (below)

Note that you need to enable S3 in the BIOS SETUP to try S3.

Note that neither S1 nor S3 will do anything on the SMP kernel. (and unfortunately, they will not even tell you that when you try)

-Len

BIOS SETUP: Power/ACPI
ACPI Suspend State [S3 State] (default is S1)

boot FC2-test1 UP kernel

# cat /proc/acpi/sleep
S0 S1 S3 S4 S5

# /etc/init.d/acpid stop
(to make power button resume event not initiate a shut-down)

# echo 1 >/proc/acpi/sleep
Stopping tasks: ================================|
psmouse.c: bad data from KBC - timeout bad parity
hdc: start_power_step(step: 0)
hdc: completing PM request, suspend
hda: start_power_step(step: 0)
hda: start_power_step(step: 1)
hda: complete_power_step(step: 1, stat: 50, err: 0)
hda: completing PM request, suspend
psmouse.c: bad data from KBC - timeout bad parity
psmouse.c: bad data from KBC - timeout bad parity
PM: Entering state.
i8042.c: Can't restore CTR.

<press power button here to resume>

Back to C!
i8042.c: Can't read CTR while initializing i8042.
i8042: resume failed
PM: Finishing up.
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.1 to 64
PCI: Setting latency timer of device 0000:00:1d.2 to 64
PCI: Setting latency timer of device 0000:00:1d.3 to 64
hda: Wakeup request inited, waiting for !BSY...
hda: start_power_step(step: 1000)
e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex
blk: queue f7dcb5c0, I/O limit 4095Mb (mask 0xffffffff)
hda: completing PM request, resume
hdc: Wakeup request inited, waiting for !BSY...
hdc: start_power_step(step: 1000)
hdc: completing PM request, resume
Restarting tasks... done
#

system running normally here.

now try S3:

# echo 3 >/proc/acpi/sleep
Stopping tasks: =================================|
hdc: start_power_step(step: 0)
hdc: completing PM request, suspend
hda: start_power_step(step: 0)
hda: start_power_step(step: 1)
hda: complete_power_step(step: 1, stat: 50, err: 0)
hda: completing PM request, suspend
PM: Entering state.

<power is off, press power button here to wake up system>

here a bunch of garbled junk comes out my serial console. But video is not restored to my matrox mystique FB. ping doesn't work.

Curiously CTRL-ALT-DEL results in the following on the serial console:

quotaoff: numerical sysctl 5 16 8 is obsolete.
md: stopping all md devices.
md: md0 switched to read-only mode.
Restarting system.

<and the system reboots here>

So it seems that the system did resume and talk to the keyboard at least...

I am new to ACPI but I have searched the archives, looked at the MAN pages used Google to the best of
my abilities and I still have some questions about ACPI. My basic goal is to be able
to suspend my desktop machine to S3 when not in use. I need to use the machine several times throughout the day, and feel it is a waste to leave it on continuously. The system spec are: Intel D875PBZ, Intel P4 3GHZ, Radeonm 9700 pro, Sounblaster Live, Debian unstable with 2.4.23 and 2.6.2 kernels available, both with ACPI compiled as modules. Pressing the power button once gracefully shuts down the machine running either kernel.

Hi!

Quoted 10 lines

I am new to ACPI but I have searched the archives, looked at the MAN pages used Google to the best of my abilities and I still have some questions about ACPI. My basic goal is to be able to suspend my desktop machine to S3 when not in use. I need to use the
machine several times throughout the day, and feel it is a waste to leave
it on continuously. The system spec are: Intel D875PBZ, Intel P4 3GHZ,
Radeonm 9700 pro, Sounblaster Live, Debian unstable with 2.4.23 and
2.6.2 kernels available, both with ACPI compiled as modules. Pressing
the power button once gracefully shuts down the machine running either kernel.

Try getting suspend-to-disk working, first.
Pavel

Quoted 14 lines

Quoted 13 lines

I am new to ACPI but I have searched the archives, looked at the MAN pages used Google to the best of
my abilities and I still have some questions about ACPI. My basic goal is to be able
to suspend my desktop machine to S3 when not in use. I need to use the machine several times throughout the day, and feel it is a waste to leave it on continuously. The system spec are: Intel D875PBZ, Intel P4 3GHZ, Radeonm 9700 pro, Sounblaster Live, Debian unstable with 2.4.23 and 2.6.2 kernels available, both with ACPI compiled as modules. Pressing the power button once gracefully shuts down the machine running either kernel.

Quoted 1 line

Try getting suspend-to-disk working, first.

I am assuming your terse response is meant to imply that swsusp would be a better alternative to S3?

I tried playing with suspend to disk in kernel 2.6.3. It was a no go. I have highmem enabled on this machine which has 1 gig of RAM. Going to try pmdisk.

Hi!

Quoted 12 lines

Quoted 12 lines

Quoted 12 lines

I am new to ACPI but I have searched the archives, looked at the MAN pages used Google to the best of my abilities and I still have some questions about ACPI. My basic goal is to be able to suspend my desktop machine to S3 when not in use. I need to use the
machine several times throughout the day, and feel it is a waste to leave
it on continuously. The system spec are: Intel D875PBZ, Intel P4 3GHZ,
Radeonm 9700 pro, Sounblaster Live, Debian unstable with 2.4.23 and
2.6.2 kernels available, both with ACPI compiled as modules. Pressing
the power button once gracefully shuts down the machine running either kernel.

Quoted 9 lines

Quoted 3 lines

Try getting suspend-to-disk working, first.

I am assuming your terse response is meant to imply that swsusp would be a better alternative to S3?

I mean that swsusp is easier to make going than S3, and it is quite usefull to know if it works for you. If it does not, its unlikely that S3 will.

Quoted 4 lines

I tried playing with suspend to disk in kernel 2.6.3. It was a no go. I have highmem enabled on this machine which has 1 gig of RAM. Going to try pmdisk.

Forget pmdisk, that will not work anyway. Try running without highmem (at least for a test).
Pavel

Quoted 8 lines

Quoted 5 lines

I tried playing with suspend to disk in kernel 2.6.3. It was a no go. I have highmem enabled on this machine which has 1 gig of RAM. Going to try pmdisk.

Forget pmdisk, that will not work anyway. Try running without highmem (at least for a test).

Should I also disable preemption?

Quoted 6 lines

Quoted 6 lines

Quoted 5 lines

I tried playing with suspend to disk in kernel 2.6.3. It was a no go. I have highmem enabled on this machine which has 1 gig of RAM. Going to try pmdisk.

Quoted 4 lines

Quoted 2 lines

Forget pmdisk, that will not work anyway. Try running without highmem (at least for a test).

Should I also disable preemption?

Yes.

Quoted 6 lines

Quoted 6 lines

Quoted 6 lines

Quoted 5 lines

I tried playing with suspend to disk in kernel 2.6.3. It was a no go. I have highmem enabled on this machine which has 1 gig of RAM. Going to try pmdisk.

Quoted 6 lines

Quoted 4 lines

Quoted 2 lines

Forget pmdisk, that will not work anyway. Try running without highmem (at least for a test).

Should I also disable preemption?

Yes.

WHY???

Hi!

Quoted 10 lines

Quoted 10 lines

Quoted 6 lines

I tried playing with suspend to disk in kernel 2.6.3. It was a no go. I have highmem enabled on this machine which has 1 gig of RAM. Going to try pmdisk.

Forget pmdisk, that will not work anyway. Try running without highmem (at least for a test).

Quoted 3 lines

Should I also disable preemption?

Yes.
Pavel

Quoted 3 lines

Quoted 1 line

Should I also disable preemption?

Yes.

Pavel, I'm having some trouble understanding the swsusp.txt file. It
states: " You must explicitly specify the swap partition to resume from with ``resume='' kernel option."

my swap partition resides in /dev/hda4

So I think I need to do something like this?
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
label=Linux
read-only
append="hda=autotune resume=/dev/hda4" <---- added this
# restricted
# alias=1

Is this correct, or do i pass the resume option at boot time as a LILO option?

Hi!

Quoted 26 lines

Quoted 6 lines

Quoted 3 lines

Should I also disable preemption?

Yes.

Pavel, I'm having some trouble understanding the swsusp.txt file. It states: " You must explicitly specify the swap partition to resume from with ``resume='' kernel option."

my swap partition resides in /dev/hda4

So I think I need to do something like this?
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
label=Linux
read-only
append="hda=autotune resume=/dev/hda4" <---- added this
# restricted
# alias=1

Quoted 3 lines

Is this correct, or do i pass the resume option at boot time as a LILO option?

It is correct.
Pavel

As a test I suspened the machine twice; each time the machine was off for approximately 5 minutes. It resumed twice without any problems (into X with a mozilla and xmms)
As another test, I opned up a few apps in different workspaces: abiword with a document, mozilla browser and mail, xmms playing an internet stream. I then suspended in hopes of resuming the next day after school. After about 14hrs I tried to resume, and everything seemed fine, excpet my USB mouse was unrespnsive. I was able to brinx X down into a working console, startx again, but still no mouse.

In debian kernel 2.6.3 I have the NIC and USB options compiled in. Should these be modules that are removed before swsusp? There's aslo mention of a swsusp script, but was unable to find one in ../Documentation/power or via apt-cache search; I'm assuming that I need this script, which will remove the modules before swsusp and modprobe them after resume.

Hi!

Quoted 7 lines

As a test I suspened the machine twice; each time the machine was off for approximately 5 minutes. It resumed twice without any problems (into X with a mozilla and xmms)
As another test, I opned up a few apps in different workspaces: abiword with a document, mozilla browser and mail, xmms playing an internet stream. I then suspended in hopes of resuming the next day after school. After about 14hrs I tried to resume, and everything seemed fine, excpet my USB mouse was unrespnsive. I was able to brinx X down into a working console, startx again, but still no mouse.

In debian kernel 2.6.3 I have the NIC and USB options compiled in. Should these be modules that are removed before swsusp?
There's aslo mention of a swsusp script, but was unable to find one in ../Documentation/power or via apt-cache search; I'm assuming that I need this script, which will remove the modules before swsusp and modprobe them after resume.

You should not need any script; but it probably has better chance working with USB modules removed. Anyway that's a bug in USB support, ask on USB list.

Pavel

So if there's anything you guys -- who have been more than helpful btw -- would like me to try as far as getting S3 functional, I'm all ears. I'm also assuming I need some kind of script for S4 to unload the USB and NIC modules, stop acpid, then revers all that upon resume. Is this something I'm going to have to write myself?

Hi!

Quoted 5 lines

So if there's anything you guys -- who have been more than helpful btw
-- would like me to try as far as getting S3 functional, I'm all ears.
I'm also assuming I need some kind of script for S4 to unload the USB and NIC modules, stop acpid, then revers all that upon resume. Is this something I'm going to have to write myself?

Well, ideally you should not workaround e1000/usb problems with scripts, but add driver model support to both of those.

You may want to try S3 with those two modules unloaded. There's some chance it resumes with video not working (you can tell by typing find / -- if hdd starts flashing, machine is okay but no video).
Pavel