000Mbps it syncs at boot.
Hopefully this is helpful in understanding why the workaround is no
longer required.
Thanks all
Neil
On Mon, 29 Apr 2019 at 04:55, Neil MacLeod wrote:
>
> Phil
>
> Many thanks - you've nailed it!
>
> Reverting the workaround from Heiner, and also
onger required.
Thanks all
Neil
On Mon, 29 Apr 2019 at 04:20, Phil Reid wrote:
>
> On 29/04/2019 6:05 am, Neil MacLeod wrote:
> > Hi Heiner
> >
> > 5.0.6 is the first kernel that does NOT require the workaround.
> >
> > In 5.0.6 the only obvious r8169 change
moving
> the workaround because it seems now (at least since 5.1-rc1) we're fine.
>
> Heiner
>
> On 28.04.2019 20:40, Neil MacLeod wrote:
> > Hi Heiner
> >
> > I'd already kicked off a 5.0.2 build without the workaround and I've
> > tested that no
e been in a different corner. On my hardware
> I'm not able to reproduce the issue. It's not that relevant with which
> exact version the issue vanished. Based on your results I'll just
> remove the workaround on net-next (adding your Tested-by).
>
> Heiner
>
>
Hi Heiner
Do you know if this is already fixed in 5.1-rc6 (Linus Torvalds tree),
as in order to test your request I thought I would reproduce the issue
with plain 5.1-rc6 with the workaround removed, however without the
workaround 5.1-rc6 is resuming correctly at 1000Mbps.
I went back to 4.19-rc4
Since 4.19-rc1 (up to and including 4.19-rc3) there is now a problem
with the r8169 network interface when resuming from suspend - the
negotiated network speed after resume is only 10Mbit/s half-duplex.
There is no problem with 4.18.y, and when booting into 4.19-rc3 from
power-on the full 1000Mbit
