The dtb.img in your image already has the patch, it doesn't help unfortunately.
from the amlogic mailing list:
It entirely depends on when the kernel use that region. It may never happen, or
it may happen very quickly.
....
For me it doesn't happen randomly but the first time eth activity spikes, with rsync or starting mariadb with the database on a network drive.
So far, ATF and meson-gx.dtsi is aligned for all known gxbb devices.
It's more tricky for gxl and gxm. Some early released devices (such as the kvim)
use the old 0x10000000-0x10200000 (OK) region while most recent one uses
0x5000000-0x5300000 (will trigger the problem).
mine is recent and uses a different region, it uses 0x5300000-0x7300000 if I get it right .....
This is my dts that defines 2 regions, the old 0x10000000-0x10200000 and a different region: 0x5300000 - 0x7300000
Code: Select all
linux,secmon {
compatible = "amlogic, aml_secmon_memory";
reg = <0x0 0x10000000 0x0 0x200000>;
no-map;
linux,phandle = <0x16>;
phandle = <0x16>;
};
linux,secos {
status = "disable";
compatible = "amlogic, aml_secos_memory";
reg = <0x0 0x5300000 0x0 0x2000000>;
no-map;
};
This instead is in your dts:
secmon@10000000 {
reg = <0x0 0x10000000 0x0 0x200000>;
no-map;
};
secmon@05000000 {
reg = <0x0 0x5000000 0x0 0x300000>;
no-map;
};
The patch is already present, but maybe I need a different patch. I will try later to play a bit with the dts so that the NSA backdor doesn't get overwritten. Or maybe I'll ask in themeson-amlogic mailing list first, the board is my mail server, and I hate mail messages like: ' Delivery incomplete
There was a temporary problem delivering your message to xxxx@xxxx. Gmail will retry for 45 more hours. You'll be notified if the delivery fails permanently. '
