Re: Cache-lock.

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:I have -CURRENT from today's morning (build Sat Oct  2 12:14:34 CEST 2004). 
:All compiles correctly, system is booting up cleary and so on. 
:
:But later, after trying to run any 'bigger' application (firefox, staroffice),
:I have message like that:
:Oct  2 14:05:22 insomniac kernel: [diagnostic] cache_lock: blocked on
:
:In the first case (firefox), I'm able to close X, but unable to kill firefox-bin,
:and - strange - I can't even do 'ls' in /usr/local (firefox is in /usr/local/firefox).
:In second case (staroffice), system just hangs.
:
:I've tested it just on that two 'big' applications, and both of them are on linux emulation.
:I don't have any big native soft, but all 'light', like mpg123 etc. works fine.
:
:Any ideas?
:
:-- 
:Bartek Stalewski // werbat@xxxxxxxxxxxxxxx

    There are definitely still some issues with stage 7.  I haven't gotten
    any crashes yet but I am definitely getting some incorrect lookups.  I'm
    working on it.

    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.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>