WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Thu, 19 Feb 2009 10:17:53 -0800 (PST)
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Marc - A. Dahlhaus \[ Administration | Westermann GmbH \]" <mad@xxxxxx>
Delivery-date: Thu, 19 Feb 2009 10:18:23 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1235067473; bh=QNnPw83uRf+dSCaXrsWJ0sTVE/dec4lUfEO0sZIOh+A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=nufAeNADPDuboBTr7L8jmWZxD1TBDSnjSJWyngQsM85c938QPIetcrRFIfqVZ1/vBuePCoKYn9a6nvkenLr6UMNQPOq+zSExK92+AdeyFnjjkg7gTRiCkBZ30t6p82xOjn2vxLEfuCMui0LSjkLaUXZwNG6DXx5IPnSb2qrn2mE=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=coWGKE0j8+aQ/GDMAmwvbQCP765ZbFfu04sNeWPDp7L/6bibKWYW7rZJ3QucZazh7GJcg3TUDI+g2FHwOgfe01IDBqGWMJe2ysVENRA4WdxHpEefaUVJiYkvMFEKl+UCMaMSCdVF1iPvfQ9YymkI5t6+NAeYBnitKNXySqJ02kY=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <499D971C.7020304@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bderzhavets@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Just in case, i did same snapshot on my box :-

root@ServerXen331:~# cat /proc/interrupts
           CPU0       CPU1      
  1:       2382          0  xen-pirq-pirq      i8042
  4:         23            0  xen-pirq-pirq   
  8:          0             0  xen-pirq-pirq      rtc0
  9:          0             0  xen-pirq-pirq      acpi
 16:          0            0  xen-pirq-pirq      ahci, uhci_hcd:usb1, eth1
 17:    1484598      0  xen-pirq-pirq      pata_jmicron, peth0
 18:     303892       0  xen-pirq-pirq      uhci_hcd:usb3, uhci_hcd:usb6, ehci_hcd:usb7
 19:          3            0  xen-pirq-pirq      uhci_hcd:usb5, ohci1394
 21:          0            0  xen-pirq-pirq      uhci_hcd:usb2
 22:     369205       0  xen-pirq-pirq      ahci, HDA Intel
 23:          2            0  xen-pirq-pirq      uhci_hcd:usb4, ehci_hcd:usb8
 24:    1763255      0   xen-dyn-virq      timer0
 25:       4802         0   xen-dyn-ipi       spinlock0
 26:     111735       0   xen-dyn-ipi       resched0
 27:          0            0   xen-dyn-ipi       callfunc0
 28:          0            0   xen-dyn-virq      debug0
 29:        194          0   xen-dyn-ipi       callfuncsingle0
 30:          0    1763173   xen-dyn-virq      timer1
 31:          0      14283   xen-dyn-ipi       spinlock1
 32:          0     155653   xen-dyn-ipi       resched1
 33:          0            0   xen-dyn-ipi       callfunc1
 34:          0            0   xen-dyn-virq      debug1
 35:          0         866   xen-dyn-ipi       callfuncsingle1
 36:      11249        0   xen-dyn-event     xenbus
 38:       6301         0   xen-dyn-event     evtchn:xenstored
 39:         21           0   xen-dyn-event     evtchn:xenstored
 40:        221          0   xen-dyn-event     evtchn:xenstored
 41:          5            0   xen-dyn-event     evtchn:qemu-dm
 42:        985          0   xen-dyn-event     evtchn:qemu-dm
 43:         68           0   xen-dyn-event     evtchn:qemu-dm
 44:       2672         0   xen-dyn-event     blkif-backend
 45:         24           0   xen-dyn-event     vif8.0
NMI:          0          0   Non-maskable interrupts
LOC:          0          0   Local timer interrupts
CNT:          0          0   Performance counter interrupts
RES:     111736     155653   Rescheduling interrupts
CAL:        194        866   Function call interrupts
TLB:          0          0   TLB shootdowns
SPU:          0          0   Spurious interrupts
ERR:          0
MIS:           0


--- On Thu, 2/19/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
To: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Cc: bderzhavets@xxxxxxxxx, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@xxxxxx>
Date: Thursday, February 19, 2009, 12:30 PM

Andrew Lyon wrote:
> I built from the git tree this morning and still get the same ahci and
> piix problems on my test box (a dell optiplex 755), is that problem
> supposed to be fixed?
>

Try now. Gerd noticed a pretty major bug in interrupt setup, and fixing it has
made AHCI work for me. It will likely fix your piix.

J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>