Date: Sat, 08 Jun 2002 05:14:33 -0700 From: Mike Makonnen <makonnen@pacbell.net> To: hiten@uk.FreeBSD.org Cc: jrh@lab.it.uc3m.es, freebsd-current@FreeBSD.ORG Subject: Fixing "could sleeep..." was (Re: ../../../vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from) Message-ID: <200206081214.g58CEYmq006939@kokeb.ambesa.net> In-Reply-To: <20020608110340.41492.qmail@web21110.mail.yahoo.com> References: <Pine.LNX.3.96.1020608124323.3596A-100000@lm002.lab.it.uc3m.es> <20020608110340.41492.qmail@web21110.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 08 Jun 2002 04:03:40 -0700 (PDT)
Hiten Pandya <hitmaster2k@yahoo.com> wrote:
> --- Juan Francisco Rodriguez Hervella <jrh@lab.it.uc3m.es> wrote:
> > ../vm/uma_core.c:1160
> > ../../../vm/uma_core.c:1327: could sleep with "process lock" locked
from> > ../../../kern/kern_prot.c:511
> > ../../../vm/uma_core.c:1327: could sleep with "process lock" locked
from>
> > Hope this help. Do you think these errors are alarming ?
> > I mean, do you recommend me to recopile my kernel again ?
> > (please noooooo, it takes me a lot of time to recompile whatever
thing :)>
I also get these and I figured they're as good an excuse as any to jump
into the kernel code :-} This particular one (and others related to the
setuid/gid family of functions) occur because some time after PROC_LOCK
is called in set{uid,euid} and further down the call stack uidfind()
allocates some memory specifying the M_WAITOK flag.
Is the solution to this to use M_NOWAIT and continue re-trying untill it
succeeds? Is there on-going smp work in locking down struct proc that
will eliminate this problem?
Cheers,
Mike Makonnen
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?200206081214.g58CEYmq006939>