From owner-freebsd-current Mon Feb 5 22:36:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id EF88137B491; Mon, 5 Feb 2001 22:36:26 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f166aJC38816; Tue, 6 Feb 2001 08:36:23 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200102060636.f166aJC38816@gratis.grondar.za> To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup References: In-Reply-To: ; from John Baldwin "Mon, 05 Feb 2001 20:46:42 PST." Date: Tue, 06 Feb 2001 08:36:43 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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