DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
To: Remy Horton <remy.horton@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] ethtool doesnt work on some interface after unbinding dpdk
Date: Fri, 15 Apr 2016 12:31:00 -0700	[thread overview]
Message-ID: <CABK1yFA-7cxhTBJ4Nij8WX7Q8B6nY+fgs-HWudqgHwhOBSV0rQ@mail.gmail.com> (raw)
In-Reply-To: <CABK1yFC0VLEHOaawqjo61RPpdJR7P-DjTGPpbL9oZJ4Vuk3tpg@mail.gmail.com>

So looks like I figured it out .. I came across this bug reference
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728692 and thought of
checking out my problem with ACPI turned off. And with ACPI turned off, the
problem doesnt happen. So theres something that the igb driver is not happy
about when acpi is on .. Any thoughts ?

Rgds,
Gopa.

On Fri, Apr 15, 2016 at 10:38 AM, Gopakumar Choorakkot Edakkunni <
gopakumar.c.e@gmail.com> wrote:

> Nothing in dmesg .. The ethtool was just a side-observation, the biggest
> problem was that after unbinding from igb_uio and rebinding to igb, if I
> follow it up with an /etc/init.d/network restart, that completely hoses the
> linux system - anyone trying to open a socket (ifconfig for example) just
> hangs. Thats how I started troubleshooting this and happened to see this
> ethtool thing along with it, not sure if its related. Also the issue
> doesn't happen with one or two interfaces, there needs to be at least five
> or six interfaces for this to happen.
>
> The other thing I noticed is that if I put some sleep (2 seconds) between
> unbind igb_uio and re-bind igb, the network-restart-hosing-system doesnt
> happen, but the ethtool issue still remains
>
> Rgds,
> Gopa.
>
> On Fri, Apr 15, 2016 at 12:50 AM, Remy Horton <remy.horton@intel.com>
> wrote:
>
>> On 14/04/2016 20:25, Gopakumar Choorakkot Edakkunni wrote:
>> [..]
>>
>>> ge8----->   06:00.0 Ethernet controller: Intel Corporation 82576 Gigabit
>>> Network Connection (rev 01)
>>>
>>> root:~# ls /sys/class/net/ge8/device/driver/module/drivers/
>>> pci:igb
>>> root:~#
>>>
>>> root:~# ethtool ge8
>>> Settings for ge8:
>>> Cannot get device settings: No such device
>>> Cannot get wake-on-lan settings: No such device
>>> Cannot get message level: No such device
>>> Cannot get link status: No such device
>>> No data available
>>>
>>
>> Seems a little odd. Does dmesg show anything related to igb/ixgbe when
>> you try this?
>>
>> ..Remy
>>
>
>

  reply	other threads:[~2016-04-15 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 14:48 Gopakumar Choorakkot Edakkunni
2016-04-14  7:15 ` Remy Horton
2016-04-14 19:25   ` Gopakumar Choorakkot Edakkunni
2016-04-15  7:50     ` Remy Horton
2016-04-15 17:38       ` Gopakumar Choorakkot Edakkunni
2016-04-15 19:31         ` Gopakumar Choorakkot Edakkunni [this message]
2016-04-15 22:56           ` Gopakumar Choorakkot Edakkunni
2016-04-18 10:08             ` Remy Horton
2016-04-30  1:23               ` Gopakumar Choorakkot Edakkunni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABK1yFA-7cxhTBJ4Nij8WX7Q8B6nY+fgs-HWudqgHwhOBSV0rQ@mail.gmail.com \
    --to=gopakumar.c.e@gmail.com \
    --cc=dev@dpdk.org \
    --cc=remy.horton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).