From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Abnormal behaviour towards "INIT" interrupt management
Date: Wed, 31 Mar 2004 19:44:49 +0000 [thread overview]
Message-ID: <200403311244.49766.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <40691B80.9070309@Ext.Bull.Net>
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().
next prev parent reply other threads:[~2004-03-31 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 7:02 Abnormal behaviour towards "INIT" interrupt management Francois Wellenreiter
2004-03-30 15:19 ` Bjorn Helgaas
2004-03-30 18:52 ` Luck, Tony
2004-03-31 6:37 ` Francois Wellenreiter
2004-03-31 6:43 ` Francois Wellenreiter
2004-03-31 19:44 ` Bjorn Helgaas [this message]
2004-04-01 3:23 ` Jim Garlick
2004-04-01 6:26 ` Francois Wellenreiter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200403311244.49766.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox