enok has quit [Read error: Connection reset by peer]
enok71 has joined #yocto
enok71 has quit [Ping timeout: 245 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
rob_w has joined #yocto
khimaros has quit [Remote host closed the connection]
khimaros has joined #yocto
frgo has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
alessio has joined #yocto
Vonter has joined #yocto
eduter has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
Vonter has quit [Ping timeout: 276 seconds]
dlan has quit [Ping timeout: 252 seconds]
GNUmoon has quit [Remote host closed the connection]
Vonter has joined #yocto
GNUmoon has joined #yocto
frgo has joined #yocto
dlan has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
dlan has quit [Ping timeout: 245 seconds]
dlan has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
dlan has quit [Ping timeout: 252 seconds]
dlan has joined #yocto
dlan has quit [Ping timeout: 260 seconds]
dlan has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 244 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
enok has joined #yocto
frgo has joined #yocto
enok has quit [Ping timeout: 246 seconds]
frgo has quit [Ping timeout: 276 seconds]
rfuentess has joined #yocto
leon-anavi has joined #yocto
davidinux has quit [Quit: WeeChat 4.3.1]
florian has joined #yocto
frgo has joined #yocto
frgo has quit [Read error: Connection reset by peer]
frgo has joined #yocto
ptsneves has joined #yocto
frgo has quit [Remote host closed the connection]
ablu has quit [Ping timeout: 268 seconds]
ablu has joined #yocto
florian_kc has joined #yocto
ptsneves has quit [Remote host closed the connection]
frgo has joined #yocto
frgo has quit [Ping timeout: 246 seconds]
sakoman1 has joined #yocto
sakoman has quit [Ping timeout: 276 seconds]
Dracos-Carazza_ has joined #yocto
Dracos-Carazza has quit [Ping timeout: 265 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
Dracos-Carazza_ has quit [Ping timeout: 244 seconds]
Dracos-Carazza has joined #yocto
berton has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
<berton>
Hello! I'm trying to create a small rootfs using ext4 with 1k block size. The rootfs size needs to be 20M, the du command shows that the IMAGE_ROOTFS directory is 23M because my filesystem has 4k blocks. The directory_size function https://git.openembedded.org/openembedded-core/commit/?id=6ca53ad7b26ee2b4e6d2c121c6f6d6eed7f6b56f uses hardcoded 4k and the rootfs size is always larger than 20M. How can I create a small rootfs?
<mcfrisk>
berton: you can check with bitbake -e how the ext4 do_image* tasks are constructed and try to influence the block size argument to mkfs.ext4. it may be that defaults are used and they are now 4k in mkfs.ext4. See IMAGE_CMD and EXTRA_IMAGECMD veriables for example
<mcfrisk>
berton: set ROOTFS_SIZE manually in recipe or build config?
sugarbeet has quit [Ping timeout: 248 seconds]
<mcfrisk>
the estimates are hard to get right and need to be correct for the general case, not absolutely optimized for small size. block sizes matter, and then again they don't because modern HW and mmc with much larger blocks..
<mcfrisk>
and all this depends on what is the build output format, e.g. wic, and how that is flased to target HW and which block device is used there..
<mcfrisk>
the build output container can be bigger than what actually is written to target in partition data.
goliath has joined #yocto
<mcfrisk>
for absolute control, you can introduce your own image format and run exactly those mkfs.ext4 etc commands that you know are correct
<berton>
mcfrisk: I'll try to do that. I need to check here how to do that, because it's in a project that creates more than one rootfs. Thanks!
<mcfrisk>
berton: no problem, good luck. these details are not easy to get right. often the optimisations are not worth the effort :)
frgo has joined #yocto
frgo has quit [Ping timeout: 268 seconds]
Ad0 has joined #yocto
<mcfrisk>
Is wic selftest test_permissions failing for anyone else? on my aarch64 machine it consistently fails with pseudo abort: path mismatch [2 links]: ino 36325576 db '../tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0/rootfs/var/log' req '.../tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0/tmp-wic/rootfs1/var/log'
sugarbeet has joined #yocto
<CrazyGecko>
Is there a difference between the devshell and the shell used by the yocto build environment? Especially, the ssh-agent does not seem in a task I created on my own as in the do_fetch task
<mcfrisk>
CrazyGecko: major differences, devshell is the build env seen by bitbake tasks and they on purpose don't see everything from shell env calling bitbake.
<CrazyGecko>
mcfrisk: hmm. so that would mean, when I do `bitbake -c devshell my_recipe` and `bitbake -c my_task my_recipe`, they should have the same environment and in my case the same ssh-agent? I'm asking because this differs in my case. I will try to find out more with the link you sent, thanks.
<mcfrisk>
files on build server, like $HOME/.netrc for various authentication bits for git, svn, curl/http etc
rob_w has quit [Remote host closed the connection]
Jones42 has quit [Ping timeout: 268 seconds]
olani has quit [Ping timeout: 260 seconds]
olani has joined #yocto
<CrazyGecko>
mcfrisk: thanks. I fear, this is where my issue comes from.
<mcfrisk>
CrazyGecko: ok, note that env variables easily leak into build output logs or even binaries so don't put secrets there
frgo has joined #yocto
frgo has quit [Ping timeout: 244 seconds]
<CrazyGecko>
mcfrisk: thanks that's a good hint. I think what I should get there is mostly the `SSH_AGENT_PID` and the `SSH_AGENT_PID`, which, sadly for my debugging, are already defined in `BB_ENV_PASSTHROUGH_ADDITIONS`. So I need further debugging, why this is not working in the "automatic" task procedure
savolla has joined #yocto
rfuentess has quit [Quit: QUIERO CHELAS!]
enok has joined #yocto
enok71 has joined #yocto
enok has quit [Ping timeout: 272 seconds]
enok71 is now known as enok
frgo has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
eduter has quit [Quit: Client closed]
eduter has joined #yocto
florian_kc has quit [Ping timeout: 246 seconds]
florian has quit [Ping timeout: 244 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 265 seconds]
frgo_ has joined #yocto
frgo_ has quit [Remote host closed the connection]
frgo has joined #yocto
florian has joined #yocto
florian_kc has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
olani- has joined #yocto
alessio has quit [Quit: alessio]
enok71 has joined #yocto
Jones42 has joined #yocto
enok has quit [Ping timeout: 245 seconds]
enok71 is now known as enok
enok has quit [Ping timeout: 276 seconds]
Jones42 has quit [Ping timeout: 244 seconds]
savolla has quit [Quit: WeeChat 4.4.3]
savolla has joined #yocto
savolla has quit [Read error: Connection reset by peer]
078AA6DO6 has joined #yocto
047ABD9UT has joined #yocto
ello_ has quit [Ping timeout: 252 seconds]
savolla has joined #yocto
ello has quit [Ping timeout: 265 seconds]
florian_kc has quit [Ping timeout: 252 seconds]
florian has quit [Ping timeout: 260 seconds]
florian has joined #yocto
jmiehe has joined #yocto
florian_kc has joined #yocto
olani- has quit [Ping timeout: 260 seconds]
Xagen has joined #yocto
<CrazyGecko>
It seems like there is no ssh-agent running in the environment of the tasks. ssh-add -l does not work there and when I look at the `ssh -vvv` log and compare to a local (not in the yocto environment) log, no interaction with an agent is done in the yocto context. I'm wondering if there that should be the case since the `SSH_AGENT_SOCKET` are given
<CrazyGecko>
to the environment
tgamblin has quit [Remote host closed the connection]
florian has quit [Killed (NickServ (GHOST command used by florian_kc))]
florian_kc is now known as florian
florian has quit [Ping timeout: 260 seconds]
enok has joined #yocto
cyxae has joined #yocto
reatmon_ has joined #yocto
Tyaku has quit [Ping timeout: 252 seconds]
<reatmon_>
What is the best way to debug an sstate cache miss issue? We do several platforms builds per night and most get about the same high cache hit since nothing changes that much. But recently we have a single build platform that is consistently seeing a 0% cache hit, every time... How can I debug what the issue is?
cyxae has quit [Client Quit]
cyxae has joined #yocto
Tyaku has joined #yocto
florian has joined #yocto
savolla has quit [Quit: WeeChat 4.4.3]
savolla has joined #yocto
florian has quit [Ping timeout: 252 seconds]
<Tyaku>
your documentation about watchdog was very interesting, r b u r t o n (prevent highlight). I was missing RuntimeWatchdogSec in system.conf,
<Tyaku>
Now we have other issues around watchdog but not for this channel: We have two watchdogs in the board RZG2UL + DA9062, We would like to use the DA9062 because it can trigger the reset of the whole board (also other radio chips), but there are issues with it. For exemple when the system poweroff, it provoque failures due to the fact it use I2C interrutp and at shutdown interrupts are stopped. Also with DA9062
<Tyaku>
driver, when the watcdog is triggered (nRESET from the PMIC stay LOW)
florian has joined #yocto
rcwoolley has joined #yocto
cyxae has quit [Remote host closed the connection]
frgo has quit [Quit: Leaving...]
frgo has joined #yocto
sakman_ has joined #yocto
tgamblin_ has joined #yocto
TheOneCurly has quit [Quit: Ping timeout (120 seconds)]
cyxae has joined #yocto
TheOneCurly has joined #yocto
tgamblin has quit [Ping timeout: 252 seconds]
sakman has quit [Ping timeout: 252 seconds]
<Tyaku>
But I have a question for this channel: I have a driver esp_hosted_ng that has a lot of bugs, we need to debug it, I read about kgdb and I did the required modification in the kernel to make it possible. But now I am just blocked at a "minor" step: I need the .ko of my module with the debug information. (No debugging symbols found in) I don't know how to get it. Do I have to install the -dbg version of the
<Tyaku>
In my IMAGE_INSTALL I changed esp-hosted-ng-mod by esp-hosted-ng-mod-dbg, unfortunately the .ko file has the same size, and does not have debug informations. After some research I found that I also need CONFIG_DEBUG_INFO=y, I try recompiling the kernel with it.
Tyaku has quit [Ping timeout: 244 seconds]
florian has joined #yocto
Tyaku has joined #yocto
enok has quit [Remote host closed the connection]
<JPEW>
Tyaku: Not sure about kernel modules, but usually the debug info is split out into a separate file
<Tyaku>
my esp-hosted-ng.ko is now about 4.1MB instead of 156kB, I think it worked. I am finishing building the image, flashing and try again .
<rburton>
absolutely in favour of adding the padding flag to the default cflags when we merge gcc15
florian has joined #yocto
<zeddii>
are we going to do gcc15 on the LTS ? I could cherry pick something like that now, or wait until we release and then add the support. Although it doesn't look like it would cause issues with gcc14, etc.
<rburton>
i expect we'll upgrade the toolchain over the spring/summer so that will be backported to the kernels we build before we upgrade the toolchains
florian_kc has joined #yocto
berton has quit [Ping timeout: 276 seconds]
<zeddii>
yah. and unlike some other things like newer hosts on the LTS, we won't be upgrading gcc in the LTS. If someone did it in a mixin, then it would have been picked up by the -stable kernels by then as well.
florian has quit [Ping timeout: 252 seconds]
eduter has quit [Quit: Client closed]
florian_kc has quit [Ping timeout: 272 seconds]
florian_kc has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
<khem>
rburton: thanks for sharing, zeddii yes LTS in 2026 will be gcc15 if current schedules for gcc and yocto hold
<khem>
if you cherry picked atleast into 6.12 then it will help testing our gcc15 porting work, although I have not tripped into this error explicitly
<Tyaku>
Currently I arrive to debug with kdbg + gdb, I just have one issue, on remote computer GDB have paths like this: /usr/src/kernel/include/asm-generic/atomic-instrumented.h this file isn't in /usr/src/.../ but in kernel-sources
<khem>
whats the exact path ?
<khem>
where the file is actually in
<Tyaku>
arch_kgdb_breakpoint () at /usr/src/kernel/arch/arm64/include/asm/kgdb.h:21
<Tyaku>
it should be in /mnt/project/git/xxx/build-xxx/tmp/work-shared/yyyyy/kernel-source arch/arm64/include/asm/kgdb.h for example
<Tyaku>
I try to configure 'set substitute-path X Y' without effect
<Tyaku>
Where X = /usr/src/kernel and Y is /mnt/project/git/xxx/build-xxx/tmp/work-shared/yyyyy/kernel-source
JaMa has quit [Quit: reboot]
leon-anavi has quit [Quit: Leaving]
<khem>
what does show substitute-path say?
khem has quit [Quit: WeeChat 4.5.2]
enok has joined #yocto
sakman_ is now known as sakman
<Tyaku>
show substitute-path correctly display the substition path, so X Y
Tyaku has quit [Quit: Lost terminal]
enok has quit [Read error: Connection reset by peer]
florian_kc has joined #yocto
enok has joined #yocto
mischief has quit [Ping timeout: 272 seconds]
mischief has joined #yocto
ptsneves has joined #yocto
ptsneves has quit [Remote host closed the connection]
enok has quit [Ping timeout: 276 seconds]
tec4 has quit [Quit: bye!]
tec4 has joined #yocto
enok has joined #yocto
JaMa has joined #yocto
rcwoolley has quit [Ping timeout: 245 seconds]
pidge_ has quit [Ping timeout: 245 seconds]
pidge has joined #yocto
cyxae has quit [Quit: cyxae]
pidge has quit [Ping timeout: 260 seconds]
florian_kc has quit [Ping timeout: 252 seconds]
Kubu_work has quit [Quit: Leaving.]
zwelch has quit [Read error: Connection reset by peer]