On Wed, Mar 23, 2022 at 5:18 PM Mark Brown <broonie@xxxxxxxxxx> wrote: > > On Wed, Mar 23, 2022 at 04:53:13PM +0100, Arnd Bergmann wrote: > > On Wed, Mar 23, 2022 at 3:23 PM Guenter Roeck <linux@xxxxxxxxxxxx> wrote: > > > > I don't think it is entirely academic. versatile-pb fails for me; > > > if it doesn't fail at KernelCI, I'd like to understand why - not to > > > fix it in my test environment, but to make sure that I _don't_ fix it. > > > After all, it _is_ a regression. Even if that regression is triggered > > > by bad (for a given definition of "bad") userspace code, it is still > > > a regression. > > > Maybe kernelci has a virtio-rng device assigned to the machine > > and you don't? That would clearly avoid the issue here. > > No, nothing I can see in the boot log: > > https://storage.kernelci.org/next/master/next-20220323/arm/versatile_defconfig/gcc-10/lab-baylibre/baseline-qemu_arm-versatilepb.html > > and I'd be surprised if virtio devices made it through with a specific > platform emulation. In general they do: virtio devices appear as regular PCI devices and get probed from there, as long as the drivers are available. It looks like the PCI driver does not get initialized here though, presumably because it's not enabled in versatile_defconfig. It used to also not be enabled in multi_v5_defconfig, but I have merged a patch from Anders that enables it in 5.18 for the multi_v5_defconfig. > However it looks like for that test the init > scripts didn't do anything with the random seed (possibly due to running > from ramdisk?) so we'd not have hit the condition. Right. Arnd
