Re: Current stalls...(now also panic)
Szilveszter, 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 :-) Thanks, ed 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
Re: Current stalls...(now also panic)
Mark, Thanks a lot. I read Marc's mail first so I'm trying the -k solution first but I will also take USB support out of the kernels that have it. Thanks, ed Mark Hittinger wrote: > > 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. > > I see this also. If you aren't using USB but have it compiled into your > kernel try commenting out all the "device" entries after "# USB support" > in the config file. A kernel built without USB may not show the hangs. > > I think there is a buglet that has krept into the USB code within the > last couple of weeks. > > Later > > Mark Hittinger > Earthlink > [EMAIL PROTECTED] > > 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
Re: Current stalls...(now also panic)
On Fri, Dec 29, 2000 at 10:57:10PM +0100, 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...) I see the same panic. I managed to collect some info in kern/23935. http://www.freebsd.org/cgi/query-pr.cgi?pr=23935 I can reliably reproduce it. -- Alex Kapranoff, Voice: +7(0832)791845 36 hours before the brand new millenium... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current stalls...(now also panic)
On Fri, Dec 29, 2000 at 04:02:08PM -0800, Thomas D. Dean wrote: > I have a -current stall or hang, also. > > I do NOT have USB support in my kernel. > > Running gdb on hello.c, the standard hello, world, will cause the > stall or hang. Keyboard input is echoed, but, no action. > > tomdean No, no USB devices (nor USB support in the kernel.) Also, I was not trying to use gdb (I tried that two days ago, with strikingly similar results though:-) This panic is somewhat elusive: I cannot readily trigger it it seems. Will stress system to see what gives. BTW: I do not know if it was intentional but I see a *lot* fewer pcm0: hwptr went backwards messages with very recent -CURRENT and indeed sound output is a lot more continous, even under load. Congrats to whoever did it! (probably cg) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current stalls...(now also panic)
I have a -current stall or hang, also. I do NOT have USB support in my kernel. Running gdb on hello.c, the standard hello, world, will cause the stall or hang. Keyboard input is echoed, but, no action. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current stalls...(now also panic)
> 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. I see this also. If you aren't using USB but have it compiled into your kernel try commenting out all the "device" entries after "# USB support" in the config file. A kernel built without USB may not show the hangs. I think there is a buglet that has krept into the USB code within the last couple of weeks. Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current stalls...(now also panic)
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
