From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
Subject: Re: ethtool doesnt work on some interface after
	unbinding dpdk
Date: Fri, 29 Apr 2016 18:23:37 -0700
Message-ID: <CABK1yFB9mBz9kdLM9VFoC2LMZU1FyyP16G09rwyPijs1U3ckcA@mail.gmail.com>
References: <CABK1yFCzog23fW=7pm3+Gg3twtYdF_05TH=5oojCa1Wcw3Y6Pw@mail.gmail.com>
 <570F4383.7040003@intel.com>
 <CABK1yFCBhwaGbFEXvw5cTX1Zydt7ej70QL7cPe4LiT4TUmo7pQ@mail.gmail.com>
 <57109D32.70506@intel.com>
 <CABK1yFC0VLEHOaawqjo61RPpdJR7P-DjTGPpbL9oZJ4Vuk3tpg@mail.gmail.com>
 <CABK1yFA-7cxhTBJ4Nij8WX7Q8B6nY+fgs-HWudqgHwhOBSV0rQ@mail.gmail.com>
 <CABK1yFDVVMjBxiYFP6KzjODtsRc0H+scrvHJszYV_mhscXDpjQ@mail.gmail.com>
 <5714B219.7080202@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: dev@dpdk.org
To: Remy Horton <remy.horton@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-io0-f173.google.com (mail-io0-f173.google.com
 [209.85.223.173]) by dpdk.org (Postfix) with ESMTP id 1A5FB530C
 for <dev@dpdk.org>; Sat, 30 Apr 2016 03:23:38 +0200 (CEST)
Received: by mail-io0-f173.google.com with SMTP id 190so118441305iow.1
 for <dev@dpdk.org>; Fri, 29 Apr 2016 18:23:38 -0700 (PDT)
In-Reply-To: <5714B219.7080202@intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Just to update this thread. With power management for IGB disabled, this
problem is not seen .. So for now thats the "workaround"

Rgds,
Gopa.

On Mon, Apr 18, 2016 at 3:08 AM, Remy Horton <remy.horton@intel.com> wrote:

>
> On 15/04/2016 23:56, Gopakumar Choorakkot Edakkunni wrote:
>
>> This time the problem statement is more narrowed down.
>>
>> 1. dpdk is enabled on the interface, interfaces bound to igb_uio
>> 3. kill the process using dpdk
>> 3. rmmod rte_kni
>> 4. rmmod igb_uio
>> 5. bind interface to igb
>> 6. ethtool, ifconfig up/down etc.. works for approximately 30 seconds,
>> and then stops working
>>
>
> Hmm.. can you try that but with rte_kni left out completely? KNI hooks
> into the Linux network stack and think it at the least needs eliminating as
> a casual factor. Can you also try using uio_pci_generic rather than igb_uio?
>
> Those aside, I'm suspecting driver issues, so seeing if I can get one of
> the driver test guys to have a look at this..
>
>
> Regards,
>
> ..Remy
>