Skip to contentSkip to conversation

Q: swsusp with S5 instead of S4?

DISCUSSION Pavel Machek 2 participants 3 messages May 2, 2005 – May 30, 2005

lore
Share & tools
lore
#0 lore raw

[now cc-ed l-k, sorry for duplicate]

Hi!

Quoted 12 lines

works just fine, in terms of general computing anyways, after resume.

However, some of the ancilary functions, such as LCD brightness, RF kill switch, and volume mute button do not work after resuming.

Figuring that some hardware parameters were not being restored, I verified that by forcing a cold boot (boot up to GRUB, issue the 'halt' command to power off, then power on again and let the kernel resume from swsusp), everything works perfectly again just as it should because the BIOS takes care of the initialisation then, which it normally skips after a soft-off/S4.

Quoted 5 lines

Asside from trying to figure out exactly what hardware parameteres are not being saved/restored, I'm happy to let the BIOS initialise those things. But, I need a way to perform a normal power-off/S5 after swsusp instead of a soft-off/S4 so that I don't have to go though the double-grub-boot process every time. Can this be done?

echo shutdown > /sys/power/disk should do that. If it does not... well, see what is different in those two codepaths...

Pavel

Signature · 1 line
Boycott Kodak -- for their patent abuse against Java.
#1 lore raw
Quoted 12 lines · Pavel Machek
Quoted 12 lines

works just fine, in terms of general computing anyways, after resume.

However, some of the ancilary functions, such as LCD brightness, RF kill switch, and volume mute button do not work after resuming.

Figuring that some hardware parameters were not being restored, I verified that by forcing a cold boot (boot up to GRUB, issue the 'halt' command to power off, then power on again and let the kernel resume from swsusp), everything works perfectly again just as it should because the BIOS takes care of the initialisation then, which it normally skips after a soft-off/S4.

Quoted 8 lines
Quoted 5 lines

Asside from trying to figure out exactly what hardware parameteres are not being saved/restored, I'm happy to let the BIOS initialise those things. But, I need a way to perform a normal power-off/S5 after swsusp instead of a soft-off/S4 so that I don't have to go though the double-grub-boot process every time. Can this be done?

echo shutdown > /sys/power/disk should do that. If it does not... well, see what is different in those two codepaths...

I found out that 'shutdown' is the default and that I was already using that. Strange.

I did finally now get around to doing a more through battery of tests with many combinations of hibernating with 'platform' and 'shutdown' modes, and various GRUB 'halt' and 'reboot' commands. What I came up with is that basically nothing works.

In essentially all cases (except for rare inexplicable instances when it _does_ work, though I cannot replicate it with any consistency) the special keys _are_ functional immediately after power-on, through GRUB, through kernel initialization, through reading the suspended image. But then immediately after control is passed to the resumed system, the keys stop working.

Does this give you any other clues as to what might be going on?

Regards,
Ian Morgan

Signature · 5 lines
-------------------------------------------------------------------
 Ian E. Morgan          Vice President & C.O.O.       Webcon, Inc.
 imorgan at webcon dot ca       PGP: #2DA40D07       www.webcon.ca
    *  Customized Linux Network Solutions for your Business  *
-------------------------------------------------------------------
#2 lore raw

Hi!

Quoted 18 lines
Quoted 9 lines
Quoted 6 lines

Asside from trying to figure out exactly what hardware parameteres are not being saved/restored, I'm happy to let the BIOS initialise those things. But, I need a way to perform a normal power-off/S5 after swsusp instead of a
soft-off/S4 so that I don't have to go though the double-grub-boot process every time. Can this be done?

echo shutdown > /sys/power/disk should do that. If it does not... well, see what is different in those two codepaths...

I found out that 'shutdown' is the default and that I was already using that. Strange.

I did finally now get around to doing a more through battery of tests with many combinations of hibernating with 'platform' and 'shutdown' modes, and various GRUB 'halt' and 'reboot' commands. What I came up with is that basically nothing works.

Quoted 8 lines

In essentially all cases (except for rare inexplicable instances when it _does_ work, though I cannot replicate it with any consistency) the special keys _are_ functional immediately after power-on, through GRUB, through kernel initialization, through reading the suspended image. But then immediately after control is passed to the resumed system, the keys stop working.

Does this give you any other clues as to what might be going on?

No idea :-(. Something bad in ACPI land.

If there are some effects that survive reboot or powerdown, complain to your system vendor about crappy hardware. We should fix Linux, too, but that will be hard to do remotely.

Just go through swsusp and normal code paths, and see whats different...

Pavel