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/
Home Products Support Community News


RE: [Xen-devel] tg3 network stall in xen-3.4.x but not in xen-3.3.x

To: Teck Choon Giam <giamteckchoon@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] tg3 network stall in xen-3.4.x but not in xen-3.3.x
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Date: Sun, 5 Jul 2009 22:36:39 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Sun, 05 Jul 2009 14:37:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9b5c9bb30907041956t5369a584g4cc86eee89ebf0db@xxxxxxxxxxxxxx>
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: <9b5c9bb30907032359h13c37e3en45dd9b100a7e2502@xxxxxxxxxxxxxx> <C674BEAD.EEC2%keir.fraser@xxxxxxxxxxxxx> <9b5c9bb30907040030m332f0634t13d608976894e4b0@xxxxxxxxxxxxxx> <9b5c9bb30907041956t5369a584g4cc86eee89ebf0db@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn9HG/znEaB0i6VSWKHxS2LsznFFwAmm4rg
Thread-topic: [Xen-devel] tg3 network stall in xen-3.4.x but not in xen-3.3.x
> >> Power management is another difference between 3.3 and 3.4. You can
> disable
> >> 3.4 power management by adding Xen boot parameters: cpuidle=0
> cpufreq=none
> > I will disable and run the test tomorrow to see whether network stall
> > issue is there or not.
> Using cpuidle=0 cpufreq=none seems to solve the network stall problem.

Hmm, that's rather disturbing. Its presumably the cpuidle parameter which is 
having the effect. Quite why deeper sleep states can result in one particular 
device interrupt getting stuck (as opposed to all of them) is a mystery. It 
might be interesting to see the boot messages, and also to find out which of 
the C states is causing the problem (presumably C2 or C3).

In your tests, rather than rebooting the machine you may possibly be able to 
recover the machine by unloading and reloading the NIC module. (you may need to 
remove it from the bridge and ifconfig it down first).


Xen-devel mailing list