From owner-freebsd-current Wed Sep 5 13:50:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 3D20637B403; Wed, 5 Sep 2001 13:50:41 -0700 (PDT) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f85Koef03426; Wed, 5 Sep 2001 13:50:40 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.11.6/8.11.5) id f85KoeD00459; Wed, 5 Sep 2001 13:50:40 -0700 (PDT) (envelope-from marcel) Date: Wed, 5 Sep 2001 13:50:40 -0700 From: Marcel Moolenaar To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Linuxulator: possible Giant pushdown victim Message-ID: <20010905135040.A398@athlon.pn.xcllnt.net> References: <20010905100651.A5560@gauss.cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i 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 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. When I get back home again, I'll try this on Alpha as well. The Alpha has already got a serial console, so it's easier to experiment at this time. Please standby... :-) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message