Hi,
I'm sorry to send this to all, but there are no test cases on qatracker to report this on and it seems urgent.
A little while after booting the latest android images on my Panda it goes into an endless loop, outputting this:
pm_op(): platform_pm_suspend+0x0/0x9c returns -95 PM: Device kim failed to suspend: error -95 PM: Some devices failed to suspend PM: resume of devices complete after 476.470 msecs Restarting tasks ... done. suspend: exit suspend, ret = -95 (2000-01-01 00:01:20.662933350 UTC) PM: Syncing filesystems ... done. Freezing user space processes ... (elapsed 0.02 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. Suspending console(s) (use no_console_suspend to debug)
Complete log attached.
Thanks,
Mattias
On Fri, May 27, 2011 at 11:54 AM, Mattias Backman mattias.backman@linaro.org wrote:
Hi,
I'm sorry to send this to all, but there are no test cases on qatracker to report this on and it seems urgent.
A little while after booting the latest android images on my Panda it goes into an endless loop, outputting this:
pm_op(): platform_pm_suspend+0x0/0x9c returns -95 PM: Device kim failed to suspend: error -95 PM: Some devices failed to suspend PM: resume of devices complete after 476.470 msecs Restarting tasks ... done. suspend: exit suspend, ret = -95 (2000-01-01 00:01:20.662933350 UTC) PM: Syncing filesystems ... done. Freezing user space processes ... (elapsed 0.02 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. Suspending console(s) (use no_console_suspend to debug)
Thanks for testing.
I saw that in one of the previous builds. my install from yesterday ran for 3 hours and didn't get this issue. It's obviously kind of PM related.
Please file a bug against linaro-android project.
On 05/27/2011 12:14 PM, Somebody in the thread at some point said:
pm_op(): platform_pm_suspend+0x0/0x9c returns -95 PM: Device kim failed to suspend: error -95
Thanks for testing.
I saw that in one of the previous builds. my install from yesterday ran for 3 hours and didn't get this issue. It's obviously kind of PM related.
Please file a bug against linaro-android project.
kim is the BT stuff in the shared module with WLAN.
Previously, on 2.6.38 anyway there were issues around BT logical interface also feeling it was available on SDIO and defeating wlan power actions then from affecting sdio parent, since it still felt the BT was another logical sdio child interface that was active.
Actually, BT is accessed via UART on Panda. Maybe it's something about that.
-Andy
Freezing user space processes ... (elapsed 0.02 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. Suspending console(s) (use no_console_suspend to debug)
Thanks for testing.
I saw that in one of the previous builds. my install from yesterday ran for 3 hours and didn't get this issue. It's obviously kind of PM related.
Please file a bug against linaro-android project.
-
Alexander Sack -
Andy Green -
Mattias Backman