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.
