lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<Armbian-Discord> <W​erner> Odd. Both flavors sharing the same kernel/firmware package
simernes has joined #armbian-rockchip
Werner__ is now known as Werner
simernes has quit [Remote host closed the connection]
simernes has joined #armbian-rockchip
<Armbian-Discord> <T​enkawa> I agree that this sounds board specific however neither of my Rock5's nor my Edge2
<Armbian-Discord> <T​enkawa> That's why I'd like to know what he's doing differently on those boards/installs
<Armbian-Discord> <a​mazingfate> One of my 3588 board has this issue.
<Armbian-Discord> <a​mazingfate> I haven't started to investigate that.
<Armbian-Discord> <T​enkawa> I know the watchdog timer can have different triggers set though for default action
<Armbian-Discord> <T​enkawa> So if it it set to reset if it detects no activity and it doesn't see/get called from a shutdown call its going to (in my theory) treat it as an event
<Armbian-Discord> <T​enkawa> That could bee SoC dependent too on vendor
<Armbian-Discord> <a​mazingfate> Just did some Google search and find this: https://github.com/radxa/kernel/commit/2be8da0b30765c08b164fe6e7dd206ae2d8b8fc0
<Armbian-Discord> <T​enkawa> thats a 3399 year and a half old change though...
<Armbian-Discord> <T​enkawa> why would it just be manifesting now on certain 3588's?
<Armbian-Discord> <T​enkawa> Although I agree with the logic in the change
<Armbian-Discord> <a​mazingfate> This could be a hint. I will dive into my issue later.
simernes has quit [Remote host closed the connection]