From owner-freebsd-bugs@FreeBSD.ORG  Thu May 28 18:12:26 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A706A5A2
 for <freebsd-bugs@FreeBSD.org>; Thu, 28 May 2015 18:12:26 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9238D3D5
 for <freebsd-bugs@FreeBSD.org>; Thu, 28 May 2015 18:12:26 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4SICQEP033926
 for <freebsd-bugs@FreeBSD.org>; Thu, 28 May 2015 18:12:26 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 200493] Killing pid 11 (idle) wedges the disk IO
Date: Thu, 28 May 2015 18:12:26 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200493-8-Zjq629v3zk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200493-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-200493-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Thu, 28 May 2015 18:12:26 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200493

--- Comment #3 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Edward Tomasz Napierala from comment #2)
No, bug report is weird because it does not contain even an attempt to get an
overview of the system state after it enters the un-understandable condition. 
ps auxwwH, procstat, looking for the threads eating 100% cpus, stopped clocks,
whatever.

As I said, I killed my idle process and did not see any change in the system
behavior.

The 'enter' key ticking some processing might indicate problems with stopped
event clocks or clock interrupts.  E.g. network interrupts coming in could have
similar effect ?

Anyway, collect as much as possible of the overview information for the system
before and after the killing, and see what changed.

-- 
You are receiving this mail because:
You are the assignee for the bug.