Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Oct 2011 13:36:05 +0200
From:      =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To:        Alexander Motin <mav@FreeBSD.org>
Cc:        current@freebsd.org
Subject:   Re: 9 hangs with idletick = 0
Message-ID:  <86lispaztm.fsf@ds4.des.no>
In-Reply-To: <86botmjf7p.fsf@ds4.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8rg?= =?utf-8?Q?rav=22's?= message of "Wed, 12 Oct 2011 19:24:10 %2B0200")
References:  <86bou59gpf.fsf@ds4.des.no> <4E83186C.4080707@FreeBSD.org> <86botmjf7p.fsf@ds4.des.no>

next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Sm=C3=B8rgrav <des@des.no> writes:
> I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR
> and KTR_SCHED enabled by default.  I'll see what turns up.  I'm also
> going to try machdep.idle=3Dhlt with kern.eventtimer.idletick=3D0, and us=
ing
> a PCI re(4) instead of the on-board msk(4) while running with default
> settings.

Great, the bug does not occur when KTR is enabled.  The machine has been
up for 14+ hours without crashing, despite plenty of network activity,
which usually triggers a freeze within minutes.

It looks like there may still be short freezes (a few seconds at a
time).  I'm thinking of instrumenting fetch(1) to record any instances
of fread() taking more than, say, half a second.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86lispaztm.fsf>