From owner-freebsd-stable@FreeBSD.ORG Wed Feb 8 10:28:21 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 E2063106564A; Wed, 8 Feb 2012 10:28:21 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id AE0BC8FC08; Wed, 8 Feb 2012 10:28:21 +0000 (UTC) Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id q18ASHr1052113 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 8 Feb 2012 02:28:20 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4F324E93.50303@freebsd.org> Date: Wed, 08 Feb 2012 02:29:39 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.26) Gecko/20120129 Thunderbird/3.1.18 MIME-Version: 1.0 To: Andriy Gapon References: <4F2F6ABA.2020809@freebsd.org> <4F30F3D1.4060600@FreeBSD.org> In-Reply-To: <4F30F3D1.4060600@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable , FreeBSD Current Subject: Re: kernel debugging and ULE 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: Wed, 08 Feb 2012 10:28:22 -0000 On 2/7/12 1:50 AM, Andriy Gapon wrote: > on 06/02/2012 07:52 Julian Elischer said the following: >> so if I'm sitting still in the debugger for too long, a hardclock >> event happens that goes into ULE, which then hits the following KASSERT. >> >> >> KASSERT(pri>= PRI_MIN_BATCH&& pri<= PRI_MAX_BATCH, >> ("sched_priority: invalid priority %d: nice %d, " >> "ticks %d ftick %d ltick %d tick pri %d", >> pri, td->td_proc->p_nice, td->td_sched->ts_ticks, >> td->td_sched->ts_ftick, td->td_sched->ts_ltick, >> SCHED_PRI_TICKS(td->td_sched))); >> >> >> The reason seems to be that I've been sitting still for too long and things have >> become pear shaped. >> >> >> how is it that being in the debugger doesn't stop hardclock events? >> is there something I can do to make them not happen.. >> It means I have to ge tmy debugging done in less than about 60 seconds. >> >> suggesions welcome. > Does this really happen when you just sit in the debugger? > Or does it happen when you let the kernel run? Like stepping through the code, > etc.... > good point.. I was doing some single stepping..