Date: Wed, 10 Jul 2002 12:26:19 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Don Lewis <dl-freebsd@catspoiler.org> Cc: zipzippy@sonic.net, current@FreeBSD.ORG Subject: Re: What to do with witness verbiage (is this new?)? Message-ID: <20020710172619.GB86282@dan.emsphone.com> In-Reply-To: <200207100943.g6A9hswr006550@gw.catspoiler.org> References: <20020710075421.GA4924@blarf.homeip.net> <200207100943.g6A9hswr006550@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 10), Don Lewis said: > On 10 Jul, Alex Zepeda wrote> After the rude awakening that I was after all running current, I've > > finally turned on the WITNESS related options for my kernel (and boy is it > > wickedly unstable as of now). > > I haven't had any instability problems in a while on my UP box. > > > Anyways.. is there any sort of list of > > known warnings? I'm seeing a few consistantly relating to "pcm0:play:0", > > "pcm0", "inp", "tcp", and "kernel linker". The pcm related ones are well > > known, right? > > I don't have the pcm hardware. The only WITNESS message I consistently > see is the kernel linker one. > > > The most recent one I'm seeing (that I'd never seen before) is this: > > > > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from ../../../kern/kern_exec.c:332 > > I haven't seen that one. If you can reproduce it, you might try setting > the debug.witness_ddb sysctl to 1 and get a stack trace from ddb. I see this one once every 10 seconds or so: ../../../vm/uma_core.c:1332: could sleep with "inp" locked from ../../../netinet/tcp_subr.c:935 ../../../vm/uma_core.c:1332: could sleep with "tcp" locked from ../../../netinet/tcp_subr.c:928 -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020710172619.GB86282>