-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optee 3.11 cannot initialize imx-watchdog causing cpu stall and heavy network lag #4219
Comments
For the watchdog you'll want #4116 and for the scheduling stalls this patch if you are running with |
@Emantor Thanks for the info. I'll try those patches and close this issue if they work for me. EDIT: your patch unfortunately doesn't solve my issue. The fdt I pass to barebox does define both wd nodes at the location
with the compatible flags your patch uses to find those nodes:
Also, when I run Whe optee searches for the nodes, in kernel/dt.c:157 Apparently optee-os itself is capable to find nodes in general since prior to the search for the watchdog, I can see these msgs: I can imagine 3 possibilities for this behavior:
Do you have an idea how to verify the node location and property offset is correct? |
I just updated the PR, on my nitrogen6x everything works now.
Wdog init from OP-TEE:
|
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
Hey guys,
I am using optee tag 3.11.0 with yocto zeus branch on a custom hardware powered by an i.MX6q SoM. The relvant software I'm using is
I'm facing a problem with network timeouts especially visible with qualcom's QCA7005 and general system lags when I boot optee along with REE. I can boot two different kernels: 4.14.78 and 4.19.100. The later is more sensitive to the problems and lags more frequently as the 4.14.78.
The problems heavily increase when I run some CPU intensive operations in the TA. When optee starts, it tells me it can't perform an Initcall in the method wdog_init().
And when I reboot the system optee panics:
Additionally, when performing CPU intensive operations both kernel stall and or panic. Here are example traces for the 4.14.78 and 4.19.100 kernel:
Sometime I get an network transmit timeout:
I suspect since Optee can't handle the watchdog, the kernel detects the stall, but the eth scheduler doesn't and runs in a timeout. Both watchdogs from the imx_wdog.c:115
are configured in the unsecure devicetree optee is using. My problem seems to relate to this issue: #1353 which was resolved in 2017.
Can someone give me pointers where I should search for the solution since I have now idea how to processd from here on.
Thank you and have nice weekend
Stanislav
The text was updated successfully, but these errors were encountered: