From owner-freebsd-current Sat Jun 8 5:10: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id A74CA37B400 for ; Sat, 8 Jun 2002 05:09:57 -0700 (PDT) Received: from kokeb.ambesa.net ([64.166.84.58]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GXD00NGTZ4L41@mta6.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Sat, 08 Jun 2002 05:09:57 -0700 (PDT) Received: from kokeb.ambesa.net (dev1ant@localhost [127.0.0.1]) by kokeb.ambesa.net (8.12.3/8.12.3) with ESMTP id g58CEcaD006940; Sat, 08 Jun 2002 05:14:38 -0700 (PDT envelope-from mikem@kokeb.ambesa.net) Received: (from mikem@localhost) by kokeb.ambesa.net (8.12.3/8.12.3/Submit) id g58CEYmq006939; Sat, 08 Jun 2002 05:14:34 -0700 (PDT envelope-from mikem) Date: Sat, 08 Jun 2002 05:14:33 -0700 From: Mike Makonnen Subject: Fixing "could sleeep..." was (Re: ../../../vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from) In-reply-to: <20020608110340.41492.qmail@web21110.mail.yahoo.com> To: hiten@uk.FreeBSD.org Cc: jrh@lab.it.uc3m.es, freebsd-current@FreeBSD.ORG Message-id: <200206081214.g58CEYmq006939@kokeb.ambesa.net> MIME-version: 1.0 X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i386--freebsd5.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20020608110340.41492.qmail@web21110.mail.yahoo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 08 Jun 2002 04:03:40 -0700 (PDT) Hiten Pandya wrote: > --- Juan Francisco Rodriguez Hervella 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