Friday, 2021-06-25

*** alimon <alimon!~alimon@2806:10b7:3:491c:2c32:cfff:fe8e:de1f> has joined #yocto00:06
*** alimon <alimon!~alimon@2806:10b7:3:491c:2c32:cfff:fe8e:de1f> has quit IRC (Client Quit)00:06
*** alimon <alimon!> has joined #yocto00:07
*** xicopitz[m] <xicopitz[m]!~xicopitzm@2001:470:69fc:105::4869> has joined #yocto00:08
*** Tokamak_ <Tokamak_!> has quit IRC (Ping timeout: 256 seconds)00:28
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)00:49
*** goliath <goliath!~goliath@user/goliath> has joined #yocto00:50
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Client Quit)00:50
*** jpuhlman_ <jpuhlman_!> has joined #yocto00:59
*** jpuhlman__ <jpuhlman__!> has quit IRC (Ping timeout: 252 seconds)01:03
*** Tokamak <Tokamak!> has joined #yocto02:11
overridecant figure out why its the recipr is trying to cd like that -
moto-timoWARNING: No recipes available for:02:21
moto-timo  /home/ubuntu/oe-core/build/workspace/appends/opentrons_git.bbappend02:21
overridethis is the simple recipe -
overrideive been ignoring that warning, this the recipe in question02:21
overrideive been setting the path for distutils like that plenty of times before, not sure why its giving me crap for this one02:22
moto-timoYou named the main recipe previously. PN = package name == the string before the underscore.02:22
overrideoh shoot, let me check that.02:22
overridemoto-timo: im more concerned about that cd error..02:24
overridethe warning I can fix02:24
overridethe cd error is for the current recipe im working on02:24
moto-timoYou need to share what the notify-see we recipe is we have no clue02:24
overrideoh, thought i put a link in there02:25
overridelet me repost it one sec02:25
overridethis is the recipe -
moto-timoI see it, but you aren’t including the file name so we are partly blind02:25
overridewait what? this is what the file is called -" 18L, 755C02:26
moto-timoLook at your paste bin. No file name info02:27
overrideits called notfy-server_git.bb02:28
overridedoes that help, or were you trying to ask something else02:28
overrideits the do_compile cd step that I have no clue about02:29
moto-timoAlso, we use Debian naming. It should be python3-notify-server_git.bb02:30
overrideoh, think its been cutting me some slack so far02:30
overrideyou think thats problematic ?02:31
overrideor just a convention thing02:31
overrideI wont run into any glob issues or something would I02:31
overrideI had those when I wouldnt get the directory levels right for my recipes02:32
moto-timoShare a git repo with your entire layer. This is madness trying to do it with pastebin.02:33
overrideoh sure one sec02:33
overrideohhh I can just push the workspace folder all these recipes are getting collected in02:34
overridedoes that work?02:34
*** sakoman <sakoman!~steve@> has quit IRC (Quit: Leaving.)02:35
*** sakoman <sakoman!~steve@> has joined #yocto02:37
moto-timoPut it on GitHub or gitlab.02:37
*** vmeson <vmeson!> has quit IRC (Ping timeout: 258 seconds)02:38
*** vmeson <vmeson!> has joined #yocto02:40
moto-timoSeveral of those recipes already exist in meta-python. Do not recreate the wheel.02:43
moto-timoLayers are like lego blocks. Mix and match to build the desired outcome.02:43
overridethink im not goign to reuse those. Thats from when I didnt know any better02:44
overridelike pyserial and all ..02:44
moto-timoI’m no longer going to help you. Good luck.02:44
*** Tokamak <Tokamak!> has quit IRC (Ping timeout: 252 seconds)02:45
overridewe were barely getting started .. jeez02:45
overrideanyone else around who could help me out a lil?02:46
overridejust a link or anything would work too, doesnt have to be too extensive02:47
*** camus1 <camus1!~Instantbi@> has joined #yocto02:50
overrideand moto-timo: think what I said earlier came out wrong - what I meant was Im not going to redo the exisiting recipies - as in I will just reuse them from meta-python. Guess I kinda see why you acted up there lol. Not trying to reinvent the wheel. its all good02:50
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 258 seconds)02:51
*** camus1 is now known as camus02:51
moto-timoMy time is precious. You used up your a lot,02:56
overrideappreciate your time. just thought you wanted to go over the repo with me, so that "Im no longer going to help you. Good luck." sounded rather abrupt..02:58
overrideits all good thought, thanks for all the help02:58
*** Spooster <Spooster!~Spooster@user/spooster> has joined #yocto03:34
*** Vonter <Vonter!~Vonter@> has quit IRC (Quit: WeeChat 3.1)03:37
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto03:39
overridecould use another set of eyes on this, cant figure what Im doing wrong -
*** Vineela <Vineela!~vtummala@user/vineela> has quit IRC (Quit: Leaving.)04:16
*** Spooster <Spooster!~Spooster@user/spooster> has quit IRC (Remote host closed the connection)04:20
*** Spooster <Spooster!~Spooster@user/spooster> has joined #yocto04:20
overrideits all good, i figured it out. something was up with the commit id devtool would pick up. prolly a yocto bug.04:24
*** Spooster <Spooster!~Spooster@user/spooster> has quit IRC (Ping timeout: 246 seconds)04:25
*** sakoman <sakoman!~steve@> has quit IRC (Quit: Leaving.)04:39
*** georgem <georgem!> has quit IRC (Quit: Connection closed for inactivity)04:50
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto04:55
*** davidinux <davidinux!~davidinux@> has joined #yocto05:03
*** Spectrejan[m] <Spectrejan[m]!~spectreja@2001:470:69fc:105::1609> has joined #yocto05:10
*** asus_986_gpu[m] <asus_986_gpu[m]!~asus986gp@2001:470:69fc:105::1014> has joined #yocto05:11
*** shoragan|m <shoragan|m!~shoragans@2001:470:69fc:105::c9f> has joined #yocto05:12
*** fabatera[m] <fabatera[m]!~fabateram@2001:470:69fc:105::18d5> has joined #yocto05:12
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 246 seconds)05:13
*** camus <camus!~Instantbi@> has joined #yocto05:13
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto05:27
*** paulg <paulg!> has quit IRC (Ping timeout: 268 seconds)05:40
*** zpfvo <zpfvo!~fvo@> has joined #yocto05:51
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto05:58
*** rob_w <rob_w!> has joined #yocto06:11
*** LetoThe2nd <LetoThe2nd!> has joined #yocto06:17
LetoThe2ndyo dudX06:20
perdmann_Hi, i created a recipe which creates a shared Object. If i built with yocto everything looks fine, if i built the SDK my so file is not in there.06:38
LetoThe2ndperdmann_: but the rest of the package is? only the object is missing?06:45
*** mckoan|away is now known as mckoan06:48
mckoangood morning06:48
perdmann_LetoThe2nd: its just one .so and a header file. Both are not part of the SDK - but both are built during the "normal image built"06:52
perdmann_LetoThe2nd: i observed this during another RDEPENDS. do i really need to use that .so file in the building process to make it available in the SDK/Image?06:54
perdmann_LetoThe2nd: someone mentioned the "so Solver" but i does not find more sources about it06:54
LetoThe2ndperdmann_: i'd look at the packaging. and theres TOOLCHAIN_HOST_TASK  (or something similar, i can't remember) variable that lets you add stuff to the sdk.06:55
perdmann_LetoThe2nd: thanks, i will try that one06:59
*** florian <florian!> has joined #yocto06:59
LetoThe2ndperdmann_: look it up first, i'm very sure i got it close but not right.06:59
perdmann_TOOLCHAIN_TARGET_TASK and TOOLCHAIN_HOST_TASK. i tried _TARGET_ but looks like its not working. I will investigate again07:04
*** cquast <cquast!~cquast@> has joined #yocto07:04
*** ant_ <ant_!> has quit IRC (Ping timeout: 265 seconds)07:11
*** ilunev <ilunev!~koolkhel@> has joined #yocto07:41
*** kayterina <kayterina!> has joined #yocto07:49
LetoThe2nddoes anybody know if alex gonzales (of yocto cookbook fame) is around?08:00
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)08:00
*** davidinux1 <davidinux1!~davidinux@> has joined #yocto08:04
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 246 seconds)08:07
*** davidinux1 is now known as davidinux08:08
mckoanLetoThe2nd: I only have his LinkedIN connection08:26
LetoThe2ndmckoan: yeah have that too.08:28
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto08:54
*** rodrjassoccom[m] <rodrjassoccom[m]!~rodrjasso@2001:470:69fc:105::4019> has joined #yocto09:05
*** lacouture[m] <lacouture[m]!~lacouture@2001:470:69fc:105::35b7> has joined #yocto09:05
*** tnovotny <tnovotny!> has joined #yocto09:09
*** camus1 <camus1!~Instantbi@> has joined #yocto09:12
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 256 seconds)09:14
*** camus1 is now known as camus09:14
*** dwagenk <dwagenk!~dwagenk@2001:470:69fc:105::103d> has joined #yocto09:34
*** Pierre-jeanTexie <Pierre-jeanTexie!~pjtexierm@2001:470:69fc:105::f2f> has joined #yocto09:43
*** janvermaete[m] <janvermaete[m]!~vermaetem@2001:470:69fc:105::ee7> has joined #yocto09:43
*** Saur[m] <Saur[m]!~saur2000m@2001:470:69fc:105::dce> has joined #yocto09:43
*** Guest6275 <Guest6275!~nobody@> has quit IRC (Quit: WeeChat 3.1)09:50
*** vquicksilver <vquicksilver!~nobody@user/vquicksilver> has joined #yocto09:51
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:05
*** jonesv[m] <jonesv[m]!~jonesvmat@2001:470:69fc:105::4616> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** fabatera[m] <fabatera[m]!~fabateram@2001:470:69fc:105::18d5> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** Spectrejan[m] <Spectrejan[m]!~spectreja@2001:470:69fc:105::1609> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** shoragan|m <shoragan|m!~shoragans@2001:470:69fc:105::c9f> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** dwagenk <dwagenk!~dwagenk@2001:470:69fc:105::103d> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** lacouture[m] <lacouture[m]!~lacouture@2001:470:69fc:105::35b7> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** rodrjassoccom[m] <rodrjassoccom[m]!~rodrjasso@2001:470:69fc:105::4019> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** xicopitz[m] <xicopitz[m]!~xicopitzm@2001:470:69fc:105::4869> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** asus_986_gpu[m] <asus_986_gpu[m]!~asus986gp@2001:470:69fc:105::1014> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** Pierre-jeanTexie <Pierre-jeanTexie!~pjtexierm@2001:470:69fc:105::f2f> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** Saur[m] <Saur[m]!~saur2000m@2001:470:69fc:105::dce> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** janvermaete[m] <janvermaete[m]!~vermaetem@2001:470:69fc:105::ee7> has quit IRC (Quit: Bridge terminating on SIGTERM)10:28
*** Andrei[m] <Andrei[m]!~andreicub@2001:470:69fc:105::c95> has joined #yocto10:30
*** kayterina[m] <kayterina[m]!~kayterina@2001:470:69fc:105::960> has joined #yocto10:30
*** jordemort <jordemort!~jordemort@2001:470:69fc:105::2d9> has joined #yocto10:36
*** Jari[m] <Jari[m]!~jarihmatr@2001:470:69fc:105::6a7> has joined #yocto10:36
*** janvermaete[m] <janvermaete[m]!~vermaetem@2001:470:69fc:105::ee7> has joined #yocto10:36
*** Emantor[m] <Emantor[m]!~emantorm]@2001:470:69fc:105::8eb> has joined #yocto10:36
*** Saur[m] <Saur[m]!~saur2000m@2001:470:69fc:105::dce> has joined #yocto10:36
*** shoragan[m] <shoragan[m]!~shoraganm@2001:470:69fc:105::39> has joined #yocto10:36
*** khem <khem!~khemmatri@2001:470:69fc:105::b81> has joined #yocto10:36
*** cody <cody!~cody@user/cody> has joined #yocto10:36
*** Pierre-jeanTexie <Pierre-jeanTexie!~pjtexierm@2001:470:69fc:105::f2f> has joined #yocto10:36
*** ejoerns[m] <ejoerns[m]!~ejoernsma@2001:470:69fc:105::252> has joined #yocto10:36
*** moto_timo[m] <moto_timo[m]!~mototimom@2001:470:69fc:105::c94> has joined #yocto10:36
*** barath <barath!~barath@2001:470:69fc:105::21a> has joined #yocto10:36
*** ndec[m] <ndec[m]!~ndecmatri@2001:470:69fc:105::9c0> has joined #yocto10:36
*** WadeBerrier[m] <WadeBerrier[m]!~wberrierm@2001:470:69fc:105::3f0e> has joined #yocto10:36
*** Alban[m] <Alban[m]!~albeugaen@2001:470:69fc:105::34b4> has joined #yocto10:36
*** keepitsimplejim[ <keepitsimplejim[!~keepitsim@2001:470:69fc:105::3630> has joined #yocto10:36
*** shoragan|m <shoragan|m!~shoragans@2001:470:69fc:105::c9f> has joined #yocto10:36
*** Spectrejan[m] <Spectrejan[m]!~spectreja@2001:470:69fc:105::1609> has joined #yocto10:36
*** fabatera[m] <fabatera[m]!~fabateram@2001:470:69fc:105::18d5> has joined #yocto10:36
*** jonesv[m] <jonesv[m]!~jonesvmat@2001:470:69fc:105::4616> has joined #yocto10:36
*** PascalBach[m] <PascalBach[m]!~bachpmatr@2001:470:69fc:105::1d3b> has joined #yocto10:36
*** xicopitz[m] <xicopitz[m]!~xicopitzm@2001:470:69fc:105::4869> has joined #yocto10:36
*** lacouture[m] <lacouture[m]!~lacouture@2001:470:69fc:105::35b7> has joined #yocto10:36
*** alex88[m] <alex88[m]!~alex88moz@2001:470:69fc:105::ce4> has joined #yocto10:36
*** rodrjassoccom[m] <rodrjassoccom[m]!~rodrjasso@2001:470:69fc:105::4019> has joined #yocto10:36
*** asus_986_gpu[m] <asus_986_gpu[m]!~asus986gp@2001:470:69fc:105::1014> has joined #yocto10:36
*** AlessandroTaglia <AlessandroTaglia!~al3x88mat@2001:470:69fc:105::ce3> has joined #yocto10:36
*** dwagenk <dwagenk!~dwagenk@2001:470:69fc:105::103d> has joined #yocto10:36
*** yates_work <yates_work!> has quit IRC (Remote host closed the connection)10:42
*** georgem <georgem!> has joined #yocto10:50
*** xmn <xmn!> has quit IRC (Ping timeout: 258 seconds)10:51
*** camus1 <camus1!~Instantbi@> has joined #yocto10:51
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)10:52
*** camus1 is now known as camus10:52
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)10:58
*** tnovotny <tnovotny!> has joined #yocto11:03
*** camus <camus!~Instantbi@> has quit IRC (Quit: camus)11:40
*** bluelightning <bluelightning!~paul@2406:e003:12a7:7601:89e6:905f:8fed:afbb> has quit IRC (Quit: Konversation terminated!!!111)11:44
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)11:49
*** rob_w <rob_w!> has quit IRC (Quit: Leaving)11:57
*** LetoThe2nd <LetoThe2nd!> has quit IRC (Quit: Connection closed for inactivity)12:14
*** davidinux1 <davidinux1!~davidinux@> has joined #yocto12:25
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 250 seconds)12:25
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)12:30
*** tnovotny <tnovotny!> has joined #yocto12:34
*** Spooster <Spooster!~Spooster@user/spooster> has joined #yocto12:38
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)12:39
overridehow can I force clean a package's sources?12:46
RPjonmason: testimage works with slirp?12:46
*** davidinux1 <davidinux1!~davidinux@> has quit IRC (Ping timeout: 250 seconds)12:46
overridestuff under workspace/sources12:46
overridefor some reason all the stuff from a git repo isnt getting fetched for the commit id Im setting up a recipe with...12:48
*** davidinux1 <davidinux1!~davidinux@> has joined #yocto12:48
overridetrying to run devtool clean recipe or something but those options tell me do_clean isnt set..12:49
overrideany way to just force clean the source for a recipe ?12:49
tnovotnyoverride: this will clean everything (including sstate cache): bitbake -c cleanall <recipe>12:52
*** paulg <paulg!> has joined #yocto12:53
jonmasonRP: yes.  It took way longer than it should've for me to find the extra things to enable to get it working, but it's passing the boot test.  Seeing some issues on some platforms with dropbear/ssh.  So, I'll add that (and extra tests) in the future12:54
tnovotnyoverride: but I'm not using devtool yet, so I might be missing something12:54
overridetnovotny: ive been trying to clean that way. been seeing this,
jonmasonRP: Also, I'm trying it on dev kernels as well
jonmasonrisc-v is breaking, which is probably normal ;-)12:56
overridethe overaching problem here is how the recipe is conviniently skipping some stuff out from the commit Im poininting it to..12:59
overrideso i was trying to bitbake clean and maybe try other commits or something12:59
RPjonmason: the boot test is pretty basic, am just wondering about some of the others that use ssh13:04
zeddRP / jonmason: when I was getting set up to debug the LTP issue, I figured out the tweaks to get ssh login, etc, passing with slirp. so in theory, it should be doable.13:06
zeddbut I've flushed it from the cache, and can't quite recall everything I changed :D13:06
tnovotnyoverride: hmm, I have no idea...btw the missing yarn in the output is strange. Is it possible that it is related?13:06
RPzedd, jonmason: would be good to document this somewhere13:07
zeddthe box I was doing the tests on, is still largely unchanged from that, I can go have a look later.13:07
RPzedd: I have a horrible kernel hack to make the rcu stall detector 3s in master-next. Is there anything else we could do to try and provoke it you know of?13:07
overridethink bitbake just trying doing that when it sees a make file or something in the repo.. I can build fine with the recipe tho, I just inherit setuptools3 .. :tnovotny13:07
jonmasonRP: has dropbear working, but the other qemus that meta-arm cares about failed13:09
zeddRP: to make it the stall trigger in a shorter time ? i.e. more than tweaking: /sys/module/rcupdate/parameters/rcu_cpu_stall_timeout ?13:11
RPzedd: Yes, just wondering if there is anything else we could tweak to maybe make it fail more frequently.13:16
RPzedd: if changing this doesn't change the frequency of failures on the AB, I think that tells us something13:16
zeddright. That's the biggest runtime knob, but the docs talk about some macro's in the kernel that can be changed to lower some thresholds. are those the ones that you changed in your run ?13:20
RPzedd: no, I just started with
*** zpfvo <zpfvo!~fvo@> has quit IRC (Remote host closed the connection)13:44
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: Textual IRC Client:
zeddRP: yup, that's where I would have started as well.  There's some potential in the options hidden under RCU_EXPERT, but they are more for runing, and doing rcu offloads, etc, probably wouldn't help much here.13:47
zeddbut we could always clear the rcu cbs off a core (if we are smp) and see if it makes a difference.13:47
RPzedd: right, that could be an interesting experiment. I guess I'll see what the current  experiment shows. Do you know if there is a way to trigger a dummy stall just to test the kernel reporting?13:49
zeddthe rcu torture tests might be able to do that. I'll have a look at the docs for them. I haven't run them myself, but pauk mkinny is always tweaking them.13:50
RPzedd: I'd like to try and see if the stall crashes the system or whether the system is crashed and the stall is just a symptom. The kernel BUG: yesterday makes me suspcious13:51
zeddwe could also make sure that CONFIG_RCU_TRACE is on in the future (along with the other kernel debug options), to see if that can help us glean more about the cause.13:51
* zedd wonders how long until someone asks for a rcutorture name change13:52
*** Guest55 <Guest55!~Guest55@> has joined #yocto13:54
*** Guest55 <Guest55!~Guest55@> has quit IRC (Client Quit)13:55
zeddthere's also panic_on_rcu_stall, which might dump more information to the vmcore, or maybe that is what was already tried when you talked about the vmcore.13:55
zeddan yah, I can't see anyway to trigger a dummy stall at the moment.13:57
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto13:58
*** sakoman <sakoman!~steve@> has joined #yocto14:02
RPzedd: we pulled the vmcore from qmp out from qemu14:04
RPzedd: I think I might add a sysctl to trigger a stall14:04
*** ant_ <ant_!> has joined #yocto14:33
*** OutBackDingo_ is now known as OutBackDingo14:35
rburtonzedd: today's discovery: linux-yocto won't boot in lkvm14:47
*** ilunev <ilunev!~koolkhel@> has quit IRC (Quit: Textual IRC Client:
zeddaka kvmtool ?14:52
zeddyah. I've never tried to boot in using it myself, so I have no config fragments for it.14:52
rburtoni have docs14:52
overridecan anyone please tell me whats going on with my bitbake here -
rburtonmoto-timo: thats obsolete14:52
moto-timoThanks Google14:53
rburtonlike how yocto docs give you 1.6 releases14:54
zeddoverride: the bitbake server hung, it can happen. just find the bitbake processes and kill them.14:57
*** wesm <wesm!> has quit IRC (Ping timeout: 265 seconds)14:59
*** p34nutz <p34nutz!> has joined #yocto15:00
overridethanks zedd15:12
overridezedd: so this what makes it hang to begin with, Im trying to undersatnd what an ExpansionError is -
*** wesm <wesm!> has joined #yocto15:14
RPabelloni, zedd: We have at least one rcu failure in the builds on the AB. Just trying to think of the best way to track this as it requires sshing in to check in many cases :/15:16
RPzedd, abelloni: Looks like that patch in master-next is causing mayhem, tons of crashed/broken stuff :)15:23
RPzedd: conclusion - the stall messsages in the kernel cause the kernel to break somehow :/15:24
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)15:26
zeddsome sort of non graceful recovery from the stall state perhaps.15:34
RPzedd: that is my thinking. I just mailed out 4 backtraces/stall reports15:34
RPpaulg, zedd: this is looking very kernel related now15:35
zeddRP: one other question. do all the hangs / crashes have rcu stalls ?15:35
RPzedd: yes15:36
zeddso have you tried the opposite ? set the stall to some unreachable timeout ?  and see if the hangs just never report the same way ? i.e. an oom or something similar ?15:37
RPzedd: I have not. You have my live data15:37
RPzedd: I have never seen a build with as many hangs though15:37
* zedd nods15:38
RPzedd: if that were the issue, with the original threshold we should have been seeing more oom/other messages which we haven't15:38
* paulg wonders if he can get away with playing the Schultz "I know nothing" card...15:42
*** kayterina <kayterina!> has quit IRC (Remote host closed the connection)15:45
RPpaulg: it isn't working ;-)15:46
RPpaulg: particularly as I also know *nothing* about rcu and yet I'm this far... :)15:50
paulgI thought the LTP thing would buy me a free pass for at least a week...15:56
RPpaulg: I was hoping the LTP issue and this were the same thing :/15:59
*** mckoan is now known as mckoan|away15:59
RPmanually running print_cpu_stall() with the "suppressed" bit hacked out doesn't seem to crash my local qemu16:00
RPbut it doesn't print any cpu traces either16:01
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)16:13
RPand even forcing CPU traces and load onto cpus, doesn't crash16:19
RPpaulg: actually, could you look at something for me? I think I can see a locking bug.16:40
RPpaulg: rcu_print_task_stall() in kernel/rcu/tree_stall.h - that return 0;16:40
RPzedd: ^^^ if you fancy a look16:41
paulgbaseline?  5.10.43?16:41
RPpaulg: 5.10.4316:41
paulggot a bunch of goings on today but will look quickly now.16:41
RPpaulg: look at where its called and the comment, then the code...16:42
RP(all in that file)16:42
paulg?   the return 0  comes at the top if there is nothing to do.   I don't see anything.16:45
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 256 seconds)16:45
RPpaulg: note the "raw_spin_unlock_irqrestore_rcu_node(rnp, flags);" below and "ndetected += rcu_print_task_stall(rnp, flags); // Releases rnp->lock."16:46
paulgI guess you gave me the wrong fcn name16:47
paulgprint_other_cpu_stall   vs.  rcu_print_task_stall  ?16:47
RPpaulg: no, that name is right :/16:48
paulgok, lemme look some more16:48
RPstatic int rcu_print_task_stall(struct rcu_node *rnp, unsigned long flags)16:48
RPperhaps I'm missing something obvious :/16:49
paulgok, now I think I see what you are saying.16:50
paulgnow I have to find what is obvious that we are both missing.16:50
RPpaulg: basically that function is supposed to release that lock and doesn't when it hits the return 0 path16:52
RPpaulg: and that could give the BUG: scheduling when atomic we've seen16:52
paulgyeah  I see the stub for ! PREEMPT_RCU releases the lock, so I'm failing to prove you wrong so far....16:53
RPrcu_preempt_blocked_readers_cgp() could conceivably do something but is handled with locks elsewhere so seems unlikely16:53
paulglemme do a bit of git blame and check mainline and then if paul is around maybe go check with him.16:54
paulgit does seem a bit sus though --  I'll grant you that.16:55
RPpaulg: looks the same in mainline too16:55
RPpaulg: sorry to add to your plate but thanks, does seem odd and worth looking at16:55
RPpaulg: definitely would explain a few things16:56
RPpaulg: also, its only called by print_other_cpu_stall() and I was testing my sysrq with print_cpu_stall()17:01
paulgso basically you might have found a bug - just not the one you were looking for.   :-P17:01
RPpaulg: no, I think this could be it17:02
paulglooking at 3fc3d1709fc  currently....17:02
RPpaulg: definitely fits the two BUG: in those backtraces I sent17:02
ant_you guys have a perfect week-end timing17:02
* paulg hasn't read email yet today. :-/17:06
* paulg wasn't here yesterday.17:06
RPpaulg: its c583bcb8f5edd48c1798798e341f78afb9bf4f6f17:07
paulgyeah looking at that commit already17:09
paulgintroduces the "interesting" locking.17:09
RPpaulg: I need to head afk for food. I'm going to queue a fix in master-next and ask it be started on the autobuilder after maint completes17:12
RPpaulg:  we can run it with the other patch to lower the timing so we'll hopefully see a few rcu stalls but no crashes17:12
paulgI'll see if I can scare up paulmck17:12
RPpaulg: thanks. Its help to have a sanity check I'm not missing anything obvious17:13
RPhalstead: after maint could we schedule a master-next build of a-full please to test this change?17:14
RPpaulg: is my attempted fix17:15
* RP -> afk17:15
*** Vineela <Vineela!~vtummala@user/vineela> has joined #yocto17:26
paulgfor those following along at home, it seems a fix is already in,  just hasn't completed the mainline --> stable --> zedd/yocto  circuit quite yet.17:29
*** behanw <behanw!> has joined #yocto18:18
ecdheI have a recipe that doesn't inherit any bbclass.  I set some variables, that's okay, but when I add do_configure(), I get the error " unparsed line: 'do_configure()'"18:32
ecdheThe line above it is "S = "${WORKDIR}/git""18:32
ecdheI put the entire line in quotes on irc but should have left it: S = "${WORKDIR}/git"18:33
ecdheWhen I remove do_configure, there's no parse issue.18:33
ecdheI changed the function name to my_do_configure, and even to a random identifier, but any task I attempt to define results in an "unparsed line" error18:34
*** LetoThe2nd <LetoThe2nd!> has joined #yocto18:40
ecdheokay, got it: you have to use K&R brace placement, so "do_configure() { "18:56
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Remote host closed the connection)19:20
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto19:20
*** goliath <goliath!~goliath@user/goliath> has joined #yocto19:23
*** vmeson <vmeson!> has quit IRC (Ping timeout: 246 seconds)19:26
*** vmeson <vmeson!> has joined #yocto19:32
*** Guest15 <Guest15!~Guest15@> has joined #yocto19:34
*** behanw[m] <behanw[m]!~behanwmat@2001:470:69fc:105::c96> has joined #yocto19:47
*** TrevorWoerner[m] <TrevorWoerner[m]!~trevorwoe@2001:470:69fc:105::4e57> has joined #yocto19:54
*** dev1990_ <dev1990_!> has quit IRC (Quit: Konversation terminated!)20:10
*** p34nutz <p34nutz!> has quit IRC (Quit: Client closed)20:12
ecdheI've got a recipe that requires a gcc3 or gcc4 cross compiler.  I'm working in dunfell.20:19
paulginteresting - that is rather retro.20:19
ecdheI probably need to just cherry pick a denzil recipe and add it to my own layer20:20
ecdheunless there is a faster way I haven't considered20:20
ecdheI wish yocto would keep more recipe versions around for reverse compatibility20:20
ecdhepaulg: this user is having my same issue:
ecdheThe cross compiler I'm using is too new20:21
ecdheanother option could be to patch the old kernel just enough to be built with a newer compiler20:21
paulgI wouldn't recommend that.20:22
paulgany reason why you can't simply build the kernel outside of yocto and plop it into your image?20:23
ecdhepaulg: may want to iterate on it, want to have things source controlled if possible20:23
ecdhebut archiving the binaries is an option too20:23
ecdhethe layer system is brilliant20:24
ecdhepaulg: why would you recommend against patching the kernel?20:27
paulgthe reason I don't recommend patching the old to build with the new, is that you are straying into unchartered waters, as nobody else has probably done that and updated the old source appropriately ;  so you've lost the implicit run-time validation of *all* the original user base for whatever it is you are working on.20:28
paulgsure, you can make it *compile* but what if the compiler does an optimization on some lock ordering that the old compiler never did and the old source never anticipated?20:29
paulgif you are just hacking around on some personal project then maybe that isn't a concern.20:30
*** wesm <wesm!> has quit IRC (Remote host closed the connection)20:31
*** florian <florian!> has quit IRC (Ping timeout: 265 seconds)20:40
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto20:42
abellonimy answer would be "simply upgrade your kernel"20:44
abelloniyou don't want to ship a product on 2.6.x20:44
abellonior 3.x20:45
paulgor 4.x   :-)20:45
abelloniyes too but I'll accept 4.19 ;)20:46
paulganyway who knows if ecdhe is fighting with an old product being sustained, or limited RAM resources or what -  I'm sure an upgrade was considered if at all possible.20:48
*** florian <florian!> has joined #yocto20:52
abelloniyes but I don't see the point in updating userspace if the kernel is full of holes21:01
abelloniand also upgrading userspace will have a bigger impact on storage/memory size than just the kernel21:01
*** hauke <hauke!> has joined #yocto21:07
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 258 seconds)21:17
*** florian <florian!> has quit IRC (Ping timeout: 252 seconds)22:15
*** cquast <cquast!~cquast@> has quit IRC (Ping timeout: 258 seconds)22:17
*** florian <florian!> has joined #yocto22:32
*** LetoThe2nd <LetoThe2nd!> has quit IRC (Quit: Connection closed for inactivity)22:39
*** alejandr1 <alejandr1!> has quit IRC (Ping timeout: 265 seconds)22:44
ecdhepaulg: on may way to having original compiler available23:09
ecdheno kernel mods23:09
*** florian <florian!> has quit IRC (Ping timeout: 252 seconds)23:21
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (Remote host closed the connection)23:33
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto23:37

Generated by 2.17.2 by Marius Gedminas - find it at!