DavidHeidelberg has quit [Quit: Bridge terminating on SIGTERM]
aat596 has quit [Quit: Bridge terminating on SIGTERM]
kusma has quit [Quit: Bridge terminating on SIGTERM]
maxnet[m] has quit [Quit: Bridge terminating on SIGTERM]
jevinskie[m] has quit [Quit: Bridge terminating on SIGTERM]
DavidHeidelberg has joined #tegra
aat596 has joined #tegra
jevinskie[m] has joined #tegra
maxnet[m] has joined #tegra
kusma has joined #tegra
maxnet[m] has quit [Ping timeout: 246 seconds]
maxnet[m] has joined #tegra
torez has joined #tegra
torez has quit [*.net *.split]
torez has joined #tegra
<lucaceresoli>
hello, I have a tegra20 board where rebooting does not work after upgrading from v5.17 to v5.18/v5.19/v6.0
<lucaceresoli>
does this ring any bell? I tried reverting some reboot-related patches found in v5.17..v5.18 but to no avail
<lucaceresoli>
I'm not bisecting v5.17..v5.18
<lucaceresoli>
interesting, the first bad commit is 8bd4aaf438e3 ("media: staging: tegra-vde: De-stage driver") by digetx, clearly unrelated to rebooting
<lucaceresoli>
however it does 2 things: renames TEGRA_VDE to VIDEO_TEGRA_VDE and moves it under an 'if V4L2_MEM2MEM_DEV'
<lucaceresoli>
sp I enabled V4L2_MEM2MEM_DEV + VIDEO_TEGRA_VDE and now reboot is working
<lucaceresoli>
I don't see how a video decode engine driver would affect rebooting :-?
<lucaceresoli>
I investigated whether VIDEO_TEGRA_VDE indirectly selects the reset controller so that I foud it enabled by chance, but found no evidence of such a dependency
Foxyloxy has quit [Remote host closed the connection]
<digetx>
kwizart: you'll either need to wait until somebody will fix it or bisect the bug and report it upstream, could be nouveau or iommu core regression
<lucaceresoli>
digetx: thanks for the feedback, however I'm not sure I follow what's going on. I would expect the cpu to be able to reboot with or without a VDE driver, no?