Martin Wilck 8d1f66dc9b ipmi: set schedule_timeout_wait() value back to one ... Fix a regression introduced by ae74e823cb ("ipmi: add parameter to limit CPU usage in kipmid"). Some systems were seeing CPU usage go up dramatically with the recent changes to try to reduce timer usage in the IPMI driver. This was traced down to schedule_timeout_interruptible(1) being changed to schedule_timeout_interruptbile(0). Revert that part of the change. Addresses https://bugzilla.kernel.org/show_bug.cgi?id=16147 Reported-by: Thomas Jarosch <thomas.jarosch@intra2net.com> Signed-off-by: Corey Minyard <cminyard@mvista.com> Tested-by: Thomas Jarosch <thomas.jarosch@intra2net.com> Cc: <stable@kernel.org> [2.6.34.x] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2010-06-29 15:29:31 -07:00
..
ipmi_bt_sm.c
ipmi_devintf.c	drivers: Push down BKL into various drivers	2010-05-17 05:27:41 +02:00
ipmi_kcs_sm.c
ipmi_msghandler.c	ipmi: update driver to use dev_printk and its constructs	2010-05-27 09:12:50 -07:00
ipmi_poweroff.c
ipmi_si_intf.c	ipmi: set schedule_timeout_wait() value back to one	2010-06-29 15:29:31 -07:00
ipmi_si_sm.h
ipmi_smic_sm.c
ipmi_watchdog.c	drivers: Push down BKL into various drivers	2010-05-17 05:27:41 +02:00
Kconfig
Makefile