From: Rusty Russell <rusty@rustcorp.com.au>
To: Sean Young <sean@mess.org>
Subject: Re: Regression: boot failure on AMD Elan TS-5500
Date: Mon, 16 Jun 2008 23:27:34 +1000
User-Agent: KMail/1.9.9
Cc: linux-kernel@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>,
       "H. Anvin" <hpa@zytor.com>
References: <20080616121138.GA51097@atlantis.8hz.com>
In-Reply-To: <20080616121138.GA51097@atlantis.8hz.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200806162327.34912.rusty@rustcorp.com.au>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1001
Lines: 30

On Monday 16 June 2008 22:11:39 Sean Young wrote:
> The symptons are either a crash or reboot on booting the kernel. No
> printk's have occurred yet -- even with early printk on.
>
> 2.6.15 worked on this board however current does not. I've bisected it to:
>
> 	commit a24e785111a32ccb7cebafd24b1b1cb474ea8e5d
> 	Author: Rusty Russell <rusty@rustcorp.com.au>
> 	Date:   Sun Oct 21 16:41:35 2007 -0700
>
> 	    i386: paravirt boot sequence

Hi Sean,

   Thanks for tracking this down.  Can we try reverting this in pieces to see 
exactly what the cause was?

1) Revert arch/x86/boot/compressed/head_32.S
2) If that doesn't fix it, Try removing the 8 lines which were added to 
arch/x86/kernel/head_32.S

I assume this is CONFIG_PARAVIRT=n?

Thanks,
Rusty.
--
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/