From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
Date: Wed, 31 Mar 2004 19:44:49 +0000
Subject: Re: Abnormal behaviour towards "INIT" interrupt management
Message-Id: <200403311244.49766.bjorn.helgaas@hp.com>
List-Id: <linux-ia64.vger.kernel.org>
References: <40691B80.9070309@Ext.Bull.Net>
In-Reply-To: <40691B80.9070309@Ext.Bull.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-ia64@vger.kernel.org

On Tuesday 30 March 2004 11:43 pm, Francois Wellenreiter wrote:
> All the processors call the "ia64_monarch_init_handler",
> the result is that the same trace appears many times (1 per CPU in fact)
> and a kernel oops occurs (I think it is due to a concurrent access
> to the same stack without any lock mechanism).

What kind of machine is this?  Linux registers different OS_INIT
procedures for the monarch and non-monarch processors, so it
sounds like a SAL bug if more than one CPU calls
ia64_monarch_init_handler().