Cgroup module randomly fails to load on pixel 6 for unknown reasons. It seems to be related to how the USB is setup (via a hub or not) but we haven't been able to really understand the issue so far. Since the cgroups module is enabled by default, WA will crash because of unused feature, which is a shame.
LISA is not directly impacted because the approach to loading is different:
we don't enable any module by default
the modules are loaded on-demand
there is a user-provided list of forbidden modules. Users typically don't care about needing module X or Y unless it makes their setup crash. The code already knows what module it needs, so all we need is the list of forbidden module.
Some modules have to be loaded in advance and by the user, but none of the ones in the default list seem to fall in that category:
I haven't looked at the details but it seems that WA could also use a loading-on-demand system, in which case there would be no point in having that default module set anymore.
Cgroup module randomly fails to load on pixel 6 for unknown reasons. It seems to be related to how the USB is setup (via a hub or not) but we haven't been able to really understand the issue so far. Since the cgroups module is enabled by default, WA will crash because of unused feature, which is a shame.
LISA is not directly impacted because the approach to loading is different:
Some modules have to be loaded in advance and by the user, but none of the ones in the default list seem to fall in that category:
I haven't looked at the details but it seems that WA could also use a loading-on-demand system, in which case there would be no point in having that default module set anymore.
The WA issue can be currently worked around using: https://workload-automation.readthedocs.io/en/latest/faq.html?highlight=default_modules#q-i-get-the-error-module-x-failed-to-install-on-target