Arch Linux

Inchw0rm

Member

Registered: 2013-05-12

Posts: 25

[SOLVED] Broken suspend

Hi there,

for quite some time I've got a problem suspending my computer.
Running systemctl suspend suspends my machine, but powers it on instantly. I disabled all wake up settings (keyboard, mouse, network and so on) in the BIOS, but the same behavior occurred again.

This is my dmesg output:

[ 1391.336457] PM: suspend entry (deep)
[ 1391.336459] PM: Syncing filesystems ... done.
[ 1393.325887] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 1393.327648] OOM killer disabled.
[ 1393.327648] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1393.328831] Suspending console(s) (use no_console_suspend to debug)
[ 1393.329612] serial 00:05: disabled
[ 1393.329900] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
[ 1393.329956] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 1393.329999] sd 4:0:0:0: [sdc] Stopping disk
[ 1393.330005] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 1393.330334] sd 2:0:0:0: [sda] Stopping disk
[ 1393.339669] sd 3:0:0:0: [sdb] Stopping disk
[ 1395.003986] ACPI: Preparing to enter system sleep state S3
[ 1395.005036] PM: Saving platform NVS memory
[ 1395.005233] Disabling non-boot CPUs ...
[ 1395.031415] smpboot: CPU 1 is now offline
[ 1395.061368] smpboot: CPU 2 is now offline
[ 1395.088004] smpboot: CPU 3 is now offline
[ 1395.089973] ACPI: Low-level resume complete
[ 1395.090044] PM: Restoring platform NVS memory
[ 1395.091199] PCI-DMA: Resuming GART IOMMU
[ 1395.091200] PCI-DMA: Restoring GART aperture settings
[ 1395.091205] LVT offset 1 assigned for vector 0x400
[ 1395.091214] IBS: LVT offset 1 assigned
[ 1395.091550] microcode: CPU0: new patch_level=0x010000db
[ 1395.091577] Enabling non-boot CPUs ...
[ 1395.091618] x86: Booting SMP configuration:
[ 1395.091619] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 1395.094166] TSC synchronization [CPU#0 -> CPU#1]:
[ 1395.094167] Measured 4628095298 cycles TSC warp between CPUs, turning off TSC clock.
[ 1395.094169] tsc: Marking TSC unstable due to check_tsc_sync_source failed
[ 1395.094190] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
[ 1395.094191] sched_clock: Marking unstable (1395100882453, -9897147)<-(1395197608459, -103419140)
[ 1396.496814]  cache: parent cpu1 should not be sleeping
[ 1396.496903] microcode: CPU1: patch_level=0x01000086
[ 1396.496906] microcode: CPU1: new patch_level=0x010000db
[ 1396.493887] CPU1 is up
[ 1396.493887] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 1396.494578]  cache: parent cpu2 should not be sleeping
[ 1396.494659] microcode: CPU2: patch_level=0x01000086
[ 1396.494661] microcode: CPU2: new patch_level=0x010000db
[ 1396.494785] CPU2 is up
[ 1396.494828] clocksource: Switched to clocksource hpet
[ 1396.494824] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1396.494853]  cache: parent cpu3 should not be sleeping
[ 1396.494853] microcode: CPU3: patch_level=0x01000086
[ 1396.494853] microcode: CPU3: new patch_level=0x010000db
[ 1396.494853] CPU3 is up
[ 1396.494853] ACPI: Waking up from system sleep state S3
[ 1396.494853] pci 0000:00:08.0: Enabling HT MSI Mapping
[ 1396.494853] ahci 0000:00:09.0: Enabling HT MSI Mapping
[ 1396.494853] forcedeth 0000:00:0a.0: Enabling HT MSI Mapping
[ 1396.494853] serial 00:05: activated
[ 1396.494853] ata2: port disabled--ignoring
[ 1396.494853] sd 2:0:0:0: [sda] Starting disk
[ 1396.494853] sd 3:0:0:0: [sdb] Starting disk
[ 1396.494853] sd 4:0:0:0: [sdc] Starting disk
[ 1396.494853] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1396.494853] ata7: SATA link down (SStatus 0 SControl 300)
[ 1396.494853] ata8: SATA link down (SStatus 0 SControl 300)
[ 1396.494853] ata6.00: configured for UDMA/100
[ 1396.494853] usb 3-4: reset full-speed USB device number 3 using ohci-pci
[ 1396.494853] OOM killer enabled.
[ 1396.494853] Restarting tasks ... 
[ 1396.494853] usb 3-1: USB disconnect, device number 2
[ 1396.494853] done.
[ 1396.494853] PM: suspend exit

This is my journal:

-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sleep.target has finished shutting down.
Dec 30 15:54:21 archangel systemd[1]: Reached target Suspend.
-- Subject: Unit suspend.target has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit suspend.target has finished starting up.
-- 
-- The start-up result is RESULT.
Dec 30 15:54:21 archangel systemd-logind[430]: Operation 'sleep' finished.
Dec 30 15:54:21 archangel systemd[1]: suspend.target: Unit not needed anymore. Stopping.
Dec 30 15:54:21 archangel systemd[1]: Stopped target Suspend.
-- Subject: Unit suspend.target has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit suspend.target has finished shutting down.

I'm currently clueless, and would be grateful if you told me where to look. I also consider flashing a new BIOS, is there a way to do so from within my Arch?

Last edited by Inchw0rm (2017-12-30 18:41:46)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,863

Re: [SOLVED] Broken suspend

cat /proc/acpi/wakeup

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Inchw0rm

Member

Registered: 2013-05-12

Posts: 25

Re: [SOLVED] Broken suspend

cat /proc/acpi/wakeup

ok thx a lot

Device  S-state   Status   Sysfs node
PS2K      S4    *disabled
PS2M      S4    *disabled
UAR1      S4    *disabled  pnp:00:05
SMB0      S4    *disabled  pci:0000:00:01.1
USB0      S4    *enabled   pci:0000:00:02.0
USB2      S3    *enabled   pci:0000:00:02.1
US15      S4    *enabled   pci:0000:00:04.0
US12      S3    *enabled   pci:0000:00:04.1
NMAC      S5    *disabled  pci:0000:00:0a.0
P0P1      S4    *disabled  pci:0000:00:08.0
HDAC      S4    *disabled  pci:0000:00:07.0
MXR0      S4    *disabled  pci:0000:00:10.0
BR11      S4    *disabled
BR12      S4    *disabled
BR13      S4    *disabled  pci:0000:00:13.0
BR14      S4    *disabled  pci:0000:00:14.0
BR15      S4    *disabled
BR16      S4    *disabled
BR17      S4    *disabled

I've matched those pci IDs with those from lspci

00:02.0 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:02.1 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:04.0 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:04.1 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)

Also I did some research, and I found out that you can toggle between the states by just echoing the device descriptors to /proc/cpu/wakeup, I run echo as root, but still get the permission denied error. Is there another way to toggle them?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,863

Re: [SOLVED] Broken suspend

echo USB0 | sudo tee /proc/cpu/wakeup

In case you tried something like "sudo echo USB0 > /proc/cpu/wakeup": what writes into the file? The sudo'd echo?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Inchw0rm

Member

Registered: 2013-05-12

Posts: 25

Re: [SOLVED] Broken suspend

echo USB0 | sudo tee /proc/cpu/wakeup

In case you tried something like "sudo echo USB0 > /proc/cpu/wakeup": what writes into the file? The sudo'd echo?

Alright, playing around with the USB plugs + BIOS settings solved my problem. Removing every USB device except the mouse fixed the strange wake up behavior. Replugging broke it again, but this time in another way. The system froze with shining LEDs and spinning fans, doing nothing. I played around with my BIOS, and discovered some working settings. Strange... Whatevs... I'll mark as solved for now. @Seth, thanks for the support!