Hi Eric,
On Thu, May 26, 2016 at 06:08:22AM -0700, Eric Dumazet wrote:
> On Thu, 2016-05-26 at 16:41 +0800, Feng Tang wrote:
> > On Wed, May 25, 2016 at 07:53:41PM -0400, David Miller wrote:
>
> > >
> > > But now that we have at least two instances of this code we really
> > > need to put a comm
From: Feng Tang
Date: Thu, 26 May 2016 16:41:55 +0800
> Maybe the driver maintainer from Atheros could take a look, as they
> can reach all the real HWs :)
Don't hold your breath.
On Thu, 2016-05-26 at 16:41 +0800, Feng Tang wrote:
> On Wed, May 25, 2016 at 07:53:41PM -0400, David Miller wrote:
> >
> > But now that we have at least two instances of this code we really
> > need to put a common version somewhere. :-/
>
> I agree, and furthermore I noticed there are some sim
On Wed, May 25, 2016 at 07:53:41PM -0400, David Miller wrote:
> From: Feng Tang
> Date: Wed, 25 May 2016 14:49:54 +0800
>
> > This patch follows Eric Dumazet's commit 7b70176421 for Atheros
> > atl1c driver to fix one exactly same bug in alx driver, that the
> > network link will be lost in 1-5 m
From: Feng Tang
Date: Wed, 25 May 2016 14:49:54 +0800
> This patch follows Eric Dumazet's commit 7b70176421 for Atheros
> atl1c driver to fix one exactly same bug in alx driver, that the
> network link will be lost in 1-5 minutes after the device is up.
>
> My laptop Lenovo Y580 with Atheros AR8
This patch follows Eric Dumazet's commit 7b70176421 for Atheros
atl1c driver to fix one exactly same bug in alx driver, that the
network link will be lost in 1-5 minutes after the device is up.
My laptop Lenovo Y580 with Atheros AR8161 ethernet device hit the
same problem with kernel 4.4, and it w
