Date: Thu, 8 Feb 2001 01:27:45 +0100 From: Andrea Campi <andrea@webcom.it> To: Jake Burkholder <jburkholder0829@home.com> Cc: John Baldwin <jhb@FreeBSD.ORG>, Jim Bloom <bloom@acm.org>, "Crist J. Clark" <cjclark@reflexnet.net>, current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208012740.A3525@webcom.it> In-Reply-To: <20010207235341.C22E2BAB0@cr66388-a.rchrd1.on.wave.home.com>; from jburkholder0829@home.com on Wed, Feb 07, 2001 at 06:53:41PM -0500 References: <andrea@webcom.it> <20010207235341.C22E2BAB0@cr66388-a.rchrd1.on.wave.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> This is why you're getting the panic in exit1(), but I thought I fixed
> this in intr_machdep.c version 1.47.
>
> revision 1.47
> date: 2001/01/28 17:20:11; author: jake; state: Exp; lines: +2 -1
> Clear intr_nesting_level when an interrupt thread has no more
> handlers and wants to exit, so it doesn't panic in exit1()
> which malloc()s with M_WAITOK.
Well, either it fails to deliver, but then somebody else would have
seen it, or it's in some way tied to my hw setup. Could there be a
race, an interrupt firing at a very bad time? Shouldn't be a problem
if locking is correct...
Bah... any idea?
Andrea
--
The dark ages were caused by the Y1K problem.
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?20010208012740.A3525>