From: Andi Kleen <andi@firstfloor.org>
To: Troy Benjegerdes <hozer@hozed.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Debugging x86_64 apic & bootup problems on the Cray XD1
Date: 12 Mar 2007 12:29:54 +0100 [thread overview]
Message-ID: <p737itmaedp.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070311223802.GB27026@narn.hozed.org>
Troy Benjegerdes <hozer@hozed.org> writes:
> I am attempting to make a 2.6.20 kernel boot on a Cray XD1 node with a
> Mellanox InfiniBand card installed, however both the ancient supplied
> cray 2.6.5 suse derivative, and a 2.6.20 kernel I just booted fail
> on APIC initialization.
>
> Below is a diff of boot-up logs from a node without the mellanox IB
> card, and one with.. Does anyone have some pointers on debug options I
> should start turning on?
apic=debug
But most likely it's not related to the APICs anyways.
Is there some way I can disable some of the
> memory regions in the infiniband card via some early PCI init code
> before APIC's are set up?
Sure, you can code anything. There isn't a standard way to do this
though.
-Andi
prev parent reply other threads:[~2007-03-12 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 22:38 Debugging x86_64 apic & bootup problems on the Cray XD1 Troy Benjegerdes
2007-03-12 11:29 ` Andi Kleen [this message]
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=p737itmaedp.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=hozer@hozed.org \
--cc=linux-kernel@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