In message: Re: [PATCH 0/8][v2] linux-yocto: introduce v6.10 on 07/08/2024 Richard Purdie wrote:
> On Tue, 2024-08-06 at 14:55 -0400, [email protected] wrote: > > Here's v2 of the patch series. > > > > In a similar manner to v1, I've got yocto/yocto-bsp patches along > > side the > > oe-core ones .. just to save us both some synchronization and > > juggling. > > > > - the 6.10.3 update contains kconfig changes to fixup some of the > > warnings seen in v1 > > - I've updated the parselogs exceptions to fix the issues with > > qemumips*. I didn't run in directly on the AB, so there's a chance > > these will need a tweak. > > - As discussed I've pinned genericarm64 to 6.6 until it is updated > > to 6.10 > > - meta-virt has been updated, so xen should be fine now > > > > - meta-arm/meta-agl will still need updates from their maintainers. > > Thanks Bruce! > > This did look better but there is a new issue that has appeared: > > musl core-image-full-cmdline qemux86: > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/9349 > > musl core-image-full-cmdline qemux86-64: > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/9361/steps/12/logs/stdio > > sysvinit weston build: > https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/9334/steps/13/logs/stdio > > and also arm and x86-64 selftests in weston: > https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/3695 > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/6988 > https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/3695 > https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/7045 > https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/7053 > > all showing a traceback: > > 8.163704] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery > directory > [ 8.166639] NFSD: Using legacy client tracking operations. > [ 8.168227] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state > recovery directory > [ 8.170571] ------------[ cut here ]------------ > [ 8.171987] kernel BUG at /fs/nfsd/nfs4recover.c:534! > [ 8.172757] Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI > [ 8.173575] CPU: 1 PID: 386 Comm: rpc.nfsd Not tainted > 6.10.3-yocto-standard #1 > [ 8.174587] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS > rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 > [ 8.177362] RIP: 0010:nfsd4_legacy_tracking_init+0x17e/0x1b0 [nfsd] > [ 8.186979] Code: 89 de 48 c7 c7 f0 8e 51 c0 e8 3e fb ff ff 85 c0 41 89 c4 > 0f 85 2d 2d 00 00 48 c7 c7 90 bd 56 c0 45 31 e4 e8 d4 b7 08 c6 eb 08 <0f> 0b > 41 bc f4 ff ff ff 48 8b 45 d8 65 48 2b 04 25 28 00 00 00 75 > [ 8.192013] RSP: 0018:ffffae1d40653ca0 EFLAGS: 00010286 > [ 8.193466] RAX: 0000000000000049 RBX: ffff9c2a82d94000 RCX: > 0000000000000000 > [ 8.195370] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: > 0000000000000001 > [ 8.202191] RBP: ffffae1d40653cd0 R08: ffffffff870a7fa8 R09: > 00000000fffff000 > [ 8.210819] ? do_error_trap+0x6c/0x90 > [ 8.204171] R13: ffffffff87663e80 R14: ffff9c2a82d94000 R15: > ffff9c2a826c09c0 > [ 8.205187] FS: 00007f11b564a740(0000) GS:ffff9c2a8f880000(0000) > knlGS:0000000000000000 > [ 8.206335] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 8.207169] CR2: 000055b21bf12048 CR3: 0000000004c86000 CR4: > 00000000001506f0 > [ 8.208173] Call Trace: > [ 8.208547] <TASK> > [ 8.208860] ? __die_body.cold+0x19/0x1f > [ 8.209437] ? __die+0x2e/0x40 > [ 8.209885] ? die+0x33/0x60 > [ 8.210317] ? do_trap+0xbc/0x100 > [ 8.210819] ? do_error_trap+0x6c/0x90 > [ 8.211364] ? nfsd4_legacy_tracking_init+0x17e/0x1b0 [nfsd] > [ 8.212404] ? exc_invalid_op+0x56/0x70 > [ 8.213448] ? nfsd4_legacy_tracking_init+0x17e/0x1b0 [nfsd] > [ 8.221589] ? asm_exc_invalid_op+0x1f/0x30 > [ 8.227504] ? nfsd4_legacy_tracking_init+0x17e/0x1b0 [nfsd] > [ 8.234183] nfsd4_client_tracking_init+0x5b/0x1b0 [nfsd] > [ 8.235550] nfs4_state_start_net+0x2bf/0x360 [nfsd] > [ 8.236281] nfsd_svc+0x162/0x340 [nfsd] > [ 8.237309] write_threads+0xdb/0x1a0 [nfsd] > [ 8.238547] ? __pfx_write_threads+0x10/0x10 [nfsd] I'm not sure what is going on with these traps, I'm not able to reproduce them locally. It must be something in 6.10.3, I'll keep trying to see it here. .. but, it also may be something else weird in the build, see below. > > > > Also, a preempt-rt build failure: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/9340/steps/34/logs/stdio > > | > /home/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work-shared/qemux86-64/kernel-source/kernel/events/core.c: > In function 'event_sched_out': > | > /home/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work-shared/qemux86-64/kernel-source/kernel/events/core.c:2286:20: > error: 'struct perf_event' has no member named 'pending_sigtrap'; did you > mean 'pending_irq'? > | 2286 | if (event->pending_sigtrap) { > | | ^~~~~~~~~~~~~~~ > | | pending_irq > | > /home/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work-shared/qemux86-64/kernel-source/kernel/events/core.c:2287:24: > error: 'struct perf_event' has no member named 'pending_sigtrap'; did you > mean 'pending_irq'? > | 2287 | event->pending_sigtrap = 0; > | | ^~~~~~~~~~~~~~~ > | | pending_irq > This is fixed. > meta-virt was showing config warnings: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3471/steps/12/logs/stdio This one should be impossible if building my 6.10.3 latest. I removed the option that is throwing that warning on June 22nd. Is there anyway that I can find the checked out linux-yocto recipe and see what meta SRCREV it was using ? I'm wondering if this mix and match is somehow showing that trap that I'm not able to reproduce. Bruce > > And for completeness, as are meta-agl: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3471/steps/12/logs/stdio > > and meta-arm: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5827 > > Cheers, > > Richard > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#203095): https://lists.openembedded.org/g/openembedded-core/message/203095 Mute This Topic: https://lists.openembedded.org/mt/107756369/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
