narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
vagrantc has quit [Quit: leaving]
Consolatis_ has joined #linux-amlogic
Consolatis is now known as Guest5295
Guest5295 has quit [Ping timeout: 260 seconds]
<adema> Hi all! I am the lucky owner of a potato board aml-s905x-cc, and I was trying to upgrade my system from upstream kernel 5.11 to 5.16 and 19 times over 20 I encounter a kernel segfault during boot: https://paste.ee/p/u6lAv
<adema> and when that happens network is never properly initialized and any network related command like `ip a s` or `ping` just hangs
<adema> even though that might be two different problems, it seems the network issue happens everytime the kernel segfault is trigerred
<adema> I tried 5.15 and 5.14, same problem
<adema> I haven't tried 5.12 and 5.13 yet
<adema> One thing to note though it that I the segfault is also present in 5.11 iirc but it doesn't happen frequently
<adema> same issue with 5.13
valdikss has quit [Ping timeout: 240 seconds]
valdikss has joined #linux-amlogic
<adema> I upgraded to latest u-boot, just for the fun of it, but of course it doesn't solve the issue
<adema> so basically potato boards are borked with recent kernels :/
tolszak has joined #linux-amlogic
tolszak has quit [Ping timeout: 256 seconds]
<montjoie> adema: which 5.16.x exactly ?
tolszak has joined #linux-amlogic
tolszak has quit [Ping timeout: 252 seconds]
vagrantc has joined #linux-amlogic
<adema> 5.16.16
<adema> montjoie, is this a known issue?
<adema> I've removed the 5.16 I was trying to be honest because I tried other versions and I didn't have enough /boot space
<adema> I can retry 5.16.16 to confirm though, let me do that
<adema> montjoie, yeah 5.16.16, i'll try to post the full dmesg as soon as I can boot the board with network working :(
<adema> this bug also seem to prevent rebooting
<adema> montjoie, here is the full dmesg http://ix.io/3TDg
<adema> Here is a dmesg log when 5.16.16 boot successfuly: http://ix.io/3TDd
<montjoie> let me launch a 5.16.6 on my potatoes
<montjoie> adema: works for me
<montjoie> I will run my network testsuite for being sure
<montjoie> only diff I could see, is that you have flow control rx/tx (mine is off)
<montjoie> adema: could you paste your segfault ? any kernel message ?
<montjoie> oups I just see the paste
<montjoie> wow the reboot: HARDWARE PROTECTION shutdown (Temperature too high) and the scpi seems unrelated with network but still bad
buzzmarshall has joined #linux-amlogic
<adema> well the network issue is always present when the scpi segfault is triggered
<adema> so it seems they are related
<adema> when the scpi segfault is not triggered, network always work fine
<montjoie> so very related
<montjoie> scpi is not in my knowledge unfortunatly
<montjoie> narmstrong could help perhaps
vagrantc has quit [Quit: leaving]
tdebrouw has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 272 seconds]
camus1 is now known as camus
buzzmarshall has quit [Quit: Konversation terminated!]
adeepv has quit [Quit: %exit%]
Terry1373229 has quit [Ping timeout: 256 seconds]
Terry1373229 has joined #linux-amlogic
tdebrouw has quit [Quit: Leaving.]