From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [BUG] igb: reconnecting of cable not always detected
Date: Thu, 17 Jan 2019 13:55:07 -0800 [thread overview]
Message-ID: <CAL3LdT5DV1faoFsX6CH4LRSQa9rn-Eg71sRu64=bs3w7WCGg4g@mail.gmail.com> (raw)
In-Reply-To: <87603lbelc.fsf@gmail.com>
On Fri, May 18, 2018 at 12:36 AM Holger Schurig <holgerschurig@gmail.com> wrote:
>
> Alexander Duyck <alexander.duyck@gmail.com> writes:
> > Thanks for the data. It is actually useful. There are a few things
> > that I see that seem to point to an obvious issue.
>
> Any news on this?
>
> A collegue of mine states (I have not checked this) that a kernel
> 4.9.0-6-686 from a Debian Live ISO (debian-live-9.4.0-i386-kde.iso)
> didn't show this behavior, so we have some kind of regression perhaps?
Our validation team was only able to reproduce this once, but is not
able to reproduce the issue again or even consistently to be able to
adequate debug the issue.
Are you still seeing the issue with the latest upstream kernel from
either David Miller's net-next tree or Linus's tree?
--
Cheers,
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [BUG] igb: reconnecting of cable not always detected
Date: Thu, 17 Jan 2019 13:55:07 -0800 [thread overview]
Message-ID: <CAL3LdT5DV1faoFsX6CH4LRSQa9rn-Eg71sRu64=bs3w7WCGg4g@mail.gmail.com> (raw)
In-Reply-To: <87603lbelc.fsf@gmail.com>
On Fri, May 18, 2018 at 12:36 AM Holger Schurig <holgerschurig@gmail.com> wrote:
>
> Alexander Duyck <alexander.duyck@gmail.com> writes:
> > Thanks for the data. It is actually useful. There are a few things
> > that I see that seem to point to an obvious issue.
>
> Any news on this?
>
> A collegue of mine states (I have not checked this) that a kernel
> 4.9.0-6-686 from a Debian Live ISO (debian-live-9.4.0-i386-kde.iso)
> didn't show this behavior, so we have some kind of regression perhaps?
Our validation team was only able to reproduce this once, but is not
able to reproduce the issue again or even consistently to be able to
adequate debug the issue.
Are you still seeing the issue with the latest upstream kernel from
either David Miller's net-next tree or Linus's tree?
--
Cheers,
Jeff
next prev parent reply other threads:[~2019-01-17 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 15:14 [BUG] igb: reconnecting of cable not always detected Holger Schurig
2018-04-24 15:14 ` [Intel-wired-lan] " Holger Schurig
2018-04-24 18:09 ` Alexander Duyck
2018-04-24 18:09 ` [Intel-wired-lan] " Alexander Duyck
2018-04-25 3:30 ` Richard Cochran
2018-04-25 3:30 ` [Intel-wired-lan] " Richard Cochran
2018-04-25 9:47 ` Holger Schurig
2018-04-25 9:47 ` [Intel-wired-lan] " Holger Schurig
2018-04-25 16:01 ` Alexander Duyck
2018-04-25 16:01 ` [Intel-wired-lan] " Alexander Duyck
2018-04-26 7:54 ` Holger Schurig
2018-04-26 7:54 ` [Intel-wired-lan] " Holger Schurig
2018-04-26 9:08 ` Holger Schurig
2018-04-26 9:08 ` [Intel-wired-lan] " Holger Schurig
2018-04-26 16:02 ` Alexander Duyck
2018-04-26 16:02 ` [Intel-wired-lan] " Alexander Duyck
2018-04-27 10:39 ` Holger Schurig
2018-04-27 10:39 ` [Intel-wired-lan] " Holger Schurig
2018-05-18 7:35 ` Holger Schurig
2018-05-18 7:35 ` [Intel-wired-lan] " Holger Schurig
2019-01-17 21:55 ` Jeff Kirsher [this message]
2019-01-17 21:55 ` Jeff Kirsher
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='CAL3LdT5DV1faoFsX6CH4LRSQa9rn-Eg71sRu64=bs3w7WCGg4g@mail.gmail.com' \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=holgerschurig@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.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.