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 <pid>' where <pid> 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 <pid> 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 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
