Haipeng Shen <[EMAIL PROTECTED]> writes: > This is the end of the output from "dmesg". It seems like having to do > with afs. This might be caused the expired tokens in afs.
I'd actually say the opposite -- there's nothing there that really touches on AFS. I was somewhat hoping to see a kernel BUG or deadlock warning, as that would make this much easier to track down. The messages from dmesg aren't timestamped, so it's hard to know how long ago the token expiration happened. However, in general, token expiration is normal and expected and always logs a message like that. I wouldn't suspect that unless the timing coincides. Although it's still a possibility. If you can get to your syslog (or other system log) file, could you see when that afs message was logged and if it is at all close to when the system started behaving strangely? I suspect some sort of lock deadlock is happening, although I don't know if AFS is the culprit. I don't suppose you know if this happens if you run the system without AFS loaded, so that we can know with more certainty? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
