05:26 <kwizart> digetx, yes, if the governor is available when tegra20-emc is loaded (like within an initramfs) it will auto-load it, but for both to be available in initramfs, there is a need to add a certain tag in the tegra20-emc (like: MODULE_SOFTDEP("pre: governor_simpleondemand")

06:27 <digetx> kwizart: how initramfs module list is created in the first place? are you specifying modules manually?

06:33 <kwizart> digetx, well, I can patch dracut to do the right thing, but modules list are created according to either it's a disk driver or a dependency of a disk driver (usb/ pci/ etc) or a graphic driver. Opionally graphic drivers can be added for desktop users

06:33 <kwizart> so either tegra20-emc is relevant for initramfs is a question...

06:35 <kwizart> this is the code that controls the "module list" by default: https://github.com/dracutdevs/dracut/blob/master/modules.d/90kernel-modules/module-setup.sh

06:36 <kwizart> and this for graphics https://github.com/dracutdevs/dracut/blob/master/modules.d/50drm/module-setup.sh

06:39 <kwizart> currently, tegra20-emc might not be added by default, I have added it explicitely, but I can double check if it's done by default (or if not having it leads to issue)

11:12 <digetx> kwizart: drm won't work without tegra20-emc

11:14 <digetx> softdep will work for emc

11:15 <digetx> but still drm driver needs interconnect providers, i.e. memory drivers

11:18 <digetx> it's possible to list all memory drivers as softdeps for drm driver, but then drm will load unrelated memory modules unconditionally

11:26 <kwizart> digetx, maybe it's possible to use: (like: MODULE_SOFTDEP("post: tegra_drm") from tegra20-emc... so tegra_drm will not have always have it if tegra20-emc isn't relevant for the given hardward

11:27 <digetx> that won't help drm to express dependency on the emc

11:28 <kwizart> no, but that will help the emc to express that it's needed for tegra_drm

11:29 <kwizart> I haven't tested much that way to express "reverse dependencies" but that's testable

11:34 <digetx> need a way to specify which modules should present in ramfs without enforcing preloading of those modules

11:35 <digetx> maybe dracut just needs option for "memory" drivers

11:36 <kwizart> another way would be to tell that all memory module needs to be available

11:38 <kwizart> at least there is https://github.com/dracutdevs/dracut/blob/master/modules.d/90kernel-modules/module-setup.sh#L83

11:40 <digetx> iommu/ also should be there

11:40 <kwizart> https://github.com/dracutdevs/dracut/commit/07c671cc51efcdffce90a90c2d9fd2af7bc0012a#diff-ce156d6151c76992972bd142959fed0fb9e1bd6db64927811d403a525a13e80d

11:40 <kwizart> indeed, we are using them builtin in Fedora, but they can be built as modules, indeed

11:41 <kwizart> or maybe I should double check

11:46 <kwizart> yes fedora has CONFIG_TEGRA_IOMMU_{GART,SMMU}=y

11:46 <kwizart> and tegra_drm has depends: host1x,drm,drm_kms_helper,cec,iova

11:47 <digetx> tegra iommu drivers can't be built as modules, but there is arm smmu and other drivers that could

11:51 <digetx> on the other hand, I'm not sure whether those drivers could really be useful in practice when built as modules

11:53 <kwizart> which ones ?

11:54 <digetx> all iommu drivers

11:54 <kwizart> interesting is that despite been listed as depends: iova isn't automatically added into the initramfs, maybe thats the error I'm seeing with 5.14:

11:55 <kwizart> Failed to attached device 54200000.dc to IOMMU_mapping (on jetson-tk1)

11:58 <digetx> drm driver won't load at all without iova

11:59 <kwizart> so that's probably a reason why tegra_drm is taking too long to load

11:59 <kwizart> is iova needed also in tegra20 ?

12:01 <digetx> it's needed unconditionally for all tegras since tegra-drm uses symbols from the iova module

12:02 <digetx> "Failed to attached device" should be harmless

12:03 <digetx> you should have it on older kernels that work

12:06 <digetx> dracut should automatically pull iova and others modules by the used symbols, are you sure that CONFIG_IOVA=m?

12:07 <kwizart> okay iova is added as a dependency of the tegra_drm only for cases when the drm (optional) module is used by dracut as I understand

12:07 <digetx> that's correct

12:11 <digetx> for tegra_drm you need memory,regulator,gpio modules

12:14 <digetx> and host1x

12:15 <digetx> but host1x should be auto-pulled

20:29 <m4t> digetx: just got same panic again, rebuilding with kasan (CONFIG_KASAN_INLINE=y)

20:31 <m4t> i think it's happening when munin runs 'sensors' cmd... not 100% sure, but looking at .bash_history when i ping/ssh when it freezes, seems to line up

20:32 <m4t> 'ouya' is alias to ssh in: 317399 10/11/21 22:40:27 ouya | 317538 10/14/21 16:05:26 ouya

20:32 <m4t> munin plugin is run every 5min

20:43 <m4t> hrm might need https://lkml.org/lkml/2021/10/11/459 to actually build...

21:26 <m4t> eh unfortunately neither boot (INLINE / OUTLINE)

21:50 <digetx> outline works on nexus7

21:52 <m4t> maybe it's to do with kexec loader... it was just boot looping

21:53 <m4t> inline was quite large, something like 16MB. not sure if that was looping or freezing as i didn't have hdmi hooked up when i tried that

21:53 <m4t> did not get to the point where heartbeat led was going though