summaryrefslogtreecommitdiff
path: root/kernel/power
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@linux.intel.com>2008-11-18 06:56:51 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2008-11-18 08:07:36 -0800
commita6a0c4ca7edb378a8a7332501f097089cb1051c4 (patch)
treeafc4bd95482576e7dfd0685d1cb2bed6cac65db9 /kernel/power
parent72b51a6b4d803381f16d819df392dd1efd1c7181 (diff)
suspend: use WARN not WARN_ON to print the message
By using WARN(), kerneloops.org can collect which component is causing the delay and make statistics about that. suspend_test_finish() is currently the number 2 item but unless we can collect who's causing it we're not going to be able to fix the hot topic ones.. Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/power')
-rw-r--r--kernel/power/main.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/power/main.c b/kernel/power/main.c
index 19122cf6d827..b8f7ce9473e8 100644
--- a/kernel/power/main.c
+++ b/kernel/power/main.c
@@ -174,7 +174,7 @@ static void suspend_test_finish(const char *label)
* has some performance issues. The stack dump of a WARN_ON
* is more likely to get the right attention than a printk...
*/
- WARN_ON(msec > (TEST_SUSPEND_SECONDS * 1000));
+ WARN(msec > (TEST_SUSPEND_SECONDS * 1000), "Component: %s\n", label);
}
#else