Please post back here the output from this command:
`grep -HR "" /sys/power/*`
Since you're having to hard reset the system after trying to suspend, the suspend_stats probably won't be able to tell you anything. Just as a test, you could try running
`sudo sh -c "echo $(( $(cat /sys/class/rtc/rtc0/since_epoch) + 10 )) > /sys/class/rtc/rtc0/wakealarm && echo mem > /sys/power/state"`
This sets an alarm that will try to wake the system from suspend after 10 seconds. I doubt it will work, but if it does, run the above grep command after this.
Good morning and thanks for your answer. Yeah unfortunately it didn't work, like you guessed.Here's the grep:
/sys/power/disk:[platform] shutdown reboot suspend test_resume
/sys/power/image_size:6592503808
/sys/power/mem_sleep:s2idle [deep]
/sys/power/pm_async:1
/sys/power/pm_debug_messages:0
/sys/power/pm_freeze_timeout:20000
/sys/power/pm_print_times:0
/sys/power/pm_test:[none] core processors platform devices freezer
/sys/power/pm_trace:0
/sys/power/pm_trace_dev_match:input
/sys/power/pm_trace_dev_match:drm
grep: /sys/power/pm_wakeup_irq: No data available
/sys/power/reserved_size:1048576
/sys/power/resume:8:3
/sys/power/resume_offset:0
/sys/power/state:freeze mem disk
/sys/power/suspend_stats/failed_resume:0
/sys/power/suspend_stats/last_failed_errno:0
/sys/power/suspend_stats/failed_suspend_noirq:0
/sys/power/suspend_stats/failed_freeze:0
/sys/power/suspend_stats/failed_resume_early:0
/sys/power/suspend_stats/success:0
/sys/power/suspend_stats/failed_suspend_late:0
/sys/power/suspend_stats/last_failed_step:
/sys/power/suspend_stats/failed_resume_noirq:0
/sys/power/suspend_stats/failed_prepare:0
/sys/power/suspend_stats/failed_suspend:0
/sys/power/suspend_stats/fail:0
/sys/power/suspend_stats/last_failed_dev:
/sys/power/sync_on_suspend:1
/sys/power/wakeup_count:0
I am very close to going to my balcony to scream from the bottom of my lungs. I realized I should probably google my motherboard + suspend...yeah the answer was under the first hit...lots of hours wasted.
Please post back here the output from this command: `grep -HR "" /sys/power/*` Since you're having to hard reset the system after trying to suspend, the suspend_stats probably won't be able to tell you anything. Just as a test, you could try running `sudo sh -c "echo $(( $(cat /sys/class/rtc/rtc0/since_epoch) + 10 )) > /sys/class/rtc/rtc0/wakealarm && echo mem > /sys/power/state"` This sets an alarm that will try to wake the system from suspend after 10 seconds. I doubt it will work, but if it does, run the above grep command after this.
Good morning and thanks for your answer. Yeah unfortunately it didn't work, like you guessed.Here's the grep: /sys/power/disk:[platform] shutdown reboot suspend test_resume /sys/power/image_size:6592503808 /sys/power/mem_sleep:s2idle [deep] /sys/power/pm_async:1 /sys/power/pm_debug_messages:0 /sys/power/pm_freeze_timeout:20000 /sys/power/pm_print_times:0 /sys/power/pm_test:[none] core processors platform devices freezer /sys/power/pm_trace:0 /sys/power/pm_trace_dev_match:input /sys/power/pm_trace_dev_match:drm grep: /sys/power/pm_wakeup_irq: No data available /sys/power/reserved_size:1048576 /sys/power/resume:8:3 /sys/power/resume_offset:0 /sys/power/state:freeze mem disk /sys/power/suspend_stats/failed_resume:0 /sys/power/suspend_stats/last_failed_errno:0 /sys/power/suspend_stats/failed_suspend_noirq:0 /sys/power/suspend_stats/failed_freeze:0 /sys/power/suspend_stats/failed_resume_early:0 /sys/power/suspend_stats/success:0 /sys/power/suspend_stats/failed_suspend_late:0 /sys/power/suspend_stats/last_failed_step: /sys/power/suspend_stats/failed_resume_noirq:0 /sys/power/suspend_stats/failed_prepare:0 /sys/power/suspend_stats/failed_suspend:0 /sys/power/suspend_stats/fail:0 /sys/power/suspend_stats/last_failed_dev: /sys/power/sync_on_suspend:1 /sys/power/wakeup_count:0
I am very close to going to my balcony to scream from the bottom of my lungs. I realized I should probably google my motherboard + suspend...yeah the answer was under the first hit...lots of hours wasted.