From owner-freebsd-current@FreeBSD.ORG Tue Feb 7 09:50:16 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2B5210656A4; Tue, 7 Feb 2012 09:50:16 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A25658FC1A; Tue, 7 Feb 2012 09:50:15 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA15619; Tue, 07 Feb 2012 11:50:12 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Ruhgi-000OC2-8A; Tue, 07 Feb 2012 11:50:12 +0200 Message-ID: <4F30F3D1.4060600@FreeBSD.org> Date: Tue, 07 Feb 2012 11:50:09 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0) Gecko/20120202 Thunderbird/10.0 MIME-Version: 1.0 To: Julian Elischer References: <4F2F6ABA.2020809@freebsd.org> In-Reply-To: <4F2F6ABA.2020809@freebsd.org> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable , FreeBSD Current Subject: Re: kernel debugging and ULE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2012 09:50:16 -0000 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.... -- Andriy Gapon