From owner-freebsd-bugs@FreeBSD.ORG  Fri Oct  5 08:50:13 2012
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 7A3E61065672
	for <freebsd-bugs@hub.freebsd.org>;
	Fri,  5 Oct 2012 08:50:13 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 5D9EE8FC14
	for <freebsd-bugs@hub.freebsd.org>;
	Fri,  5 Oct 2012 08:50:13 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q958oCwF020019
	for <freebsd-bugs@freefall.freebsd.org>; Fri, 5 Oct 2012 08:50:12 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q958oCod020014;
	Fri, 5 Oct 2012 08:50:12 GMT (envelope-from gnats)
Date: Fri, 5 Oct 2012 08:50:12 GMT
Message-Id: <201210050850.q958oCod020014@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Eugene Grosbein <egrosbein@rdtc.ru>
Cc: 
Subject: Re: kern/172166: Deadlock in the networking code, possible due to
 a bug in the SCHED_ULE
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Eugene Grosbein <egrosbein@rdtc.ru>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 08:50:13 -0000

The following reply was made to PR kern/172166; it has been noted by GNATS.

From: Eugene Grosbein <egrosbein@rdtc.ru>
To: Andriy Gapon <avg@freebsd.org>
Cc: bug-followup@freebsd.org, Alexander Motin <mav@freebsd.org>
Subject: Re: kern/172166: Deadlock in the networking code, possible due to
 a bug in the SCHED_ULE
Date: Fri, 05 Oct 2012 15:39:58 +0700

 04.10.2012 17:23, Andriy Gapon пишет:
 
 >> Can I have any advice/workaround/bugfix on how to reconfigure my routers
 >> to prevent them from locking this way?
 > 
 > As I said, the primary problem here is the ipmi thread going insane.
 > You can try to remove ipmi driver, if you can afford that.
 > Or you can try to hack on it, so that
 > (1) it voluntary yields even when it thinks that it always has work to do
 > (2) there is some diagnostic on what keeps it running
 > 
 > You may also try to set the thread's priority to PUSER (using sched_prio), but I
 > am not sure what bad side-effects may happen because of that.
 > 
 > No magic bullet here, sorry.
 
 Thank you. As workaround, I've unloaded ipmi.ko
 and edited my scripts to access IPMI sensors over IP instead of local interface.
 
 Eugene Grosbein