From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ACPI: Uninitialized spinlocks & Unable to dump stack
Date: Wed, 01 Aug 2007 13:33:41 +0000 [thread overview]
Message-ID: <yq0zm1bfkga.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707312246390.14878@schroedinger.engr.sgi.com>
>>>>> "Kenji" = Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> writes:
Kenji> Hi,
Kenji> I don't know why no IOSAPIC entries was found on your system.
Kenji> But I think the cause of this stack trace is a bug in the code
Kenji> path of interrupt registering failure. Here is a patch to fix
Kenji> this bug. Could you try that?
Hi Kenji,
The answer to your first comment is simple - we don't have any in the
system :-)
Cheers,
Jes
next prev parent reply other threads:[~2007-08-01 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 5:48 ACPI: Uninitialized spinlocks & Unable to dump stack Christoph Lameter
2007-08-01 12:18 ` Kenji Kaneshige
2007-08-01 13:33 ` Jes Sorensen [this message]
2007-08-01 16:00 ` Russ Anderson
2007-08-01 20:02 ` Christoph Lameter
2007-08-01 20:34 ` Russ Anderson
2007-08-02 1:06 ` Keith Rich
2007-08-02 1:37 ` Keith Rich
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=yq0zm1bfkga.fsf@jaguar.mkp.net \
--to=jes@sgi.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