From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: NX related build failure in latest pv_ops dom0 hackery tree Date: Thu, 16 Apr 2009 09:34:14 -0700 Message-ID: <49E75E06.1060702@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> <1239899080.30384.138.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: In-Reply-To: <1239899080.30384.138.camel@leto.intern.saout.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christophe Saout Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Christophe Saout wrote: > Hi Jeremy, > > >>> I could try to compile netconsole and the NIC driver into the kernel to >>> capture the kernel messages if that would help. >>> >> Well, I've tried it on a newish Intel mobo machine with on-board ahci, >> and that fails. Another, older, Dell machine using a scsi controller >> works fine. I haven't tried my laptop yet. >> >> In theory AHCI is ACHI, so the controller vendor shouldn't matter. It >> may have more to do with interrupt controller configuration or memory >> layout. >> >> On your failing machine, does it work any better if you switch the >> controller to compat/legacy mode? >> > > I only have network and remote reset possibility and to boot from a > network rescue system, so sorry, can't test that. > > I will try to get some kernel messages and also check if the latest > hackery kernel boots. > Actually, the kernel to test is xen-tip/next. That's going to be the base for ongoing development, and I'll cull all the rest of the branches once all their nutritious changesets have been extracted. Oh, and it actually works. J