In fact, I didn't see any performance drop because I'm still trying it in a small and initial phase, just want to eliminate any risk when move to debian11, you know if issue happen in production environment, it maybe really not easy to debug.
Back to the question: in lava, if we use debian11 which default cgroupV2 enabled, then when use docker-test-shell, lava will attach a custom BPF Device program to container to replace the default one in docker.
Everything looks fine, just I observed if I use "adb devices" in container, then the trace_pipe will be flushed with next:
```
device poll-7289 [001] d... 103054.767620: bpf_trace_printk: Device access: major = 189, minor = 261
device poll-7289 [001] d... 103055.767851: bpf_trace_printk: Device access: major = 189, minor = 261
device poll-7289 [001] d... 103056.768117: bpf_trace_printk: Device access: major = 189, minor = 261
device poll-7289 [001] d... 103057.768354: bpf_trace_printk: Device access: major = 189, minor = 261
device poll-7289 [001] d... 103058.768590: bpf_trace_printk: Device access: major = 189, minor = 261
device poll-7289 [001] d... 103059.768819: bpf_trace_printk: Device access: major = 189, minor = 261
device poll-7289 [001] d... 103060.769053: bpf_trace_printk: Device access: major = 189, minor = 261
```
Which means that bpf function frequently be called (interval less than 1 second)
On the other hand, if I do next then the BPF prog unregistered from linux kernel, but looks every adb devices still works.
```
/sys/fs/cgroup/system.slice/docker-a9354f54a8c6a56932e15b4d577432abf86c897630d5e94da442474e938bf875.scope
78 device multi lava_docker_dev
$ bpftool cgroup detach /sys/fs/cgroup/system.slice/docker-a9354f54a8c6a56932e15b4d577432abf86c897630d5e94da442474e938bf875.scope device id 78
```
So, I just want to confirm have you guys noticed this behavior, and you confirm this behavior is ok?
(To be honestly, I'm not sure BPF performance if it's frequently be called, so this is just a enquire)
Or, we have better methods handle it in lava?
I need your confirm to decide if I need to downgrade to CGroupV1 when I migrate, thanks!
Regards,
Larry
Hi,
I'm facing an issue after updating the base-uboot file on the server.
*Configuration Error: missing or invalid template.*
*Jobs requesting this device type will not be able to start until a
template is available on the master.*
I have restarted the server and dispatcher but no update. All the devices
went offline automatically.
Any advice to resolve this issue would be appreciated.
Thank you
Hello Team
After facing " Infrastructure ERror: bootloader interrupt ", I have made
changes in the base-uboot.jinja file and restarted the server.
But, it says "*Configuration Error: missing or invalid template.*
Jobs requesting this device type will not be able to start until a template
is available on the master."
Please advise how to fix this.
Thank you
Hi Team,
Good day to you!
I'm making a dispatcher setup to connect new devices and run tests. In
order to do this, I have connected all the required hardware correctly and
created configuration files by following Lava documentation. I Am able to
control the device with the relay board automatically and can login using
telnet.
I'm trying to run my initial test job definition, It downloads the image
but fails to flash the image on device with the below message:
- {"dt": "2022-08-22T09:07:45.799863", "lvl": "debug", "msg": "Calling:
'nice' 'flash' 'pk_raspi-unit1' '{package}'"}
- {"dt": "2022-08-22T09:07:45.809654", "lvl": "debug", "msg": ">>
/var/lib/lava/dispatcher/tmp/466/deploy-flasher-p2k8tvri
/var/lib/lava/dispatcher/tmp/466/deploy-flasher-p2k8tvri\r"}
- {"dt": "2022-08-22T09:07:45.811510", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.811674", "lvl": "debug", "msg": ">> 7-Zip
[64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21\r"}
- {"dt": "2022-08-22T09:07:45.811955", "lvl": "debug", "msg": ">> p7zip
Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,8 CPUs Intel(R)
Core(TM) i5-8265U CPU @ 1.60GHz (806EB),ASM,AES-NI)\r"}
- {"dt": "2022-08-22T09:07:45.812045", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812121", "lvl": "debug", "msg": ">> Scanning
the drive for archives:\r"}
- {"dt": "2022-08-22T09:07:45.812195", "lvl": "debug", "msg": ">> 0M
Scan\b\b\b\b\b\b\b\b\b \b\b\b\b\b\b\b\b\b\r"}
- {"dt": "2022-08-22T09:07:45.812266", "lvl": "debug", "msg": ">> ERROR: No
more files\r"}
- {"dt": "2022-08-22T09:07:45.812366", "lvl": "debug", "msg": ">>
{package}\r"}
- {"dt": "2022-08-22T09:07:45.812434", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812712", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812790", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812860", "lvl": "debug", "msg": ">> System
ERROR:\r"}
- {"dt": "2022-08-22T09:07:45.812929", "lvl": "debug", "msg": ">> Unknown
error -2147024872\r"}
- {"dt": "2022-08-22T09:07:45.813221", "lvl": "debug", "msg": "Returned 2
in 0 seconds"}
- {"dt": "2022-08-22T09:07:45.813306", "lvl": "error", "msg": "Unable to
run 'nice' '['flash', 'pk_raspi-unit1', '{package}']'"}
- {"dt": "2022-08-22T09:07:45.813411", "lvl": "exception", "msg": "Unable
to flash the device"}
Any suggestion to overcome the issue would be very helpful.
Attached log file
Best Regards.
Hi, I’m tying to login to git.lavasoftware.org but neither is my account approved nor does GitHub logins work (500 error).
Could someone please unlock my account or fix the GitHub issue?
Thanks!
Paul
Hi all,
I’m failing to understand how to transfer an overlay (containing tests) to an embedded device.
My device health check runs a Kernel via tftp and works fine. When I’m trying to add tests it fails since the overlay isn’t found. How are tests added when outside of a QEMU instance (which uses mount)?.
My idea was to use SCP but defining a `ssh_host` for for the targeted device gives me an error since power commands are defined. I’m thinking of a workflow like tftpboot -> wait for prompt -> run scp -> run tests.
All I could find in the docs is MultiNode related, which is from my understanding something I don’t want for this very basic testing.
Could someone please give me some advise?
Best,
Paul
Hi all,
I’m planing to test some boards running OpenWrt. Since I have plenty of routers capable to run Python code I’m wondering if someone managed to run a dispatcher/worker outside of Debian?
About 7 years ago people seem to have managed that[1] but the code base changed quite a bit, I figured.
Thanks for all further advice!
Best,
Paul
[1]: https://gitlab.nic.cz/turris/openwrt-lava/-/blob/master/lava-dispatcher/Mak…
Hi,
My console connection terminates if I add the logic to reset my target
physically. But this does not if I reboot my target using "reboot"
I suspect this issue may arise due to re-initiating my target USB-Serial
ftdi driver after target physical power off/on.
Is there any way to re-establish the terminal connection after
physically rebooting my target without terminating?
Attached screenshots.
Regards,
Koti
Hi,
I just want to know if there is any "email" notification facility in our
lava test framework.
Example:
########
1. We need to recevied below notification to configured email id
a. Test trigger info
b. Test complete/canceled/incomplete info
Regards,
Koti
I met this for twice during past years, I use django shell to reset the state, FYI:
sudo lava-server manage shell
from lava_scheduler_app.models import Device
Device.objects.filter(hostname="imx8mm-evk-sh99").update(state=Device.STATE_IDLE)
-----Original Message-----
From: lava-users-request(a)lists.lavasoftware.org <lava-users-request(a)lists.lavasoftware.org>
Sent: Tuesday, June 7, 2022 8:00 AM
To: lava-users(a)lists.lavasoftware.org
Subject: [EXT] Lava-users Digest, Vol 46, Issue 3
Caution: EXT Email
Send Lava-users mailing list submissions to
lava-users(a)lists.lavasoftware.org
To subscribe or unsubscribe via email, send a message with subject or body 'help' to
lava-users-request(a)lists.lavasoftware.org
You can reach the person managing the list at
lava-users-owner(a)lists.lavasoftware.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Lava-users digest..."
Today's Topics:
1. Re: [EXTERNAL] Re: Device stuck in 'Running' (Milosz Wasilewski)
----------------------------------------------------------------------
Message: 1
Date: Mon, 6 Jun 2022 13:39:08 +0100
From: Milosz Wasilewski <milosz.wasilewski(a)foundries.io>
Subject: [Lava-users] Re: [EXTERNAL] Re: Device stuck in 'Running'
To: "Westermann, Oliver" <Oliver.Westermann(a)cognex.com>
Cc: "lava-users(a)lists.lavasoftware.org"
<lava-users(a)lists.lavasoftware.org>
Message-ID:
<CAH1=h_QrLjTp5g+gCgVnZ1fyi+M7tnamAqEngzxjCj--H+2wAw(a)mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Thu, Jun 2, 2022 at 10:36 AM Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote:
>
> Hey,
>
> > From: Milosz Wasilewski <milosz.wasilewski(a)foundries.io>
> >
> > On Tue, May 31, 2022 at 9:04 PM Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote:
> > >
> > > Hey,
> > >
> > > I've a device stuck in 'Running' state, but missing the usual appending of '#<123> <Job Name> [submitter]'.
> > >
> > > Does somebody have some tips how to set/force the device state to 'Idle' manually?
> >
> > I put my bet on lava-dispatcher crashing somewhere along the way.
> > Please try to restart lava-dispatcher and all services around it (webserver, ser2net, etc.).
>
> Did so before my mail request. We're running the docker-compose setup and I've already update (to 2022.05) and restarted (and rebuild) the containers with no success.
That's weird. It should fix the issue
>
> > Once you've done this, you can mark the device "idle" in the admin interface. This should help.
>
> Can you give me some guidance here? The admin interface (as well as the lava-server cli) allow me to set the health (good, bad, maintenance, retired), but not the state.
My bad, you're absolutely right. The state field doesn't seem to be editable. You might need to change it in the DB. I've no idea how it got to this point. In my case when dispatcher is restarted the device status usually fixes itself. One thing to consider is deleting the offending TestJob from DB. This might help (I didn't look at the code to confirm it)
>
> Unrelated sidenote:
> Rebuilding the docker containers failed me.
> The dispatcher requires a file from schneider electric [1], which is currently not available for me.
> I found the file on Remis Github [2] and fixed my Dockerfile locally, but I will try to create a Issue in the gitlab.
It's MIB for APC PDU (or some other Schneider equipment). It's only required if you're using SNMP to talk to PDU with the name instead of it's ASN.1 number. Linaro's lab-scripts [1] make use of this MIB.
[1] https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.linar…
Best Regards,
Milosz
>
> Best regards, Olli
>
> [1]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
> lavasoftware.org%2Flava%2Fpkg%2Fdocker-compose%2F-%2Fblob%2Fmaster%2Fd
> ispatcher%2FDockerfile%23L14&data=05%7C01%7Clarry.shen%40nxp.com%7
> Ce553a3e81ed4483b0aa508da4818b237%7C686ea1d3bc2b4c6fa92cd99c5c301635%7
> C0%7C0%7C637901568148410870%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&s
> data=jQS9w3MoZmp5zq6GwQHleYhWuYRUOAyIEB7mVTPVIvc%3D&reserved=0
> [2]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> ub.com%2Fci-box%2Fci-box-lava-worker%2Fblob%2Fmaster%2Fpowernet428.mib
> &data=05%7C01%7Clarry.shen%40nxp.com%7Ce553a3e81ed4483b0aa508da481
> 8b237%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637901568148410870%
> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
> 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oQ%2B4ZVu7i27IA4%2BHBD3
> mzToa4nLUurFPSP4VoFyojU0%3D&reserved=0
>
------------------------------
Subject: Digest Footer
_______________________________________________
Lava-users mailing list -- lava-users(a)lists.lavasoftware.org To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
------------------------------
End of Lava-users Digest, Vol 46, Issue 3
*****************************************
