> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup Jake Burkholder
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup Alexander N. Kabaev
- Re: Kernel Panic from Yesterday's CVSup Jake Burkholder
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVSup Warner Losh