Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: dupuy@columbia.edu (Alexander Dupuy)
Newsgroups: comp.sys.sun
Subject: panic: hat_unload -- What's this mean
Message-ID: <8901241818.AA08048@cs.columbia.edu>
Date: 3 Feb 89 15:04:40 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 9
Approved: Sun-Spots@rice.edu
Original-Date: Tue, 24 Jan 89 13:18:36 EST
X-Sun-Spots-Digest: Volume 7, Issue 138, message 5 of 10

I've seen the same panic on our Sun-2/170 running 4.0.1.  "hat" stands for
hashed address table, but beyond that I couldn't say.  We have also had a
wierd panic every time we boot our 2/120s under 4.0[.1].  Just before
vmunix starts probing for devices, right after it sizes memory, we get a
"panic: hat_unlock".  After it (tries to) write a crash dump, it
(auto)boots normally.  We haven't ever seen this on our 2/170, though.
Could it be a CPU board rev problem which only our ancient 2/120s have?

@alex