From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Build vmlinuz-2.6.29-rc5-tip Date: Wed, 18 Feb 2009 14:39:44 -0800 Message-ID: <499C8E30.1020104@goop.org> References: <20090217131120.GZ15052@edu.joroinen.fi> <250247.41545.qm@web56108.mail.re3.yahoo.com> <20090217135717.GA15052@edu.joroinen.fi> <499B04B6.7050306@goop.org> <20090218214813.GC15052@edu.joroinen.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090218214813.GC15052@edu.joroinen.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Ian Campbell , Boris Derzhavets , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen wrote: > On Tue, Feb 17, 2009 at 10:40:54AM -0800, Jeremy Fitzhardinge wrote: > =20 >> Pasi K=E4rkk=E4inen wrote: >> =20 >>> On Tue, Feb 17, 2009 at 05:31:57AM -0800, Boris Derzhavets wrote: >>> =20 >>> =20 >>>> Hardware config:- >>>> C2D E8400, 8 GB RAM, ASUS P5K Premium/WIFI (Intel P35+Intel ICH9R), >>>> 2x250 SATA Seagate Barracuda (no RAID). Bios settings for ICH9R - AH= CI. >>>> Details here:- >>>> http://bderzhavets.wordpress.com/2009/02/17/setup-xen-unstable-dom0-= via-2629-rc5-pv_ops-enabled-kernel-on-intel-sataahci/ >>>> >>>> =20 >>>> =20 >>> Thanks! >>> >>> So it seems you're running 64 bit dom0 OS/hypervisor..=20 >>> >>> 64 bit seems to work better atm than 32 bit..=20 >>> =20 >>> =20 >> I tend to focus on 64-bit, and Ian Campbell has been looking at 32-bit= . =20 >> In theory there shouldn't be all that much difference between them. =20 >> There have been a few issues, but they're sharing 90+% of the code. (= In=20 >> practice I'm interested in any bug reports, esp comparing 32 and 64-bi= t=20 >> behaviour). >> >> =20 > > I'm testing 32bit PAE dom0 on 32bit PAE hypervisor.=20 > > Today, with 2.6.29-rc5, I managed to boot my dom0 into login prompt!=20 > I haven't been able to get this working earlier.. congratulations! > > I had to use 'noapic' dom0 kernel parameter though.. without 'noapic' I= 'm seeing > the same IRQ problems with ata_piix than earlier. > =20 Hm, interesting. One change I made in the last few days was making gsis=20 map 1:1 with irqs, like the native kernel. I wonder if that helps in=20 your case. That said, I'm not quite sure how its working with noapic; I=20 would have thought that it wouldn't go through the Xen-hooked paths that=20 way... Oh, you're using ahci, not piix - and that works with noapic. Hm, I=20 should try that. Can you start xend and a domain? > My dom0 kernel config: > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.29-rc5-tip-do= m0 > > My grub.conf: > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/grub.conf > > Working dom0 bootlog with 'noapic': > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-13-x= en331-linux-2.6.29-rc5-noapic.txt > =20 What does your /proc/interrupts look like in this case? > Failing dom0 bootlog (without 'noapic'): > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-12-x= en331-linux-2.6.29-rc5.txt > =20 Do you think you could boot from a usb device or something and see if=20 you can get /proc/interrupts for this as well? Thanks, J