Rafael,
On Fri, 28 Jul 2017, Tomi Sarvela wrote:
> rtcwake-1332 [000] d..1 64.411112: suspend_device_irqs:
> presuspend 8 state 00401200
> rtcwake-1332 [000] d..1 64.411112: __irq_disable: predisable 8
> state 00401200
> rtcwake-1332 [000] d..1 64.411113: __irq_disable: postdisable 8
> state 00411200
> rtcwake-1332 [000] d..1 64.411114: suspend_device_irqs:
> postsuspend 8 state 00411200
> rtcwake-1332 [000] d..1 64.411115: suspend_device_irqs:
> presuspend 9 state 00403300
> rtcwake-1332 [000] d..1 64.411115: __irq_disable: predisable 9
> state 00403300
> rtcwake-1332 [000] d..1 64.411116: __irq_disable: postdisable 9
> state 00413300
> rtcwake-1332 [000] d..1 64.411116: suspend_device_irqs:
> postsuspend 9 state 00413300
> rtcwake-1332 [000] d..1 64.411117: suspend_device_irqs:
I'm trying to analyze that suspend/resume problem. While staring at the
trace Tomi provided I noticed, that neither the RTC irq nor the ACPI irq
have the wakeup armed bit set, but the system resumes from an RTC
interrupt. That's inconsistent at least, or am I missing something
essential?
Thanks,
tglx
