From owner-freebsd-smp  Tue Nov 25 18:58:27 1997
Return-Path: <owner-freebsd-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA06685
          for smp-outgoing; Tue, 25 Nov 1997 18:58:27 -0800 (PST)
          (envelope-from owner-freebsd-smp)
Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06674
          for <freebsd-smp@freebsd.org>; Tue, 25 Nov 1997 18:58:23 -0800 (PST)
          (envelope-from fbsd@Ilsa.StevesCafe.com)
Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1])
	by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id TAA24316;
	Tue, 25 Nov 1997 19:58:01 -0700 (MST)
Message-Id: <199711260258.TAA24316@Ilsa.StevesCafe.com>
X-Mailer: exmh version 2.0gamma 1/27/96
From: Steve Passe <smp@csn.net>
To: Mark Murray <mark@grondar.za>
cc: ben@stuyts.nl, freebsd-smp@freebsd.org
Subject: Re: "apic_ipi might be stuck" getting worse 
In-reply-to: Your message of "Tue, 25 Nov 1997 22:14:18 +0200."
             <199711252014.WAA04358@greenpeace.grondar.za> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Nov 1997 19:58:01 -0700
Sender: owner-freebsd-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,
> Ben Stuyts wrote:
> > A few days ago I reported seeing the message "apic_ipi might be stuck". Since > then I've seen it more and more, about 4-5 times a day. I can't find anything
> > in the mailing list over the past few months about this. What does this  
> > message mean, and can it do any harm? The system function normally otherwise.
> 
> The author of this (I'm sorry - I cannot remember who you are) has said 
> that the criteria for determining this is (may be) flawed.
> 
> So far, I have had _no_ problems with this.
> 
> I await the (cosmetic) fix :-)

You really don't have to worry until it says "apic_ipi is stuck".
Then, any good silicone based lubricant will work.  I prefer the type that
comes im a spray can.  I can usually get it on the apic without opening
the case...

Seriuosly, you can just ignore it.  If it bugs you comment out the printf
in the source.

--
Steve Passe	| powered by 
smp@csn.net	|            Symmetric MultiProcessor FreeBSD