Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site dual.UUCP
Path: utzoo!linus!security!genrad!mit-eddie!mit-vax!eagle!harpo!seismo!hao!hplabs!hpda!fortune!amd70!dual!fair
From: fair@dual.UUCP (Erik E. Fair)
Newsgroups: net.unix-wizards
Subject: Re: panic from interrupt stack loses
Message-ID: <204@dual.UUCP>
Date: Wed, 4-Jan-84 00:03:47 EST
Article-I.D.: dual.204
Posted: Wed Jan  4 00:03:47 1984
Date-Received: Sat, 31-Dec-83 01:13:05 EST
References: <14854@sri-arpa.UUCP>
Organization: Dual Systems, Berkeley, CA
Lines: 21


Another annoying thing about panic in this vein:

	On our s-100 68000 System, we use some disk controllers (not by
	choice, I assure you) that LATCH their interrupts, so that you
	have to tell them to shut up. When you panic in the interrupt
	service routine of any of these devices, guess what? The panic
	keeps coming back again, and again...

	Since panic does an update(), is it assumed that disk drivers
	never panic? Didn't the PDP-11 ever have hardware that was brain
	damaged in this fashion?

	In the driver that I wrote for just such a board, I was
	eventually forced to write a quick macro for panic(), that
	printed a message and then went while(1); if for no other
	reason than to be able to read the panic message that I
	originally got...

	Erik E. Fair	{ucbvax,amd70,zehntel,unisoft,onyx,its}!dual!fair
			Dual Systems Corporation, Berkeley, California