Re: Cache-lock.

[walt <wa1ter@xxxxxxxxxxxxx>]

On Sat, 2 Oct 2004, Matthew Dillon wrote:
>
>     The 'blocked on' messages are ok as long as there is also an "...unblocked"
>     message after it.  If there isn't then the process could be deadlocked
>     in which case it would be great if you could get a kernel core &
>     kernel.debug that I could look at.

I have a reproducible 'blocked on lib' message with no 'unblocked':

I nfs-mount (read-only) a linux machine and attempt to run the linux mozilla
from that machine.  I can tell you  when I try the same from FreeBSD I get
a typical missing library error (no surprises there).

Just to avoid confusion about the MOZILLA_HOME variable I invoke the program
this way:

# cd /mnt/usr/local/lib/mozilla-1.8a5/
# ./run-mozilla.sh ./mozilla-bin

This is so easy to reproduce I thought maybe you can do it yourself.  If
not, I'll compile a debugging kernel here and give you the data.

For the kernel core you mean just hit ctl-alt-esc (or whatever the keys
ought to be) anytime after the 'blocked' happens?  BTW ps axl shows this:
1001   854   850   9 157   0  1216  344 clock  DL+   p3    0:00.00 ./mozilla-bin