From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Thimo E." <abc@digithi.de>
Subject: Re: cpuidle and un-eoid interrupts at the local apic
Date: Wed, 14 Aug 2013 09:51:17 +0200
Message-ID: <520B36F5.9010205@digithi.de>
References: <51A908CA.7050604@citrix.com><51F8CB15.1070608@digithi.de><51F8DD40.2090207@citrix.com><51FC37A9.9090809@digithi.de><51FC418D.8020708@citrix.com><51FFBA8502000078000E9462@nat28.tlf.novell.com><51FFBC08.6070804@citrix.com>
	<52055EC9.8030207@digithi.de><5208B6DE02000078000EB08E@nat28.tlf.novell.com><5208AACF.7050901@citrix.com><5208CF9702000078000EB1F2@nat28.tlf.novell.com><5208B88F.1030002@citrix.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0A8E3191@SHSMSX104.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <abc@digithi.de>) id 1V9Vri-0002H8-6m
	for xen-devel@lists.xenproject.org; Wed, 14 Aug 2013 07:51:34 +0000
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A8E3191@SHSMSX104.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xenproject.org>
List-Id: xen-devel@lists.xenproject.org

Hello,

on last reboot i've disabled interrupt remapping, since then it did not 
crash (but the crashes happened somewhere between 3 hours to 7 days). So 
still waiting if that option helped.

Here the masterplan from my conclusions out of this thread:
1) If the server crashes again I'll enable dom0_max_vcpus=1 and 
dom0_vcpus_pin.
Could that problem also be a driver error ? Another idea is to update 
the e1000e driver from 2.3.2-NAPI to 2.4.14 ?!

2) I have two Intel NICs in the server, one onboard and one PCIe NIC. 
The crash seems to come from the onboard device. So If the server 
crashes again I'll disable that internal Intel NIC and put another PCIe 
network card in it.

Best regards
   Thimo

Am 14.08.2013 04:53, schrieb Zhang, Yang Z:
>
> Did you see the issue on other HSW machine without this NIC? Also, Thimo, have you tried to pin the vcpu and stop irqbalance in dom0?
>