Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Feb 2002 02:53:07 +0000 (UTC)
From:      naddy@mips.inka.de (Christian Weisgerber)
To:        freebsd-alpha@freebsd.org
Subject:   Re: -CURRENT lockups
Message-ID:  <a5c8uj$fr$1@kemoauc.mips.inka.de>
References:  <a59h09$149$1@kemoauc.mips.inka.de> <20020224140250.GG64936@cicely8.cicely.de> <a5b5o5$2gg$1@kemoauc.mips.inka.de> <20020224180950.GA69066@cicely8.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter <ticso@cicely8.cicely.de> wrote:

> If it's realy with a lockmgr lock you should enable debugging for it:
> options         KTR
> options         KTR_EXTEND
> options         KTR_ENTRIES=1024
> options         KTR_COMPILE="(KTR_LOCKMGR)"
> options         KTR_MASK=KTR_LOCKMGR
> options         KTR_CPUMASK=0x3
> options         KTR_VERBOSE

This doesn't seem realistic.  Just how often is lockmgr() called?

> In case it's to chatty on booting you can set KTR_MASK to 0 and enable
> it later with sysctl debug.ktr.mask=0x00020000.

Well, after an hour the boot hasn't gone anywhere.

-- 
Christian "naddy" Weisgerber                          naddy@mips.inka.de


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5c8uj$fr$1>