Hi, On Wed, Oct 04, 2023 at 02:29:40PM +0100, Richard Purdie wrote: > On Wed, 2023-10-04 at 16:07 +0300, Mikko Rapeli wrote: > > Hi, > > > > Acked-by: Mikko Rapeli <mikko.rap...@linaro.org> > > > > for the full series. I hope our discussion over #yocto irc channel > > helped resolve these and the test failures seen with master-next. > > Yes, thanks! It was useful to have someone to talk the issues through > with and much appreciated. > > Sadly I don't think we've found all the issues yet. > > On the build N-1 we have a selftest failure on debian12-ty-1: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/5803/steps/14/logs/stdio
Can I get from this test run stdio to the more detailed task, qemurunner or qemu boot logs somehow? Or do you have to dig into the system manually to capture them, like in the example below? I would like to check into the detailed logs from both passing and failing test runs. Of course kernel dmesg would need to be there so maybe after your patch to the runqemu side at least. If there is a regression in kernel to the serial device detection and numbering, then we need some way to see e.g. 8250 uart/tty0/ttyAMA0 related dmesg messages. Cheers, -Mikko > with these logs saved: > > https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/d/qemurunner_log.20231004022851 > https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/d/qemu_boot_log.20231004022851 > > which suggest that ttyS1 never got any output but a getty did appear on > ttyS0. I confirmed there were only two serial devices in that > configuration. The exact image downloaded off that worker and run > locally worked so it isn't the image, it has to be some kind of race. > The image does have gettys configured for both serial ports. The kernel > boot log isn't present which a patch in this series attempts to fix. > > There was also: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5528/steps/13/logs/stdio > > which looks again like a getty didn't show up on a serial port. We > don't have more logs for that one but "Running postinst /etc/rpm- > postinsts/100-sysvinit-inittab" worries Ross and I a bit. It may or may > not be related. > > That brings me to: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/2199 > > which has two failures, I think both in commands run over the serial > interface. These ones appear to be more reproducible on ARM. > > I'm trying a new build run with this series applied to see if that > helps shed any light on what is going on. > > Cheers, > > Richard > > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#188698): https://lists.openembedded.org/g/openembedded-core/message/188698 Mute This Topic: https://lists.openembedded.org/mt/101753837/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
