| Message ID | 20230608193901.363242-2-bruce.ashfield@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | [1/2] qemux86/conf: TEST ONLY. Drop smp boot | expand |
On Thu, 2023-06-08 at 19:39 +0000, bruce.ashfield@gmail.com wrote: > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > We are seeing intermittent boot hangs on x86. To try and determine > if this is a 6.1-stable only issue, set the prferred provider for > qemux86 to linux-yocto-dev. > > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> > --- > meta/conf/machine/include/qemu.inc | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc > index 0d71bcbbad..121e8474c1 100644 > --- a/meta/conf/machine/include/qemu.inc > +++ b/meta/conf/machine/include/qemu.inc > @@ -21,6 +21,8 @@ RDEPENDS:${KERNEL_PACKAGE_NAME}-base = "" > > # Use a common kernel recipe for all QEMU machines > PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" > +PREFERRED_PROVIDER_virtual/kernel:qemux86 = "linux-yocto-dev" > +PREFERRED_PROVIDER_virtual/kernel:qemux86-64 = "linux-yocto-dev" > > EXTRA_IMAGEDEPENDS += "qemu-system-native qemu-helper-native:do_addto_recipe_sysroot" > Unfortunately this has other issues: https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/7276/steps/13/logs/stdio Traceback (most recent call last): File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ [Previous line repeated 2 more times] File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/runtime/cases/kernelmodule.py", line 48, in test_kernel_module self.assertEqual(status, 0, msg='\n'.join([cmd, output])) AssertionError: 1 != 0 : cd /tmp && insmod hellomod.ko insmod: ERROR: could not insert module hellomod.ko: Invalid module format But also: https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/6105/steps/13/logs/stdio which shows ping failures, as if the networking isn't working. I checked the boot logs and the kernel is booting but for some reason networking doesn't become live and ping fails. I can see messages saying the "IP-Config: Complete:" with appropriate network config in the kernel boot log so it is all the more puzzling: https://autobuilder.yocto.io/pub/failed-builds-data/qemu_boot_log.20230609064146 The ping failures repeated in many other targets in that build. Cheers, Richard
On Fri, 2023-06-09 at 08:17 +0100, Richard Purdie via lists.openembedded.org wrote: > On Thu, 2023-06-08 at 19:39 +0000, bruce.ashfield@gmail.com wrote: > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > We are seeing intermittent boot hangs on x86. To try and determine > > if this is a 6.1-stable only issue, set the prferred provider for > > qemux86 to linux-yocto-dev. > > > > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> > > --- > > meta/conf/machine/include/qemu.inc | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc > > index 0d71bcbbad..121e8474c1 100644 > > --- a/meta/conf/machine/include/qemu.inc > > +++ b/meta/conf/machine/include/qemu.inc > > @@ -21,6 +21,8 @@ RDEPENDS:${KERNEL_PACKAGE_NAME}-base = "" > > > > # Use a common kernel recipe for all QEMU machines > > PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" > > +PREFERRED_PROVIDER_virtual/kernel:qemux86 = "linux-yocto-dev" > > +PREFERRED_PROVIDER_virtual/kernel:qemux86-64 = "linux-yocto-dev" > > > > EXTRA_IMAGEDEPENDS += "qemu-system-native qemu-helper-native:do_addto_recipe_sysroot" > > > > Unfortunately this has other issues: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/7276/steps/13/logs/stdio > > Traceback (most recent call last): > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f > return func(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^ > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f > return func(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^ > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f > return func(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^ > [Previous line repeated 2 more times] > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/runtime/cases/kernelmodule.py", line 48, in test_kernel_module > self.assertEqual(status, 0, msg='\n'.join([cmd, output])) > AssertionError: 1 != 0 : cd /tmp && insmod hellomod.ko > insmod: ERROR: could not insert module hellomod.ko: Invalid module format > > But also: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/6105/steps/13/logs/stdio > > which shows ping failures, as if the networking isn't working. I > checked the boot logs and the kernel is booting but for some reason > networking doesn't become live and ping fails. > > I can see messages saying the "IP-Config: Complete:" with appropriate > network config in the kernel boot log so it is all the more puzzling: > > https://autobuilder.yocto.io/pub/failed-builds-data/qemu_boot_log.20230609064146 > > The ping failures repeated in many other targets in that build. There is also a perf buildpath warning: https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/6105/steps/12/logs/warnings which we'll likely have to fix at some point. Cheers, Richard
On Fri, Jun 9, 2023 at 3:19 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > > On Fri, 2023-06-09 at 08:17 +0100, Richard Purdie via > lists.openembedded.org wrote: > > On Thu, 2023-06-08 at 19:39 +0000, bruce.ashfield@gmail.com wrote: > > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > > > We are seeing intermittent boot hangs on x86. To try and determine > > > if this is a 6.1-stable only issue, set the prferred provider for > > > qemux86 to linux-yocto-dev. > > > > > > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> > > > --- > > > meta/conf/machine/include/qemu.inc | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc > > > index 0d71bcbbad..121e8474c1 100644 > > > --- a/meta/conf/machine/include/qemu.inc > > > +++ b/meta/conf/machine/include/qemu.inc > > > @@ -21,6 +21,8 @@ RDEPENDS:${KERNEL_PACKAGE_NAME}-base = "" > > > > > > # Use a common kernel recipe for all QEMU machines > > > PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" > > > +PREFERRED_PROVIDER_virtual/kernel:qemux86 = "linux-yocto-dev" > > > +PREFERRED_PROVIDER_virtual/kernel:qemux86-64 = "linux-yocto-dev" > > > > > > EXTRA_IMAGEDEPENDS += "qemu-system-native qemu-helper-native:do_addto_recipe_sysroot" > > > > > > > Unfortunately this has other issues: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/7276/steps/13/logs/stdio > > > > Traceback (most recent call last): > > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f > > return func(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^ > > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f > > return func(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^ > > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f > > return func(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^ > > [Previous line repeated 2 more times] > > File "/home/pokybuild/yocto-worker/musl-qemux86-64/build/meta/lib/oeqa/runtime/cases/kernelmodule.py", line 48, in test_kernel_module > > self.assertEqual(status, 0, msg='\n'.join([cmd, output])) > > AssertionError: 1 != 0 : cd /tmp && insmod hellomod.ko > > insmod: ERROR: could not insert module hellomod.ko: Invalid module format > > I'll fix this up as part of my -dev kernel work to get it ready as a reference kernel. > > But also: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/6105/steps/13/logs/stdio > > > > which shows ping failures, as if the networking isn't working. I > > checked the boot logs and the kernel is booting but for some reason > > networking doesn't become live and ping fails. > > > > I can see messages saying the "IP-Config: Complete:" with appropriate > > network config in the kernel boot log so it is all the more puzzling: > > > > https://autobuilder.yocto.io/pub/failed-builds-data/qemu_boot_log.20230609064146 > > > > The ping failures repeated in many other targets in that build. This is a strange one. Not seeing that here, but I'll see if some sort of networking configuration needs tweaking. > > There is also a perf buildpath warning: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/6105/steps/12/logs/warnings > > which we'll likely have to fix at some point. I'll fix that right away. Bruce > > Cheers, > > Richard
diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc index 0d71bcbbad..121e8474c1 100644 --- a/meta/conf/machine/include/qemu.inc +++ b/meta/conf/machine/include/qemu.inc @@ -21,6 +21,8 @@ RDEPENDS:${KERNEL_PACKAGE_NAME}-base = "" # Use a common kernel recipe for all QEMU machines PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" +PREFERRED_PROVIDER_virtual/kernel:qemux86 = "linux-yocto-dev" +PREFERRED_PROVIDER_virtual/kernel:qemux86-64 = "linux-yocto-dev" EXTRA_IMAGEDEPENDS += "qemu-system-native qemu-helper-native:do_addto_recipe_sysroot"