driver/net/usb/r8152 stop working after some time with kernel 5.10-rc series

driver/net/usb/r8152 stop working after some time with kernel 5.10-rc series

[Milan P. Stanić]

Hi,

[ I'm not subscribed to list so please Cc to me
  and sorry if this is not polite ]

I'm using driver r8152 'Realtek Semiconductor Corp. RTL8153 Gigabit
Ethernet Adapter' (that is what lsusb shows) which is included in
external usb-c dongle which is listed as 'VIA Labs, Inc. USB3.0 Hub'.

Driver loads and work some time but at unpredictable time it stops and
starts to flood 'dmesg' output until shutdown (eth) interface.

Machine where I test this is arm64 ACER R13 chromebook.

'dmesg' shows a lot of such messages:

[305186.211284] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211367] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211450] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211533] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211615] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211698] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211781] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211863] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.211951] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212034] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212117] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212200] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212282] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212365] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212448] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212530] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212613] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212696] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212778] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212861] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.212948] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213032] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213115] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213197] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213280] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213362] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213445] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213528] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213610] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213693] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213776] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213859] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.213941] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
[305186.214028] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11

-- 
Kind regards

Re: driver/net/usb/r8152 stop working after some time with kernel 5.10-rc series

[Oliver Neukum]

Am Samstag, den 14.11.2020, 13:55 +0100 schrieb Milan P. Stanić:
> 

Hi,

> Driver loads and work some time but at unpredictable time it stops and
> starts to flood 'dmesg' output until shutdown (eth) interface.
> 
> Machine where I test this is arm64 ACER R13 chromebook.

Are you sure this started in v5.10 or did you not try earlier kernels?

> 'dmesg' shows a lot of such messages:
> 
> [305186.211284] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11

EAGAIN is an unusual error return.

	Regards
		Oliver

Re: driver/net/usb/r8152 stop working after some time with kernel 5.10-rc series

[Milan P. Stanić]

Hi,

On Mon, 2020-11-16 at 15:06, Oliver Neukum wrote:
> Am Samstag, den 14.11.2020, 13:55 +0100 schrieb Milan P. Stanić:
> Hi,
> 
> > Driver loads and work some time but at unpredictable time it stops and
> > starts to flood 'dmesg' output until shutdown (eth) interface.
> > 
> > Machine where I test this is arm64 ACER R13 chromebook.
> 
> Are you sure this started in v5.10 or did you not try earlier kernels?

I never used much mainline kernels on this machine because previous
kernels had issues and quirks making them practically unusable.
Earlier I used old chromeOS kernel (3.18 series) and from July this
summer I switched to kernels from
https://gitlab.collabora.com/eballetbo/linux/-/tree/topic/chromeos/somewhat-stable-5.7
https://gitlab.collabora.com/eballetbo/linux/-/tree/topic/chromeos/somewhat-stable-5.8
https://gitlab.collabora.com/eballetbo/linux/-/tree/topic/chromeos/somewhat-stable-5.9

They had also some issues but on somewhat-stable-5.8 and
somewhat-stable-5.9 r8152 worked, or I missed to notice this problem.

First mainline kernel which works fine is 5.10-rc1 and up (well, still
some quirks and issues) and it is usable for everyday work.
And on this kernel and up to 5.10-rc3 problem exist, right now I'm
testing 5.10-rc4 to see will that problem appear again. Sometimes it
need full 24 hours or more to manifest and I can't conclude how to
'trigger' it.

-- 
Kind regards

> > 'dmesg' shows a lot of such messages:
> > 
> > [305186.211284] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
> 
> EAGAIN is an unusual error return.
> 
> 	Regards
> 		Oliver
> 
> 

Re: driver/net/usb/r8152 stop working after some time with kernel 5.10-rc series

[Milan P. Stanić]

Hi,

On Mon, 2020-11-16 at 17:07, Milan P. Stanić wrote:
> On Mon, 2020-11-16 at 15:06, Oliver Neukum wrote:
> > Am Samstag, den 14.11.2020, 13:55 +0100 schrieb Milan P. Stanić:
> > > Driver loads and work some time but at unpredictable time it stops and
> > > starts to flood 'dmesg' output until shutdown (eth) interface.
> > > 
> > > Machine where I test this is arm64 ACER R13 chromebook.
> > 
> > Are you sure this started in v5.10 or did you not try earlier kernels?
> 
> I never used much mainline kernels on this machine because previous
> kernels had issues and quirks making them practically unusable.
> Earlier I used old chromeOS kernel (3.18 series) and from July this
> summer I switched to kernels from
> https://gitlab.collabora.com/eballetbo/linux/-/tree/topic/chromeos/somewhat-stable-5.7
> https://gitlab.collabora.com/eballetbo/linux/-/tree/topic/chromeos/somewhat-stable-5.8
> https://gitlab.collabora.com/eballetbo/linux/-/tree/topic/chromeos/somewhat-stable-5.9
> 
> They had also some issues but on somewhat-stable-5.8 and
> somewhat-stable-5.9 r8152 worked, or I missed to notice this problem.
> 
> First mainline kernel which works fine is 5.10-rc1 and up (well, still
> some quirks and issues) and it is usable for everyday work.
> And on this kernel and up to 5.10-rc3 problem exist, right now I'm
> testing 5.10-rc4 to see will that problem appear again. Sometimes it
> need full 24 hours or more to manifest and I can't conclude how to
> 'trigger' it.

This still happens on all 5.10-rc kernels. Just happened again after
two days of uptime on kernel 5.10-rc6.

[174225.340900] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.341129] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.341338] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.341541] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.341736] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.341963] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.342166] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.342364] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.342562] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.342759] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.343102] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.343463] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.343770] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.344079] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11
[174225.344298] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[00000000eb9fa129], ret = -11

> > > 'dmesg' shows a lot of such messages:
> > > 
> > > [305186.211284] r8152 2-1.2.4:1.0 eth0: Couldn't submit rx[000000005d575699], ret = -11
> > 
> > EAGAIN is an unusual error return.