From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Re: NX related build failure in latest pv_ops dom0
	hackery tree
Date: Thu, 16 Apr 2009 15:27:01 -0700
Message-ID: <49E7B0B5.4070003@goop.org>
References: <20090404192338.GJ24960@edu.joroinen.fi>	
	<49D840D4.1070701@goop.org>
	<1239555359.12706.4.camel@leto.intern.saout.de>	
	<49E4BF6F.2010308@goop.org>	
	<1239887761.30384.13.camel@leto.intern.saout.de>	
	<49E7591E.3030402@goop.org>
	<1239919531.8028.31.camel@leto.intern.saout.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1239919531.8028.31.camel@leto.intern.saout.de>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christophe Saout <christophe@saout.de>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Christophe Saout wrote:
> Hi Jeremy,
>
> just got the netconsole output from the machine, and yes, it's the AHCI
> initialisation problem.  The older "hackery" kernel didn't boot either
> (didn't check if it's the same problem).
>   

That would be interesting to know.  push2/xen/dom0/master would also be 
an interesting result.

> I've put the log up here:
> http://www.saout.de/assets/xen-next-tip-boot-1-log.txt
>
> (ignore the crash at the end, it somehow does that if the initramfs
> fails to find the root filesystem)
>
> Also, what I haven't seen before are slowpath warnings in
> xan_apic_write.
>
> The
> 	ata1: softreset failed (device not ready)
> 	ata1: failed due to HW bug, retry pmp=0
>
> also appear during the regular boot process, but the IDENTIFY afterworks
> then succeeds.
>
> Otherwise the kernel messages from native and Xen kernel are practically
> identical (except for the fundamental differences in the setup of
> course).
>   

OK, thanks.  I'm tending towards some kind of interrupt setup.  I wonder 
if there's any difference in how we're trying to set things up.  
Certainly there's been lots of changes in mainline in that area.

    J