Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751472Ab1DOFpR (ORCPT ); Fri, 15 Apr 2011 01:45:17 -0400 Received: from eu1sys200aog108.obsmtp.com ([207.126.144.125]:41320 "EHLO eu1sys200aog108.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751018Ab1DOFpP (ORCPT ); Fri, 15 Apr 2011 01:45:15 -0400 Message-ID: <4DA7DB56.4070307@st.com> Date: Fri, 15 Apr 2011 11:14:54 +0530 From: deepaksi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0 MIME-Version: 1.0 To: Cc: Shiraz HASHIM , Vipin KUMAR , Amit GOEL , Armando VISCONTI , deepaksi , , , Subject: [linux-pm] SPEAR Power Management: Suspend to ram problem Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2137 Lines: 51 Hi, I am facing some issues related to system wake up from the sleep. The SPEAr system is a SOC having the ARM cortex core. The system hardware has certain power islands, and all islands except the one having the wake up sources and Power Management Controller are made off, while moving into sleep. On waking up from Suspend to RAM, I get the following log on the console ( the debugger shows, all the devices are up and some user space processes are being run, which execute a system call before crash). PM: Syncing filesystems ... done. Freezing user space processes ... (elapsed 0.01 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Suspending console(s) (use no_console_suspend to debug) PM: suspend of devices complete after 2.857 msecs PM: late suspend of devices complete after 0.970 msecs PM: early resume of devices complete after 0.671 msecs usb usb3: root hub lost power or was reset usb usb4: root hub lost power or was reset PM: resume of devices complete after 30.735 msecs Restarting tasks ... done. Kernel panic - not syncing: Attempted to kill init! Backtrace: [<80031b30>] (dump_backtrace+0x0/0x10c) from [<80031c70>] (dump_stack+0x18/0x1c) r7:0000000b r6:0000000b r5:8f828000 r4:803b90e8 [<80031c58>] (dump_stack+0x0/0x1c) from [<8004266c>] (panic+0x60/0x17c) [<8004260c>] (panic+0x0/0x17c) from [<80045800>] (do_exit+0x68/0x5f0) r3:8038d3c0 r2:8f828000 r1:8f8280fc r0:80331eaa [<80045798>] (do_exit+0x0/0x5f0) from [<80045e20>] (do_group_exit+0x98/0xc8) [<80045d88>] (do_group_exit+0x0/0xc8) from [<80050eec>] (get_signal_to_deliver+0x310/0x350) r7:8f82a000 r6:8f82bee0 r5:8f91259c r4:0000000b [<80050bdc>] (get_signal_to_deliver+0x0/0x350) from [<800309a0>] (do_notify_resume+0x70/0x62c) [<80030930>] (do_notify_resume+0x0/0x62c) from [<8002dd98>] (work_pending+0x24/0x28) Could any one help in debugging the same ? Deepak -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/