Date: Tue, 07 Feb 2012 11:50:09 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Julian Elischer <julian@FreeBSD.org> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org>, FreeBSD Current <current@FreeBSD.org> Subject: Re: kernel debugging and ULE Message-ID: <4F30F3D1.4060600@FreeBSD.org> In-Reply-To: <4F2F6ABA.2020809@freebsd.org> References: <4F2F6ABA.2020809@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F30F3D1.4060600>