nashpa has quit [Ping timeout: 258 seconds]
nashpa has joined #linux-exynos
adjtm has quit [Ping timeout: 240 seconds]
genii has joined #linux-exynos
genii has quit [Quit: Morning comes early.... GO LEAFS GO!]
mszyprow has joined #linux-exynos
wwilly has joined #linux-exynos
PabloPL has joined #linux-exynos
adjtm has joined #linux-exynos
wwilly has quit [Quit: This computer has gone to sleep]
<krzk> PabloPL: usual complains from ARM guys :)
mixfix41 has left #linux-exynos [#linux-exynos]
wwilly has joined #linux-exynos
<mszyprow> wwilly: you have asked about running linux-next on xu3/4 yesterday - I check it almost everyday on xu3/4/hc1
<wwilly> mszyprow, morning, yeah krzk for-next repo branch
<wwilly> is it that one you run?
<mszyprow> wwilly: frankly, I test main linux-next branch
<mszyprow> wwilly: it covers krzk/for-next too
<mszyprow> wwilly: are there any issues with it?
<wwilly> for the krzk for-next branch, I haven't tried the very true mainline linux-next
<wwilly> I will try this last next week after my paper deadline
<mszyprow> wwilly: I can run tests on krzk/for-next now
<wwilly> go ahead and tell me if you have the same, note that this happen when I access with ssh on it, via uart is fine
<mszyprow> wwilly: okay, I will try ssh session then
<krzk> mszyprow: I think snawrocki tried yesterday my branch and confirmed it is working fine
<krzk> mszyprow: "16:23 < snawrocki> krzk for-next branch works well with exynos_defconfig on XU3, I tried UART and SSH"
<mszyprow> wwilly: I also checked it now and it works fine here, both xu3 and xu4, uart and ssh
<mszyprow> wwilly: however I remember that someone reported on odroid forums that he has some random issues with smsc95xx lan
<wwilly> ok, shit on my side then
<mszyprow> logs points to smsc95xx, maybe it is a matter of triggering it
<wwilly> when you ssh, do you have automatic login with keys?
<mszyprow> yep
<wwilly> yeah seams a dead end but detective willy try to understand :)
<mszyprow> this might depend on the network configuration and topology
<mszyprow> and probably a few other things
<mszyprow> wwilly: is your issue reproducible?
<wwilly> not really
<wwilly> boot and log ssh trigger one, then network is randomly working
<wwilly> get a pong randomly as well...
<mszyprow> no idea, something definitely related to smsc95xx driver. someone on odroid forums said it worked always fine on v4.14
<mszyprow> if you find a way to reproduce it reliably, maybe it would be possible to bisect this it
<mszyprow> -this
<wwilly> yes, will take the time next week, thanks
_whitelogger has joined #linux-exynos
PabloPL has quit [Quit: PabloPL]
<mszyprow> wwilly: but I never reproduced it
<wwilly> uhm ok, thanks, maybe 5.4 is the first version where you have this in the strange world I'm living
<wwilly> this board is connected to a network where there is really HIGH traffic
<wwilly> so maybe something can't keep up somewhere on the network stack?
<wwilly> don't know, will check that later
PabloPL has joined #linux-exynos
PabloPL has quit [Ping timeout: 258 seconds]
<mszyprow> wwilly: well, even with very high trafic, the driver must not crash
wwilly has quit [Quit: This computer has gone to sleep]
wwilly has joined #linux-exynos
PabloPL has joined #linux-exynos
PabloPL has quit [Client Quit]
wwilly has quit [Quit: This computer has gone to sleep]
wwilly has joined #linux-exynos
genii has joined #linux-exynos
mszyprow has quit [Ping timeout: 265 seconds]
PabloPL has joined #linux-exynos
PabloPL has quit [Client Quit]
mixfix41_ has quit [Ping timeout: 265 seconds]
_whitelogger has joined #linux-exynos
glLiquidAcid has joined #linux-exynos
glLiquidAcid has quit [Remote host closed the connection]
PabloPL has joined #linux-exynos
PabloPL has quit [Quit: Wychodzi]
Putti has quit [Quit: Leaving]
wwilly has quit [Quit: Leaving]
Putti has joined #linux-exynos
PabloPL has joined #linux-exynos
PabloPL has quit [Client Quit]
LiquidAcid has quit [Quit: Leaving]
_whitelogger has joined #linux-exynos