From owner-freebsd-stable@FreeBSD.ORG Sat Feb 11 03:01:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C553C1065670 for ; Sat, 11 Feb 2012 03:01:08 +0000 (UTC) (envelope-from jholland@fastsoft.com) Received: from fs-mail-relay.fastsoft.com (fs-mail-relay.fastsoft.com [38.102.243.14]) by mx1.freebsd.org (Postfix) with ESMTP id A22CD8FC1A for ; Sat, 11 Feb 2012 03:01:08 +0000 (UTC) Received: from hq-es.fastsoft.com (hq-es.fastsoft.com [38.102.243.86]) by fs-mail-relay.fastsoft.com (8.14.4/8.14.4) with ESMTP id q1B2oE2V042260 for ; Fri, 10 Feb 2012 18:50:30 -0800 (PST) (envelope-from jholland@fastsoft.com) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 10 Feb 2012 18:50:14 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: hang during dump (reproducible) Thread-Index: AczoZ+Fn+NvkyIiISSKG8TQogz+obA== From: "Jake Holland" To: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: hang during dump (reproducible) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2012 03:01:08 -0000 Hi, I was reliably seeing a hang during panic in stable/8 -r231144 (and 8.2 = release) with an active ssh session. The SCHEDULER_STOPPED patch fixed = it, once I found it: http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030127.h= tml http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063824.h= tml Many thanks to Attilio Rao, Kostik Belousov, and Andriy Gapon. And = anybody else involved. However, when I looked at the commit I noticed this: > $ svn log -r228424 svn://svn.freebsd.org/base ... > MFC after: 3 months (or never) I'm not sure whether "never" is still considered an option, but it would = be useful for me if 8.3 release, when it comes, does not hang this way = during panic. But thanks for the patch, regardless. Problem details: If I did a "sysctl debug.kdb.panic=3D1" from the console while the = machine was idle, the dump would complete and the machine would reboot = and come up with a good core. If I did the same command remotely via ssh, it would hang every time. I also usually would see a hang if I had an active ssh session printing = things while I caused a panic from the console. Occasionally in that = case it would continue and make a good core if I killed the ssh session = from the client side. An open but idle ssh session did not seem to = induce a hang. If anybody wants other details, I'd be happy to provide them. Jake Holland