linux-kernel - Re: Debugging x86_64 apic & bootup problems on the Cray XD1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <p737itmaedp.fsf@bingen.suse.de>
Date:	12 Mar 2007 12:29:54 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Troy Benjegerdes <hozer@...ed.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Debugging x86_64 apic & bootup problems on the Cray XD1

Troy Benjegerdes <hozer@...ed.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/