android_kernel_motorola_msm8916 icon indicating copy to clipboard operation
android_kernel_motorola_msm8916 copied to clipboard

suspend-related oopses

Open sthalik opened this issue 8 years ago • 1 comments

I started getting these on suspend/resume. Are they serious?

[  553.264489,0] Enabling non-boot CPUs ...
[  553.265392,0] CPU1 is up
[  553.265964,0] CPU2 is up
[  553.266573,0] CPU3 is up
[  553.267022,0] PM: noirq resume of devices complete after 0.439 msecs
[  553.267306,0] ------------[ cut here ]------------
[  553.267315,0] WARNING: at kernel/irq/manage.c:459 resume_device_irqs+0x50/0x78()
[  553.267318,0] Unbalanced enable for IRQ 61
[  553.267321,0] Modules linked in:
[  553.267326,0] CPU: 0 PID: 922 Comm: system_server Tainted: G        W    3.10.90-gbc1b510-51517-g5fcb2fa #3
[  553.267340,0] [] (unwind_backtrace+0x0/0x12c) from [] (show_stack+0x10/0x14)
[  553.267351,0] [] (show_stack+0x10/0x14) from [] (warn_slowpath_fmt+0x64/0xd8)
[  553.267359,0] [] (warn_slowpath_fmt+0x64/0xd8) from [] (resume_device_irqs+0x50/0x78)
[  553.267367,0] [] (resume_device_irqs+0x50/0x78) from [] (dpm_resume_noirq+0x138/0x468)
[  553.267374,0] [] (dpm_resume_noirq+0x138/0x468) from [] (dpm_resume_start+0xc/0x18)
[  553.267381,0] [] (dpm_resume_start+0xc/0x18) from [] (suspend_devices_and_enter+0x168/0x438)
[  553.267389,0] [] (suspend_devices_and_enter+0x168/0x438) from [] (pm_suspend+0x278/0x388)
[  553.267396,0] [] (pm_suspend+0x278/0x388) from [] (state_store+0x128/0x180)
[  553.267404,0] [] (state_store+0x128/0x180) from [] (kobj_attr_store+0x14/0x20)
[  553.267413,0] [] (kobj_attr_store+0x14/0x20) from [] (sysfs_write_file+0x158/0x188)
[  553.267421,0] [] (sysfs_write_file+0x158/0x188) from [] (SyS_write+0x108/0x2a4)
[  553.267429,0] [] (SyS_write+0x108/0x2a4) from [] (__sys_trace_return+0x0/0x18)
[  553.267432,0] ---[ end trace ad3cf72605cebb4f ]---
[  553.268005,0] PM: early resume of devices complete after 0.545 msecs

sthalik avatar Oct 11 '15 05:10 sthalik

Sounds like somewhere there are unbalanced calls to disable_irq and enable_irq. Nothing serious, but somewhere there's likely a missing disable_irq or extra enable_irq call in power management code.

sultanqasim avatar Oct 11 '15 14:10 sultanqasim