From owner-freebsd-current Wed Sep 5 14:47:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 8396037B40D for ; Wed, 5 Sep 2001 14:47:38 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA10192; Wed, 5 Sep 2001 14:47:32 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010905135040.A398@athlon.pn.xcllnt.net> Date: Wed, 05 Sep 2001 14:47:28 -0700 (PDT) From: John Baldwin To: Marcel Moolenaar Subject: Re: Linuxulator: possible Giant pushdown victim Cc: current@FreeBSD.org 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 05-Sep-01 Marcel Moolenaar wrote: > On Wed, Sep 05, 2001 at 11:04:04AM -0700, John Baldwin wrote: >> >> On 05-Sep-01 Marcel Moolenaar wrote: >> > Hi, >> > >> > I get consistent locks when trying to run Mozilla for Linux (RH 7.1). >> > >> > Breaking into the debugger, I see it hangs in fork_exit()+180. This >> > is should be the PROC_LOCK(p) in the source file (kern_fork.c). >> >> Can you do 'show locks ' where is the pid of the mozilla process? >> Also, what does a 'trace' of the pid in question show? (I take it this is >> how >> you know where it locked up?) > > show locks gives nothing for all cloned mozilla processes. This > strikes me as odd. Another strange thing is that it seems to have a > local effect at first (ie only mozilla hangs), but when trying to > compose an email on the same machine (for example), it locks up hard. > > I give you a complete trace when I call it a day at the office. In the > mean time, this is roughly it (warning, from memory): > > Debugger > ... > intr...kbd > intr...isa > ithread_loop > fork_exit > fork_trampoline > > My guess is that everything beginning with ithread_loop is related to > me breaking into the debugger with CA-ESC. Yes, you can trace indiviudal processes though, using 'trace ', and I'm more curious about the traces of the Mozilla processes. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message