Re: "witness exhausted"
From: John Baldwin (jhb_at_FreeBSD.org)
Date: 08/23/04
- Previous message: John Baldwin: "Re: "witness exhausted""
- In reply to: Robert Huff: ""witness exhausted""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: freebsd-current@FreeBSD.org Date: Mon, 23 Aug 2004 14:59:15 -0400
On Monday 23 August 2004 02:09 pm, Robert Huff wrote:
> I updated to
>
> FreeBSD 6.0-CURRENT #1: Fri Aug 20 15:02:58 EDT 2004
>
> and noticed in the boot messages:
>
> witness_get: witness exhausted
>
> What's going on, and is this something I need to worry about?
> (System config file and dmesg output are appended.)
It just means that witness' internal buffers were used up so it stopped doing
lock order checking. You can try bumping up the constants in subr_witness.c
that control the size of the static arrays if you need witness to work. You
can do a 'show witness' from DDB to possibly see why it exhausted all the
entries. It may be that some class of lock is using unique names for each
lock and needs to use a common lock type so they all use the same witness
structure.
-- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: John Baldwin: "Re: "witness exhausted""
- In reply to: Robert Huff: ""witness exhausted""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|