I've got some other weird problems with cores and panics but vi is the only
one that I can define well enough.  I'm also taking all USB support from the
kernels that have it to see if my other strange problems disappear like access
to mysql databases with php4 cvs and some strange library problems that I am
having with my new XFree4.0.2_3 with kde-2.0.1 and LinuxNetscape that I just
installed on Dec. 31. (Poor timing, but sorting these things out is what makes
life interesting :-)



Szilveszter Adam wrote:

> Hi!
> Maybe this is related, maybe not... I upgraded to the latest CURRENT
> available this morning and now I also see occasional (albeit short) hangs
> sometimes, although the machine seems to be responsive otherwise.
> But, not only that, I also got a cool panic while trying to do some stuff
> (like compiling the docs) and pressing Ctrl-Z in another tty. No X, no
> nothing. I was dropped into the debugger, but since I am not a ddb artist,
> I tried to avoid to type the whole trace by hand and in the process managed
> to reboot the box... oh well. Next time I will know.
> But, the panic message was this:
> panic: blockable mtx_enter() of lockmgr interlock when not legal @
> ../../kern/kern_lock.c:247
> Maybe this rings a bell with someone. The error was appearently caught by
> WITNESS, which I also have enabled in my kernel (albeit without
> MUTEX_DEBUG, because *that* really made it impossible to do anything
> sensible on the machine...)
> Hardware-wise, nothing fancy here... UP PII-233, 128M non-ECC RAM, all-IDE,
> two disks, one CD-ROM. Next time, I promise to write down all the
> details... but just wanted to chime in quickly since this might be related
> to the hangs other people are seeing, but maybe they don't panic() because
> they don't have WITNESS enabled (just speculating)
> --
> Regards:
> Szilveszter ADAM
> Szeged University
> Szeged Hungary
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to