date:20230918

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.28.rc2)

2023-09-18 Thread Jing Hui Tham

Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.28.rc2. 
We are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
6. Edgerouter
7. Beaglebone

 
ETA for completion Friday, 22 Sept 2023.
 
Best regards,
Jing Hui


> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Sunday, September 17, 2023 3:03 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-3.1.28.rc2)
> 
> 
> A build flagged for QA (yocto-3.1.28.rc2) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.28.rc2
> 
> 
> Build hash information:
> 
> bitbake: b60c7085ec370473bea9b3b4b65826a17638837f
> meta-agl: e0f6590189cb0a510bff0d4233667c552d964591
> meta-arm: b1fe8443a7a72c65fa0fc3371f607c6671b3a882
> meta-aws: 77e5438c27292ad5f8c7d3b100cb09b8dbf1c7f4
> meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
> meta-intel: e482213f37828216c7a7df68ff353652cc865ec1
> meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
> meta-openembedded: e42d1e758f9f08b98c0e8c6f0532316951bb276f
> meta-virtualization: 0dbb8593fa38ac2a04fcac04ff3e35611e849824
> oecore: 8b91c463fb3546836789e1890b3c68acf69c162a
> poky: 926eb08fe325e2ea13098f99d920840b9354ceb9
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61040): https://lists.yoctoproject.org/g/yocto/message/61040
Mute This Topic: https://lists.yoctoproject.org/mt/101450665/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW37

2023-09-18 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW37 are listed below:
Priority Bug ID Short Description Changer Owner Was Became
Medium+ 11781  bitbake
--observe-only may get KeyError richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
11899  broken
'bitbake --status-only' and 'bitbake -m' for multiple connections
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4
13424  devupstream
doesn't work with mutilib richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
13599  Enhancement:
Detect variables that shouldn't be defined in image scope, but in global
(distro) scope richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
13808  do_task[noexec]
= "" marks task noexec, which is inconsistent with docs
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4
14620  QA error
not seen when reusing SSTATE richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
14717 
OEToolchainConfig.cmake
sets wrong and unsuitable compiler flags richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
14811  Incorrect
path matching in pseudo cause package failure in yocto
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4
14870  Dangling
bbappend behaviour can lead to unexpected surprises (error vs warn)
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4
14918  Devtool
fails if SRCREV is set to ${AUTOREV} richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
14921  devtool
failure: No such file or directory: '/tmp/devtoolqambdi_6eh/singletask.lock'
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4
15005  ParseError
in None: Not all recipes parsed, parser thread killed/died? Exiting.
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4
15102  Using
overrides on security flags may produce an incorrect meta-environment for
the generated SDK richard.pur...@linuxfoundation.org
richard.pur...@linuxfoundation.org 4.3 M3 4.3 M4
15130  bitbake
should warn if a function is defined only for specific cases
richard.pur...@linuxfoundation.org richard.pur...@linuxfoundation.org
4.3 M3 4.3
M4

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61039): https://lists.yoctoproject.org/g/yocto/message/61039
Mute This Topic: https://lists.yoctoproject.org/mt/101450048/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW37!

2023-09-18 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!
Who Count
st...@sakoman.com 2
michael.opdenac...@bootlin.com 2
richard.pur...@linuxfoundation.org 1
alex.kana...@gmail.com 1
Grand Total 6

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61038): https://lists.yoctoproject.org/g/yocto/message/61038
Mute This Topic: https://lists.yoctoproject.org/mt/101450038/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-09-18 Thread Stephen Jolley

All,

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means
people can find them. They're being listed on the triage page under the
appropriate heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:
https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project. If anyone can help,
please take ownership of the bug and send patches! If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 412
unassigned or newcomer bugs.

We're hoping people may be able to spare some time now and again to help
out with these. Bugs are split into two types, "true bugs" where things
don't work as they should and "enhancements" which are features we'd want
to add to the system. There are also roughly four different "priority"
classes right now, “4.3”, “4.4”, "4.99" and "Future", the more
pressing/urgent issues being in "4.3" and then “4.4”.

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account). The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61037): https://lists.yoctoproject.org/g/yocto/message/61037
Mute This Topic: https://lists.yoctoproject.org/mt/10144/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.3

2023-09-18 Thread Stephen Jolley

All,

Below is the list of top 27 bug owners as of the end of WW37 who have open
medium or higher bugs and enhancements against YP 4.3. There are 28
possible work days left until the final release candidates for YP 4.3 needs
to be released.
Who Count
michael.opdenac...@bootlin.com 34
ross.bur...@arm.com 33
richard.pur...@linuxfoundation.org 26
david.re...@windriver.com 23
randy.macl...@windriver.com 22
bruce.ashfi...@gmail.com 22
jpewhac...@gmail.com 11
pi...@pidge.org 7
pa...@zhukoff.net 6
sakib.sa...@windriver.com 5
yash.shi...@windriver.com 4
tim.orl...@konsulko.com 2
sundeep.kokko...@windriver.com 2
jon.ma...@arm.com 2
alexis.loth...@bootlin.com 2
alexandre.bell...@bootlin.com 2
tvgamb...@gmail.com 1
thr...@amazon.de 1
thomas.per...@bootlin.com 1
pokyli...@reliableembeddedsystems.com 1
p.lob...@welotec.com 1
martin.ja...@gmail.com 1
mark.asselst...@windriver.com 1
louis.ran...@syslinbit.com 1
jens.ge...@desy.de 1
fathi.bou...@linaro.org 1
alejan...@enedino.org 1
Grand Total 214

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61036): https://lists.yoctoproject.org/g/yocto/message/61036
Mute This Topic: https://lists.yoctoproject.org/mt/101449986/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v6.1/standard/ti-sdk-6.1/ti-j7xxx & v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx][PATCH] drivers: media: vxe-vxd: Initialize the variable __value

2023-09-18 Thread Xulin Sun via lists.yoctoproject.org

To avoid below building issue:
drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h:42:22: error: '__value' is 
used uninitialized [-Werror=uninitialized]
|42 | type __value = value; \
|   |  ^~~
drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h:42:22: note: '__value' was 
declared here
|42 | type __value = value; \
|   |  ^~~

Signed-off-by: Xulin Sun 
---
 drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h 
b/drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h
index a18ffda4efcb..b73cab6748b0 100644
--- a/drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h
+++ b/drivers/media/platform/img/vxe-vxd/decoder/reg_io2.h
@@ -39,8 +39,10 @@
  */
 #define REGIO_CHECK_VALUE_FITS_WITHIN_FIELD(group, reg, field, value, type) \
{ \
-   type __value = value; \
-   unsigned int temp = (unsigned int)(__value); \
+   type __value = 0; \
+   unsigned int temp = 0; \
+   __value = value; \
+   temp = (unsigned int)(__value); \
if (temp > group ## _ ## reg ## _ ## field ## _LSBMASK) { \
IMG_ASSERTunsigned int)__value) & \
(unsigned int)~(group ## _ ## reg ## _ ## field ## 
_LSBMASK)) == \
-- 
2.35.5


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13078): 
https://lists.yoctoproject.org/g/linux-yocto/message/13078
Mute This Topic: https://lists.yoctoproject.org/mt/101448350/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto]: [kernel/kernel-rt v6.1]: drivers: fsl_qbman: alloc memory with GFP_ATOMIC parameter

2023-09-18 Thread Meng Li via lists.yoctoproject.org

From: Limeng 

Hi Bruce,

This patch is used alloc memory with GFP_ATOMIC parameter so that avoid 
triggering sleep in atomic context. 
Could you please help merge this patch into linux-ycoto kernel?
Branch are v6.1/standard/nxp-sdk-6.1/nxp-soc and 
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc


diffstat info as below:

  dpa_alloc.c |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

thanks,
Limeng

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13076): 
https://lists.yoctoproject.org/g/linux-yocto/message/13076
Mute This Topic: https://lists.yoctoproject.org/mt/101448249/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] drivers: fsl_qbman: alloc memory with GFP_ATOMIC parameter

2023-09-18 Thread Meng Li via lists.yoctoproject.org

When running dpdk test case, there is below calltrace because of
allocating memory in atomic context.
Call trace:
..
 __might_resched+0x154/0x1c0
 __might_sleep+0x54/0xa4
 __kmem_cache_alloc_node+0x434/0x594
 kmalloc_trace+0x54/0x140
 dpa_alloc_reserve+0x100/0x19c
 qman_reserve_fqid_range+0x2c/0x3c
 usdpaa_ioctl+0x1314/0x1ae4
 __arm64_sys_ioctl+0xb4/0x100
..
To avoid this calltrace, replace GFP_KERNEL with GFP_ATOMIC.

Signed-off-by: Meng Li 
---
 drivers/staging/fsl_qbman/dpa_alloc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/fsl_qbman/dpa_alloc.c 
b/drivers/staging/fsl_qbman/dpa_alloc.c
index a98779bf26da..e420ef73325a 100644
--- a/drivers/staging/fsl_qbman/dpa_alloc.c
+++ b/drivers/staging/fsl_qbman/dpa_alloc.c
@@ -654,7 +654,7 @@ int dpa_alloc_reserve(struct dpa_alloc *alloc, u32 base, 
u32 num)
}
}
/* Add the allocation to the used list with a refcount of 1 */
-   used_node = kmalloc(sizeof(*used_node), GFP_KERNEL);
+   used_node = kmalloc(sizeof(*used_node), GFP_ATOMIC);
if (!used_node) {
spin_unlock_irq(>lock);
return -ENOMEM;
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13077): 
https://lists.yoctoproject.org/g/linux-yocto/message/13077
Mute This Topic: https://lists.yoctoproject.org/mt/101448250/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Overriding package configuration as a distro

2023-09-18 Thread Logan Grosz via lists.yoctoproject.org

Hi, Quentin

Ah, this is great. This looks exactly like what I was looking for. I appreciate 
the timely response.

Thank you,
Logan

From: Quentin Schulz 
Sent: Monday, September 18, 2023 8:50 AM
To: Logan Grosz ; yocto@lists.yoctoproject.org 

Subject: Re: [yocto] Overriding package configuration as a distro

Hi Logan,

On 9/18/23 16:43, Logan Grosz via lists.yoctoproject.org wrote:
> You don't often get email from logan.grosz=b9c@lists.yoctoproject.org. 
> Learn why this is important
> Hi, all
>
> I have two distros in the same meta layer, "A" and "B," and a recipe which 
> installs a configuration file existing in a layer elsewhere. "A" and "B" 
> should provide different configuration files, overriding the original 
> configuration. It seems less than ideal to create a bbappend in this scenario 
> as that would require the bbappend to know about the various distros and even 
> handle the case where neither distro is chosen, some other "C" distro may be 
> built for. My goal is a distro-centric configuration rather than a 
> recipe/package-centric one. How can I do this? Does this align with the 
> framework, or should I be looking into a different solution for this problem?
>

The distro name is already part of FILESOVERRIDES so you can just add
your configuration file in a directory named after your distro. e.g.
provided your distro is called logan-distro, the following makes it
possible to override the configuration file from another layer:

```
# cat recipes-foo/bar/bar-1.0.0/logan-distro/file.conf
meh
# cat recipes-foo/bar/bar_1.0.0.bbappend
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-${PV}:"
```

no need to modify anything else if the file.conf file is added via
SRC_URI mechanism, otherwise you'll need to add a bit more to the
bbappend (or use patches instead), probably via a do_configure:prepend
or even do_patch:append (I think the file fetcher also allows to install
directly in the proper directory via subdir= parameter?).

Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61035): https://lists.yoctoproject.org/g/yocto/message/61035
Mute This Topic: https://lists.yoctoproject.org/mt/101434764/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Overriding package configuration as a distro

2023-09-18 Thread Quentin Schulz via lists.yoctoproject.org


Hi Logan,

On 9/18/23 16:43, Logan Grosz via lists.yoctoproject.org wrote:

You don't often get email from logan.grosz=b9c@lists.yoctoproject.org. Learn why 
this is important
Hi, all

I have two distros in the same meta layer, "A" and "B," and a recipe which installs a configuration file 
existing in a layer elsewhere. "A" and "B" should provide different configuration files, overriding the 
original configuration. It seems less than ideal to create a bbappend in this scenario as that would require the bbappend to know 
about the various distros and even handle the case where neither distro is chosen, some other "C" distro may be built 
for. My goal is a distro-centric configuration rather than a recipe/package-centric one. How can I do this? Does this align with 
the framework, or should I be looking into a different solution for this problem?



The distro name is already part of FILESOVERRIDES so you can just add 
your configuration file in a directory named after your distro. e.g. 
provided your distro is called logan-distro, the following makes it 
possible to override the configuration file from another layer:


```
# cat recipes-foo/bar/bar-1.0.0/logan-distro/file.conf
meh
# cat recipes-foo/bar/bar_1.0.0.bbappend
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-${PV}:"
```

no need to modify anything else if the file.conf file is added via 
SRC_URI mechanism, otherwise you'll need to add a bit more to the 
bbappend (or use patches instead), probably via a do_configure:prepend 
or even do_patch:append (I think the file fetcher also allows to install 
directly in the proper directory via subdir= parameter?).


Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61034): https://lists.yoctoproject.org/g/yocto/message/61034
Mute This Topic: https://lists.yoctoproject.org/mt/101434764/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Overriding package configuration as a distro

2023-09-18 Thread Logan Grosz via lists.yoctoproject.org

Hi, all

I have two distros in the same meta layer, "A" and "B," and a recipe which 
installs a configuration file existing in a layer elsewhere. "A" and "B" should 
provide different configuration files, overriding the original configuration. 
It seems less than ideal to create a bbappend in this scenario as that would 
require the bbappend to know about the various distros and even handle the case 
where neither distro is chosen, some other "C" distro may be built for. My goal 
is a distro-centric configuration rather than a recipe/package-centric one. How 
can I do this? Does this align with the framework, or should I be looking into 
a different solution for this problem?

Thank you,
Logan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61033): https://lists.yoctoproject.org/g/yocto/message/61033
Mute This Topic: https://lists.yoctoproject.org/mt/101434764/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Cross-compilation of driver files

2023-09-18 Thread MOHAMMED HASSAN

Hi guys,
So long back I was trying to load driver files for a battery charger and a
battery fuel gauge as a kernel module. However I face errors that are
actually related to cross-compilation. I  am not sure how to proceed with
this. Can you guys refer to some documentation from both the yocto project
and any other that can help.
Thanks

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61032): https://lists.yoctoproject.org/g/yocto/message/61032
Mute This Topic: https://lists.yoctoproject.org/mt/101433218/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] debug: add CONFIG_MODULE_ALLOW_BTF_MISMATCH to debug-btf.cfg

2023-09-18 Thread Xiangyu Chen

From: Xiangyu Chen 

When enabled DEBUG_INFO_BTF option, some kernel modules cannot install due to 
mismatch the
vmlinux BTF header information and output error message as below:

root@intel-x86-64:~#  modprobe squashfs
BPF: type_id=12 bits_offset=64
BPF:
BPF: Invalid name
BPF:
failed to validate module [squashfs] BTF: -22
modprobe: ERROR: could not insert 'squashfs': Invalid argument

Signed-off-by: Xiangyu Chen 
---
 features/debug/debug-btf.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/features/debug/debug-btf.cfg b/features/debug/debug-btf.cfg
index 61815776..59df424f 100644
--- a/features/debug/debug-btf.cfg
+++ b/features/debug/debug-btf.cfg
@@ -1,2 +1,3 @@
 # SPDX-License-Identifier: MIT
 CONFIG_DEBUG_INFO_BTF=y
+CONFIG_MODULE_ALLOW_BTF_MISMATCH=y
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13075): 
https://lists.yoctoproject.org/g/linux-yocto/message/13075
Mute This Topic: https://lists.yoctoproject.org/mt/101429003/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] debug: add CONFIG_MODULE_ALLOW_BTF_MISMATCH to debug-btf.cfg

2023-09-18 Thread Xiangyu Chen

From: Xiangyu Chen 

When enabled DEBUG_INFO_BTF option, some kernel modules cannot install due to 
mismatch the
vmlinux BTF header information and output error message as below:

root@intel-x86-64:~#  modprobe squashfs
BPF: type_id=12 bits_offset=64
BPF:
BPF: Invalid name
BPF:
failed to validate module [squashfs] BTF: -22
modprobe: ERROR: could not insert 'squashfs': Invalid argument

Signed-off-by: Xiangyu Chen 
---
 features/debug/debug-btf.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/features/debug/debug-btf.cfg b/features/debug/debug-btf.cfg
index 61815776..59df424f 100644
--- a/features/debug/debug-btf.cfg
+++ b/features/debug/debug-btf.cfg
@@ -1,2 +1,3 @@
 # SPDX-License-Identifier: MIT
 CONFIG_DEBUG_INFO_BTF=y
+CONFIG_MODULE_ALLOW_BTF_MISMATCH=y
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13074): 
https://lists.yoctoproject.org/g/linux-yocto/message/13074
Mute This Topic: https://lists.yoctoproject.org/mt/101428981/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.28.rc2)

[yocto] M+ & H bugs with Milestone Movements WW37

[yocto] Enhancements/Bugs closed WW37!

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto] Current high bug count owners for Yocto Project 4.3

[linux-yocto][linux-yocto v6.1/standard/ti-sdk-6.1/ti-j7xxx & v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx][PATCH] drivers: media: vxe-vxd: Initialize the variable __value

[linux-yocto]: [kernel/kernel-rt v6.1]: drivers: fsl_qbman: alloc memory with GFP_ATOMIC parameter

[linux-yocto] [PATCH] drivers: fsl_qbman: alloc memory with GFP_ATOMIC parameter

Re: [yocto] Overriding package configuration as a distro

Re: [yocto] Overriding package configuration as a distro

[yocto] Overriding package configuration as a distro

[yocto] Cross-compilation of driver files

[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] debug: add CONFIG_MODULE_ALLOW_BTF_MISMATCH to debug-btf.cfg

[linux-yocto] [PATCH] debug: add CONFIG_MODULE_ALLOW_BTF_MISMATCH to debug-btf.cfg

14 matches

Site Navigation

Mail list logo

Footer information