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] tg3 network stall in xen-3.4.x but not in xen-3.3.x

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] tg3 network stall in xen-3.4.x but not in xen-3.3.x
From: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
Date: Sat, 4 Jul 2009 15:30:37 +0800
Delivery-date: Sat, 04 Jul 2009 00:31:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=/JfoNPn6+eKwr0KT+uxW+lOz2G8XVh7WxTIqg8zCTFw=; b=n0ZB42FcLifF2uJ6xqeNj0USY8QCcy9/C4fyWG4SkmiHC+oWIh3w2JISioYMHz2/2F jFws8RACNb8ytXblVj31jKEESqnVZjpAzv76tMafNyhDgbuDE4wuhTHE4eIiwqWwntaN Id2kSznOkf2yEz2JHs9+RtpQ2uysJH3UEpU5o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Vo8iI3RRhsrcDtELZMlLQX4ZwM+Hbo6r59U6RqRpsnU20BHD/CCt+Gk7FRxHV49EsA F820ozI/mk4gT4/uIv4vfP4PudxgbaiyzIjd/1+9qs4YKBdQur5MZUMJ0lAbU9SonwfA kKleHdUVJ4fCmsbsWyzFctpV/7I99VVXgDnbs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C674BEAD.EEC2%keir.fraser@xxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Keir,

> 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

In xen-3.3.x I got:

# xenpm get-cpuidle-states
Xen cpuidle is not enabled!
Xen cpufreq is not enabled!

In xen-3.4.x I got:

# xenpm get-cpuidle-states
Max C-state: C1

cpu id               : 0
total C-states       : 2
idle time(ms)        : 131588676
C0                   : transition [00000000000019346170]
                       residency  [00000000000003897999 ms]
C1                   : transition [00000000000019346170]
                       residency  [00000000000131507268 ms]

cpu id               : 1
total C-states       : 2
idle time(ms)        : 131696919
C0                   : transition [00000000000012247741]
                       residency  [00000000000003766854 ms]
C1                   : transition [00000000000012247741]
                       residency  [00000000000131638414 ms]

cpu id               : 2
total C-states       : 2
idle time(ms)        : 131540647
C0                   : transition [00000000000013405442]
                       residency  [00000000000003922680 ms]
C1                   : transition [00000000000013405442]
                       residency  [00000000000131482588 ms]

cpu id               : 3
total C-states       : 2
idle time(ms)        : 131527968
C0                   : transition [00000000000031194790]
                       residency  [00000000000004030618 ms]
C1                   : transition [00000000000031194790]
                       residency  [00000000000131374650 ms]

I will disable and run the test tomorrow to see whether network stall
issue is there or not.

Thanks.

Kindest regards,
Giam Teck Choon

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