On Fri, Mar 8, 2024 at 9:21 AM Steve Sakoman <[email protected]> wrote: > > On Fri, Mar 8, 2024 at 3:35 AM Kevin Hao <[email protected]> wrote: > > > > On Thu, Mar 07, 2024 at 06:13:35PM -0500, Bruce Ashfield wrote: > > > Adding Kevin, > > > > > > I'm not going to be able to debug this more for a week or so. > > > > > > The alternate ways to fix it would be to try that ubuntu patch (fixed > > > for our tree), and / or see what else needs > > > to be cherry picked to -stable to fix util-linux. It is likely just a > > > return code difference to userspace when > > > resizing is being done. > > > > > > Kevin: I'm not sure if Wind River is seeing this, but you might want to > > > look > > > into those ptests and see if they pass on your end. > > > > A silly question, which branch are these three patches supposed to apply to? > > I have tried the kirkstone branch, but it seems that they can't apply > > cleanly. > > I also tried to manually apply the two kernel patches to the latest > > linux-yocto/v5.15/standard/base branch, but they also can't be applied > > cleanly. > > Am I miss something? > > No, you haven't missed anything. Bruce was assuming that kirkstone > contained patches that he hasn't sent yet. I wasn't able to apply the > second two patches either.
Yes, exactly. I did the patches against a different queue than what Steve had in test. > > > On the latest linux-yocto/v5.15/standard/base kernel, the parted ptest > > does have three failures. Then I have tried the ubuntu kernel patch [1] > > which is > > mentioned in the previous discussion about this issue. This patch can apply > > to > > the linux-yocto/v5.15/standard/base cleanly and it indeed resolve the parted > > failures, and I also don't find util-linux ptest failure after applying this > > patch. I attached my logs. > > Hmmm . . . Bruce said that the ubuntu patch didn't apply for him, so I > haven't tried that. > > Do you have a kirkstone patch that I can try on the autobuilder? > I'd still rather not go the ubuntu patch route. It is my last choice in the options. If this is caused by upstream commits, there should also be upstream commits that fix the issues. I need to identify those commits and document why they aren't appropriate for our 5.15 kernel before I pick up someone's else patch .. since at that point, I have no idea about their logic and other issues it may introduce. Bruce > Thanks! > > Steve > > > [1] > > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-next--2024.03.04-1&id=c3032b60ff7b3948325b8f2bd688b9a74be3cfb9 > > > > Thanks, > > Kevin > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196852): https://lists.openembedded.org/g/openembedded-core/message/196852 Mute This Topic: https://lists.openembedded.org/mt/104794844/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
