From owner-freebsd-bugs@FreeBSD.ORG Sun Sep 30 12:00:11 2012 Return-Path: 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 4915B106564A for ; Sun, 30 Sep 2012 12:00:11 +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 0B97F8FC08 for ; Sun, 30 Sep 2012 12:00:11 +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 q8UC0ApK043637 for ; Sun, 30 Sep 2012 12:00:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8UC0Avb043636; Sun, 30 Sep 2012 12:00:10 GMT (envelope-from gnats) Date: Sun, 30 Sep 2012 12:00:10 GMT Message-Id: <201209301200.q8UC0Avb043636@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Andriy Gapon 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: Andriy Gapon List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2012 12:00:11 -0000 The following reply was made to PR kern/172166; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, eugen@eg.sd.rdtc.ru Cc: Subject: Re: kern/172166: Deadlock in the networking code, possible due to a bug in the SCHED_ULE Date: Sun, 30 Sep 2012 14:54:02 +0300 It looks like CPUs 0 - 4 are idle, but CPU 5 has load of three. One of those threads is the syslogd thread that holds the lock, but the currently running thread is 'ipmi0: kcs' thread with tid 100118. It would interesting to examine what it is doing. -- Andriy Gapon