From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 15:17:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 523FF523 for ; Tue, 24 Jun 2014 15:17:55 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A6012529 for ; Tue, 24 Jun 2014 15:17:55 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2DB85B96E; Tue, 24 Jun 2014 11:17:54 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: Weird ISR accounting in 10-STABLE Date: Tue, 24 Jun 2014 11:12:48 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <201406231614.51004.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201406241112.48813.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 24 Jun 2014 11:17:54 -0400 (EDT) Cc: Vlad Galu X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 15:17:55 -0000 On Monday, June 23, 2014 5:18:34 pm Vlad Galu wrote: > Hi John, thanks for reaching back. Yes, that must have been it, although > the machine was completely idle at the time, except for my SSH session it > was not generating or receiving any other traffic. > > I have since updated to r267702 and the problem seems to have magically > disappeared... I still have the old kernel but can't currently reboot the > machine. When I do next, I will revert to it and try to provide more > information. Having that swi sit at 100% CPU does seem like a bug if you can reproduce it. -- John Baldwin