cache_lock versus getty?
dillon at apollo.backplane.com
Sun Nov 14 13:06:29 PST 2004
:I'm surprised -- I assumed everyone was seeing them. Here are two more
:data points just to make your headache worse ;o)
:I can do 'shutdown now' followed by CTL-D any number of times after boot,
:and I do *not* see the cache_lock messages. It only happens during a
:I tried a GENERIC kernel, just in case, and I still see the lock messages.
:Any other diagnostic maneuvers I should try? (I must say that everything
:seems to be working just great, otherwise: wait-and-see-if-it-goes-away
:might be a viable strategy here :o)
Sorry, I was a bit unclear. I see those cachee_lock messages on getty
as well. I need to do some homework to figure out why they are occuring
but you don't have to ... you can just ignore them.
The cache lock message occurs if a program blocks on a namecache
namespace lock for more then 1 second. As long as there's an unlock
message following there is no problem. This is expected to occur in
certain situations, but I did not expect it to occur on the 'getty'
binary so I have to do some work to figure out why. It could just be
that the disk is busy enough with other things that the lookup on
'getty' stalled for > 1 second.
<dillon at xxxxxxxxxxxxx>
More information about the Kernel