|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
Re: [Xen-devel] FW: Xen 4.1 interrupts not delievered.
 
| 
To:  | 
"Lin, Ray" <Ray.Lin@xxxxxxx> | 
 
| 
Subject:  | 
Re: [Xen-devel] FW: Xen 4.1 interrupts not delievered. | 
 
| 
From:  | 
Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> | 
 
| 
Date:  | 
Mon, 18 Oct 2010 10:59:24 -0400 | 
 
| 
Cc:  | 
"jeremy@xxxxxxxx" <jeremy@xxxxxxxx>,	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>,	"keir@xxxxxxx" <keir@xxxxxxx>,	"bruce.edge@xxxxxxxxx" <bruce.edge@xxxxxxxxx>,	"Ian.Campbell@xxxxxxxxxxxxx" <Ian.Campbell@xxxxxxxxxxxxx>,	"linux@xxxxxxxxxxxxxx" <linux@xxxxxxxxxxxxxx>,	"m.a.young@xxxxxxxxxxxx" <m.a.young@xxxxxxxxxxxx> | 
 
| 
Delivery-date:  | 
Mon, 18 Oct 2010 08:02:42 -0700 | 
 
| 
Envelope-to:  | 
www-data@xxxxxxxxxxxxxxxxxxx | 
 
| 
In-reply-to:  | 
<EB4C61A1A2501842A04B573FE42B14D601319D0DDD@xxxxxxxxxxxxxxxxx> | 
 
| 
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> | 
 
| 
References:  | 
<EB4C61A1A2501842A04B573FE42B14D601319D0DDD@xxxxxxxxxxxxxxxxx> | 
 
| 
Sender:  | 
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx | 
 
| 
User-agent:  | 
Mutt/1.5.20 (2009-06-14) | 
 
 
 
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
 
 |   
 
 | 
    | 
  
  
    |   | 
    |