Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757365AbYGHXtk (ORCPT ); Tue, 8 Jul 2008 19:49:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753993AbYGHXtc (ORCPT ); Tue, 8 Jul 2008 19:49:32 -0400 Received: from gw.goop.org ([64.81.55.164]:50986 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753570AbYGHXtb (ORCPT ); Tue, 8 Jul 2008 19:49:31 -0400 Message-ID: <4873FD00.1060101@goop.org> Date: Tue, 08 Jul 2008 16:49:20 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: "Eric W. Biederman" CC: Mike Travis , "H. Peter Anvin" , Christoph Lameter , Linux Kernel Mailing List , Ingo Molnar , Andrew Morton , Jack Steiner Subject: Re: [crash, bisected] Re: [PATCH 3/4] x86_64: Fold pda into per cpu area References: <20080604003018.538497000@polaris-admin.engr.sgi.com> <48691556.2080208@zytor.com> <48691E8B.4040605@sgi.com> <48694B3B.3010600@goop.org> <486A61A7.1000902@zytor.com> <486A68DD.80702@goop.org> <486A9D4F.8010508@goop.org> <486AA72B.6010401@goop.org> <486AC9D9.9030506@zytor.com> <486AD6BD.9080600@sgi.com> <486ADD67.1020809@sgi.com> <486ADD9F.3000305@zytor.com> <486C062C.3090408@sgi.com> <48724FB4.3090305@sgi.com> <4873B016.8010404@sgi.com> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 960 Lines: 25 Eric W. Biederman wrote: > Mike Travis writes: > > >> Unfortunately it's back to the problem of faulting before x86_64_start_kernel() >> and grub just immediately reboots. So I'm back at analyzing assembler and >> config differences. >> > > Ok. That is a narrow window of code. So it shouldn't be too bad, nasty though. > > If you would like to trace through it I have attached my serial port > debugging routines that I use in that part of the code. Last time it was doing this, it was a result of a triple-fault caused by loading %ds with an all-zero gdt. I modified Xen to dump the CPU state on triple-faults, so it was easy to pinpoint. I can do that again if it helps. J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/