Date: Tue, 06 Feb 2001 08:36:43 +0200 From: Mark Murray <mark@grondar.za> To: John Baldwin <jhb@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <200102060636.f166aJC38816@gratis.grondar.za> In-Reply-To: <XFMail.010205204642.jhb@FreeBSD.org> ; from John Baldwin <jhb@FreeBSD.ORG> "Mon, 05 Feb 2001 20:46:42 PST." References: <XFMail.010205204642.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin said: > On 06-Feb-01 Andrea Campi wrote: > > > Sorry to bother everybody, but did anybody note from my panic trace, > > that instruction pointer is 0xdeadc0de? Isn't that bad? :-p > > That means it is free'd memory. One cause might be something > that is free'ing its interrupt handler w/o releasing it properly. > Alternatively, it might be a race in the interrupt list code that was > been brought about by preemption. Since locks are rather expensive, > we have avoided locking the list of interrupt handlers in the past, > but we may have to break down and do that now. :( This will hurt > interrupt latency unless I can figure out a slick way of fixing it. > Can anyone confirm that a pre-preemption kernel works fine for them? I have 2 SMP boxes (one with pentium 200MMX's, the other with PPro 233's. There are other differences in peripherals). Both boxes run an identical build of a kernel dating to sun 4th feb. The PPro is rock-stable. The PentiumMMX is very fragile, and will panic easily (often in vm_fault) with a sig9 (IIRC). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102060636.f166aJC38816>