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: 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: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sat, 04 Jul 2009 08:09:17 +0100
Cc:
Delivery-date: Sat, 04 Jul 2009 00:09:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9b5c9bb30907032359h13c37e3en45dd9b100a7e2502@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn8dRslmJbHBDp1Txyrh97fm/5fYwAATzjf
Thread-topic: [Xen-devel] tg3 network stall in xen-3.4.x but not in xen-3.3.x
User-agent: Microsoft-Entourage/12.19.0.090515
On 04/07/2009 07:59, "Teck Choon Giam" <giamteckchoon@xxxxxxxxx> wrote:

>> Certain things are on by default in 3.4 which were not in 3.3. One such
>> thing is MSI. You might try disabling CONFIG_PCI_MSI in your dom0 kernel
>> config. It'll be listed as "Message Signaled Interrupts (MSI and MSI-X)" in
>> the PCI section of the Linux config menus.
> 
> I checked on both configs and both are showing me:
> # CONFIG_PCI_MSI is not set
> 
> I also done a diff for both .config and they are the same.

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

 -- Keir



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