On Wed, 2023-10-04 at 22:34 +0300, Mikko Rapeli wrote: > 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 <[email protected]> > > > > > > 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.
I can't capture everything in time in each case but I did grab: https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/e/ which is from https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/7863/steps/21/logs/stdio which has this threads patches applied. I've put two sets of logs there from the same builds, one success, one is missing the getty on one log. I also have the logs from: https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5848/steps/14/logs/stdio which I've saved here: https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/f/ noting that: https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/f/qemu_boot_log.20231004134427 is 3 bytes in size. Also interestingly, https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/f/qemu_boot_log.20231004140326 contains: "bootlogd: writing to console: Input/output error" which appears to come from sysvinit: sysvinit/3.04/sysvinit-3.04/src/bootlogd.c: /* * We got a write error on the real console. If its an EIO, * somebody hung up our filedescriptor, so try to re-open it. */ int write_err(int pts, int realfd, char *realcons, int e) { int fd; if (e != EIO) { werr: close(pts); fprintf(stderr, "bootlogd: writing to console: %s\n", strerror(e)); return -1; } close(realfd); if ((fd = open_nb(realcons)) < 0) goto werr; return fd; } and the werr goto must be triggering. I think we've seen these for a while but it is interesting something is closing console fds. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#188700): https://lists.openembedded.org/g/openembedded-core/message/188700 Mute This Topic: https://lists.openembedded.org/mt/101753837/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
