Date: Tue, 06 Mar 2001 16:08:44 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: David Malone <dwmalone@maths.tcd.ie> Cc: Dag-Erling Smorgrav <des@ofug.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa apic_vector.s icu_vector.s Message-ID: <XFMail.010306160844.jhb@FreeBSD.org> In-Reply-To: <200103062350.aa85798@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06-Mar-01 David Malone wrote: >> Yeah, cause the stack is hosed it looks like. Hrmmmm. Add the following >> options to your kernel: > >> options KTR >> options KTR_EXTEND >> options KTR_COMPILE=0x1208 > >> Then before you do a buildworld, run the followign command as root: > >> # sysctl -w debug.ktr.mask=0x1200 > >> Then run the buildworld and crash teh machine. :-P The type 'show ktr' to >> get >> a list of the various interrupts and process changes that occured up until >> things blew up. If you have a serial console and can knab that output that > > Ok - I managed to get a panic. I don't have a serial console, but > I think it may have provided a hint anyway. "show ktr" turned up alot > of entries of the form: > > 755: ithread_schedule: pid 12: it_need 1, state 2 > 754: ithread_schedule: pid 12: (swi6: tty:sio+) need 1 > 753: swi_sched pid 12(swi6: tty:sio+) need=1 > > I presume this is because there is a Rugby Radio clock reciever > wired to the DCD pin of one of the serial ports. I'm monitoring > the asserts and clears on this pin. These are timed in userland > using the functions provided in sys/timepps.h - it should only > cause 3 or 4 interrupts per second at most. Think this could > be part of triggering the problem? No, the other handler on that swi is the softclock handler. This just means you are getting clock interrutps from the i8254, which is good. :) We just happen to hang one of the swi's for the sio driver off of the clock software interrupt thread. > (Otherwise, I can try to figure out what the ktr output it telling > me. Any hints on what I'm looking for?) Well, what process was running when it panic'd for example? Did it resume from a tsleep() or was it an ithread started after preemption? > David. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010306160844.jhb>