RE: [Xen-devel] FW: Xen 4.1 interrupts not delievered.

["Lin, Ray" <Ray.Lin@xxxxxxx>]

The dom0/domU kernel also affect it. 
dom0 kernel :  2.6.32.18-pvops-stable
domU kernel :  2.6.36-rc6-pvops-kpcif-08


-Ray

-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx] 
Sent: Monday, October 18, 2010 7:59 AM
To: Lin, Ray
Cc: bruce.edge@xxxxxxxxx; linux@xxxxxxxxxxxxxx; caker@xxxxxxxxxxxx; 
xen-devel@xxxxxxxxxxxxxxxxxxx; keir@xxxxxxx; Ian.Campbell@xxxxxxxxxxxxx; 
m.a.young@xxxxxxxxxxxx; jeremy@xxxxxxxx; pasik@xxxxxx
Subject: Re: [Xen-devel] FW: Xen 4.1 interrupts not delievered.

On Fri, Oct 15, 2010 at 02:57:44PM -0600, Lin, Ray wrote:
>  
>   We experienced the domU interrupt/DMA issue before. The symptom is like the 
> /proc/interrupts/irq# of Tachyon chip (FC controller) keep on incrementing, 
> but nobody is serving the interrupts. Eventually the count of these unserved 
> interrupts reach the max. and are forced to be disabled.  With Konrad's 
> dom0/domU configuration, this issue is resolved now.

Can you send the old dom0/domU configuration? I am really curious as of why it 
would work - the configuration for domU was just mostly made minimal to boot a 
tiny kernel, and the dom0 was based on Ubuntu/Fedora Core 13 and then enabling 
all of the Xen options.


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