All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fujinaka, Todd <todd.fujinaka@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] igb: Random NIC down for 3-4 seconds and then UP
Date: Wed, 9 Jun 2021 15:09:48 +0000	[thread overview]
Message-ID: <BYAPR11MB3606E7E70D2E3B2E58BD06CDEF369@BYAPR11MB3606.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6b36112fc1548f06a737bc7a1febaac06f799b6a.camel@intel.com>

Usually things like this are hardware-related when dealing with mature drivers.

Is there any way you can file this through your factory support because we're going to need a lot more detail. We don't usually handle issues through email unless you want to go through Intel Customer Support.

We'll need to know OS, driver, hardware, link partner, kind of traffic, etc.

Thanks.

Todd Fujinaka
Software Application Engineer
Data Center Group
Intel Corporation
todd.fujinaka at intel.com

-----Original Message-----
From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of Nguyen, Anthony L
Sent: Tuesday, June 8, 2021 4:19 PM
To: intel-wired-lan@osuosl.org; mantykuma at gmail.com
Subject: Re: [Intel-wired-lan] igb: Random NIC down for 3-4 seconds and then UP

On Fri, 2021-06-04 at 14:42 +0900, manty kuma wrote:
> We see random NIC down like shown below. It lasts for a few seconds 
> and then the connection is back up.
> 
> From kernel Log:
> ```
> [ 3306.560431] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Down [ 
> 3309.532558] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up
> 1000 Mbps Full Duplex, Flow Control: RX\/TX
> 
> [ 3337.380117] igb 0000:02:00.0 enp2s0: igb: enp2s0 NIC Link is Down [ 
> 3341.672189] igb 0000:02:00.0 enp2s0: igb: enp2s0 NIC Link is Up
> 100 Mbps Half Duplex, Flow Control: None ``` Steps to reproduce: 
> Unknown. Happens randomly
> Frequency: once in a couple of weeks so far.
> 
> Kernel: 5.10
> Firmware version: 3.25, 0x800005cf
> driver: igb
> 
> Is it a known issue?
> What can we do to better understand the reason for this behavior and 
> fix it?

Hi Manty,

I'm not aware of this as a known issue, but I've filed an internal bug so that it can be looked into further. Could you provide the lspci info for the device? Also, if you have any info that might be helpful such as occuring under traffic or when idle, etc.

Thanks,
Tony

> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan at osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2021-06-09 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  5:42 [Intel-wired-lan] igb: Random NIC down for 3-4 seconds and then UP manty kuma
2021-06-08 23:19 ` Nguyen, Anthony L
2021-06-09 15:09   ` Fujinaka, Todd [this message]

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=BYAPR11MB3606E7E70D2E3B2E58BD06CDEF369@BYAPR11MB3606.namprd11.prod.outlook.com \
    --to=todd.fujinaka@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.