From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 18 Mar 2013 20:57:35 -0400 (EDT) From: Parag Warudkar To: Shuah Khan cc: Greg Kroah-Hartman , parag.lkml@gmail.com, eranian@google.com, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, stable@vger.kernel.org Subject: Re: [ 00/48] 3.4.37-stable review In-Reply-To: Message-ID: References: <20130318210810.247845918@linuxfoundation.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, 18 Mar 2013, Shuah Khan wrote: > I am seeing the following warning after suspend and resume: > > [ 665.841331] Component: resume devices, time: 10628 [snip] > [ 665.841446] Pid: 2686, comm: bash Not tainted 3.4.37-rc1+ #13 > [ 665.841450] Call Trace: > [ 665.841463] [] warn_slowpath_common+0x7f/0xc0 > [ 665.841471] [] warn_slowpath_fmt+0x46/0x50 > [ 665.841478] [] suspend_test_finish+0x86/0x90 > [ 665.841484] [] suspend_devices_and_enter+0x16e/0x330 > [ 665.841491] [] pm_suspend+0x18f/0x1f0 It is coming from kernel/power/suspend_test.c:53 - /* Warning on suspend means the RTC alarm period needs to be * larger -- the system was sooo slooowwww to suspend that the * alarm (should have) fired before the system went to sleep! * * Warning on either suspend or resume also means the system * has some performance issues. The stack dump of a WARN_ON * is more likely to get the right attention than a printk... */ WARN(msec > (TEST_SUSPEND_SECONDS * 1000), "Component: %s, time: %u\n", label, msec); That just means your system is slow to suspend/resume. I've seen the same many times on my older machines - you can likely ignore it. --Parag