ipmi: set schedule_timeout_wait() value back to one
commit0dd6ec3a33cab9ee890c9ff671edea9202246c27
authorMartin Wilck <martin.wilck@ts.fujitsu.com>
Tue, 29 Jun 2010 22:05:31 +0000 (29 15:05 -0700)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 2 Aug 2010 17:29:45 +0000 (2 10:29 -0700)
tree054b9e1333fde16b2fcb947c468c21a67c5fc003
parentbe25710fff49935664a4cecd7ac52a1d804049e1
ipmi: set schedule_timeout_wait() value back to one

commit 8d1f66dc9b4f80a1441bc1c33efa98aca99e8813 upstream.

Fix a regression introduced by ae74e823cb7d ("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>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/char/ipmi/ipmi_si_intf.c