Some hibernate/sleep/powersafe questions

Ramurd · 03-07-2011, 02:46 AM

Hello all; I have 2 systems I use most of the time; One is a pc, the other a laptop.
The PC is configured by myself, and works almost flawlessly. For this system I have a simple question:

The PC has 2 hard disks. Using LVM, I have both in the same volumegroup, but with a few logical volumes (1 for system, 1 for /home and one for swap) They're all big enough. (Size doesn't matter in this regard). The question I have is this: does having swap in logical volume prevent me from putting the machine to sleep or hibernate, or is it having /boot in there as well that prevents this? If it's neither: any suggestions why this machine can only power off and not sleep / suspend?

The other machine is a laptop. For this one I have 2 questions:
1: when I unplug the power adapter, the machine keeps running fine and as intended. However, when I plug the power back in, the screen goes to "least bright" and seems to go to powersafe. No matter what I do, these settings keep being put there. A bug in KDE?
2: When this machine goes in any form of sleep / hibernate / suspend, it does so nicely. It is back up and running in seconds, which is nice. But... sound is completely gone and I have to reboot to hear anything, which is not so nice. Any clues how this can be resolved?

Both systems run Slackware 13.1 x86_64; The PC with kernel 2.6.35 instead of the 2.6.33

ozanbaba · 03-07-2011, 02:51 AM

What's your dmesg output?
Content of it, before and after a suspend/hibernate attempt would have a clue on the reason.

Ramurd · 03-07-2011, 06:23 AM

Just performed the suspend to ram on my laptop; which is the only one of the two I have at hand right now;

I gathered the info from dmesg during and after suspend to ram, and that shows this:

Code:

PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
btusb_intr_complete: hci0 urb ffff88007974e600 failed to resubmit (1)
btusb_bulk_complete: hci0 urb ffff8800798e8480 failed to resubmit (1)
btusb_bulk_complete: hci0 urb ffff880079971480 failed to resubmit (1)
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Stopping disk
parport_pc 00:0a: disabled
serial 00:09: disabled
ACPI handle has no context!
ehci_hcd 0000:00:1d.7: PCI INT D disabled
uhci_hcd 0000:00:1d.2: PCI INT C disabled
uhci_hcd 0000:00:1d.1: PCI INT B disabled
uhci_hcd 0000:00:1d.0: PCI INT A disabled
HDA Intel 0000:00:1b.0: PCI INT A disabled
HDA Intel 0000:00:1b.0: power state changed by ACPI to D3
ehci_hcd 0000:00:1a.7: PCI INT D disabled
uhci_hcd 0000:00:1a.2: PCI INT C disabled
uhci_hcd 0000:00:1a.1: PCI INT B disabled
uhci_hcd 0000:00:1a.0: PCI INT A disabled
PM: suspend of devices complete after 998.691 msecs
PM: late suspend of devices complete after 22.911 msecs
ACPI: Preparing to enter system sleep state S3
Disabling non-boot CPUs ...
CPU 1 is now offline
SMP alternatives: switching to UP code
Extended CMOS year: 2000
Back to C!
CPU0: Thermal monitoring handled by SMI
Extended CMOS year: 2000
Enabling non-boot CPUs ...
SMP alternatives: switching to SMP code
Booting Node 0 Processor 1 APIC 0x1
CPU1: Thermal monitoring handled by SMI
CPU1 is up
ACPI: Waking up from system sleep state S3
i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
i915 0000:00:02.0: restoring config space at offset 0x8 (was 0x1, writing 0x60f1)
i915 0000:00:02.0: restoring config space at offset 0x6 (was 0xc, writing 0x8000000c)
i915 0000:00:02.0: restoring config space at offset 0x4 (was 0x4, writing 0x98000004)
i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900000, writing 0x900407)
pci 0000:00:02.1: restoring config space at offset 0x4 (was 0x4, writing 0x98400004)
pci 0000:00:02.1: restoring config space at offset 0x1 (was 0x900000, writing 0x900007)
uhci_hcd 0000:00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
uhci_hcd 0000:00:1a.0: restoring config space at offset 0x8 (was 0x1, writing 0x60c1)
uhci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900001)
uhci_hcd 0000:00:1a.1: restoring config space at offset 0xf (was 0x200, writing 0x20b)
uhci_hcd 0000:00:1a.1: restoring config space at offset 0x8 (was 0x1, writing 0x60a1)
uhci_hcd 0000:00:1a.1: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900001)
uhci_hcd 0000:00:1a.2: restoring config space at offset 0xf (was 0x300, writing 0x30a)
uhci_hcd 0000:00:1a.2: restoring config space at offset 0x8 (was 0x1, writing 0x6081)
uhci_hcd 0000:00:1a.2: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900001)
ehci_hcd 0000:00:1a.7: restoring config space at offset 0xf (was 0x400, writing 0x40a)
ehci_hcd 0000:00:1a.7: restoring config space at offset 0x4 (was 0x0, writing 0x98904c00)
ehci_hcd 0000:00:1a.7: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
pcieport 0000:00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x98b198a1)
pcieport 0000:00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0x98809880)
pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0x20000000, writing 0x7070)
pcieport 0000:00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x10100)
pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:1c.1: restoring config space at offset 0xf (was 0x200, writing 0x20b)
pcieport 0000:00:1c.1: restoring config space at offset 0x9 (was 0x10001, writing 0x98d198c1)
pcieport 0000:00:1c.1: restoring config space at offset 0x8 (was 0x0, writing 0x98709870)
pcieport 0000:00:1c.1: restoring config space at offset 0x7 (was 0x20000000, writing 0x8080)
pcieport 0000:00:1c.1: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:1c.2: restoring config space at offset 0xf (was 0x300, writing 0x30a)
pcieport 0000:00:1c.2: restoring config space at offset 0x9 (was 0x10001, writing 0x98f198e1)
pcieport 0000:00:1c.2: restoring config space at offset 0x8 (was 0x0, writing 0x97f09400)
pcieport 0000:00:1c.2: restoring config space at offset 0x7 (was 0x20000000, writing 0x5040)
pcieport 0000:00:1c.2: restoring config space at offset 0x6 (was 0x0, writing 0x430300)
pcieport 0000:00:1c.2: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
pcieport 0000:00:1c.2: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:1c.4: restoring config space at offset 0xf (was 0x100, writing 0x10a)
pcieport 0000:00:1c.4: restoring config space at offset 0x9 (was 0x10001, writing 0x99119901)
pcieport 0000:00:1c.4: restoring config space at offset 0x8 (was 0x0, writing 0x93f09000)
pcieport 0000:00:1c.4: restoring config space at offset 0x7 (was 0x20000000, writing 0x3020)
pcieport 0000:00:1c.4: restoring config space at offset 0x6 (was 0x0, writing 0x844400)
pcieport 0000:00:1c.4: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
pcieport 0000:00:1c.4: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:1c.5: restoring config space at offset 0xf (was 0x200, writing 0x20b)
pcieport 0000:00:1c.5: restoring config space at offset 0x9 (was 0x10001, writing 0x99319921)
pcieport 0000:00:1c.5: restoring config space at offset 0x8 (was 0x0, writing 0x98609860)
pcieport 0000:00:1c.5: restoring config space at offset 0x7 (was 0x20000000, writing 0x9090)
pcieport 0000:00:1c.5: restoring config space at offset 0x6 (was 0x0, writing 0x858500)
pcieport 0000:00:1c.5: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
pcieport 0000:00:1c.5: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
uhci_hcd 0000:00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
uhci_hcd 0000:00:1d.0: restoring config space at offset 0x8 (was 0x1, writing 0x6061)
uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900001)
uhci_hcd 0000:00:1d.1: restoring config space at offset 0xf (was 0x200, writing 0x20a)
uhci_hcd 0000:00:1d.1: restoring config space at offset 0x8 (was 0x1, writing 0x6041)
uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900001)
uhci_hcd 0000:00:1d.2: restoring config space at offset 0xf (was 0x300, writing 0x30a)
uhci_hcd 0000:00:1d.2: restoring config space at offset 0x8 (was 0x1, writing 0x6021)
uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900001)
ehci_hcd 0000:00:1d.7: restoring config space at offset 0xf (was 0x400, writing 0x40a)
ehci_hcd 0000:00:1d.7: restoring config space at offset 0x4 (was 0x0, writing 0x98904800)
ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
pci 0000:00:1e.0: restoring config space at offset 0xf (was 0x20000, writing 0x200ff)
pci 0000:00:1e.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pci 0000:00:1e.0: restoring config space at offset 0x8 (was 0x0, writing 0x98509850)
pci 0000:00:1e.0: restoring config space at offset 0x7 (was 0x22800000, writing 0x228000f0)
pci 0000:00:1e.0: restoring config space at offset 0x6 (was 0x20000000, writing 0x20868600)
pci 0000:00:1e.0: restoring config space at offset 0x1 (was 0x100100, writing 0x100107)
ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00000, writing 0x2b00407)
iwlagn 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
iwlagn 0000:02:00.0: restoring config space at offset 0x4 (was 0x4, writing 0x98700004)
iwlagn 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
iwlagn 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
tg3 0000:85:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
tg3 0000:85:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
ohci1394 0000:86:02.0: restoring config space at offset 0xf (was 0x180c0100, writing 0x180c010a)
ohci1394 0000:86:02.0: restoring config space at offset 0x4 (was 0x0, writing 0x98500000)
ohci1394 0000:86:02.0: restoring config space at offset 0x3 (was 0x0, writing 0x4010)
ohci1394 0000:86:02.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900216)
PM: early resume of devices complete after 5.457 msecs
i915 0000:00:02.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
usb usb3: root hub lost power or was reset
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
uhci_hcd 0000:00:1a.1: setting latency timer to 64
usb usb4: root hub lost power or was reset
uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.2: setting latency timer to 64
usb usb5: root hub lost power or was reset
ehci_hcd 0000:00:1a.7: PCI INT D -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:1a.7: setting latency timer to 64
HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
HDA Intel 0000:00:1b.0: setting latency timer to 64
HDA Intel 0000:00:1b.0: irq 30 for MSI/MSI-X
hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x10170500
hda-intel: No response from codec, disabling MSI: last cmd=0x10170500
hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x10170500
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:1d.0: setting latency timer to 64
usb usb6: root hub lost power or was reset
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22
uhci_hcd 0000:00:1d.1: setting latency timer to 64
usb usb7: root hub lost power or was reset
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
usb usb8: root hub lost power or was reset
ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 20 (level, low) -> IRQ 20
ehci_hcd 0000:00:1d.7: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
ahci 0000:00:1f.2: setting latency timer to 64
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16]  MMIO=[98500000-985007ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
serial 00:09: activated
parport_pc 00:0a: activated
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata6: SATA link down (SStatus 0 SControl 300)
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: configured for UDMA/100
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata2.00: configured for UDMA/100
sd 0:0:0:0: [sda] Starting disk
usb 3-1: reset full speed USB device using uhci_hcd and address 2
btusb 3-1:1.0: no reset_resume for driver btusb?
btusb 3-1:1.1: no reset_resume for driver btusb?
PM: resume of devices complete after 7391.336 msecs
Restarting tasks ... done.

After suspend, in an attempt to awaken the soundcard, I do:

Code:

alsactl init  
Unknown hardware: "HDA-Intel" "Analog Devices AD1984A" "HDA:11d4194a,103c360d,00100400 HDA:11c11040,103c1378,00100200" "0x103c" "0x360d"
Hardware is initialized using a guess method

... but it's only playing the sound of silence in a literal context.

Ramurd · 03-07-2011, 02:59 PM

Now I am on my pc, and performed the hibernate and sleep options; ran dmesg prior and after the suspend. Nothing at all is added there. Checked /var/log/syslog: no changes either, nor in /var/log/debug or /var/log/messages.

It seems as if the entire command either is not performed at all or is rejected...

Hmm... could it be I am not loading a kernel module :-o

ozanbaba · 03-07-2011, 03:05 PM

Your problem at laptop might be pci/usb problem. I am not sure about that.
About your pc, try running this as root at console. pm-suspend. And it might be very well it is related to some driver on your system that breaks your suspand. (My usb keyord sometimes cause it some, time does not. NVdia AVG driver known to break it etc.).

Ramurd · 03-07-2011, 05:16 PM

hmm; nice one. pm-suspend works on the pc. nice one! Even sound works again.
so, it actually appears to be a rights issue; Going to check out more on that.

ozanbaba · 03-08-2011, 02:19 AM

Check out if you are member of group power.

Ramurd · 03-08-2011, 02:38 AM

Thought of that; made my default user member of the group power. After a "su -" I tried to perform the same commands on the prompt (as the X session would only work after a log out / log in); The prompt commands would not work (gave the reply that I have to be root); This evening I will try and see if the group power is indeed the solution. Checked this on my laptop, and noticed the normal user is indeed member of the powergroup, and with this user I can do suspend and hibernate, so I guess that is indeed the solution.

ozanbaba · 03-08-2011, 03:15 AM

For group change to get effective, You need to log off and log in by the way.

Ramurd · 03-08-2011, 09:46 AM

Quote:

Originally Posted by ozanbaba

For group change to get effective, You need to log off and log in by the way.

That's only natural;

If you do an "su - <user>" you load the user as a new login, hence the group membership is loaded. You can check this with the command "id"; you'll see that your group membership is taken into account. However, I only tried it this way to test this out on the command-line; I expect that the kde buttons do something somewhat different than that.

ozanbaba · 03-08-2011, 09:54 AM

For KDE, you need begger log off log in

Ramurd · 03-09-2011, 03:35 AM

That's only natural; Any X would require to log in again, as the session itself is still run in the user/group configuration which was effective at the point of login. That's why I did that sidestep and ran the pm-suspend as user in a new login environment, which would, at that moment, only be available after a new X login or in a shell.

Anyway, the strange thing is that even after a reboot the suspend and hibernate options are only available to the root user in a shell; I didn't log in root in X yet, so I am not 100% sure if the buttons don't work there either; which is very possible and would mean the buttons themselves are broken and perform an unsupported command ;-)