Message-ID: <48566C88.6000702@goop.org>
Date: Mon, 16 Jun 2008 06:37:12 -0700
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Rusty Russell <rusty@rustcorp.com.au>
CC: Sean Young <sean@mess.org>, linux-kernel@vger.kernel.org,
       "H. Anvin" <hpa@zytor.com>
Subject: Re: Regression: boot failure on AMD Elan TS-5500
References: <20080616121138.GA51097@atlantis.8hz.com> <200806162327.34912.rusty@rustcorp.com.au>
In-Reply-To: <200806162327.34912.rusty@rustcorp.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1231
Lines: 37

Rusty Russell wrote:
> 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
>   
And the arch/x86/boot/compressed/misc_32.c change too, just in case...

> I assume this is CONFIG_PARAVIRT=n?

What bootloader does this platform use?  I wonder if it's setting things 
up in an unexpected way?

    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/