From: 张辰 <zhangchen@loongson.cn>
To: devel@edk2.groups.io
Cc: gaoliming <gaoliming@byosoft.com.cn>, lichao <lichao@loongson.cn>,
钱东彦 <qiandongyan@loongson.cn>,
michael.d.kinney@intel.com
Subject: [edk2-devel] Problems with modifying variables after S4 recovery
Date: Fri, 17 Jan 2025 16:42:57 +0800 (GMT+08:00) [thread overview]
Message-ID: <316709e6.1c917.194736e03ba.Coremail.zhangchen@loongson.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hello,
An issue regarding the variable has been encountered on the LoongArch platform. Modifying the variable using efivar after S4 resume will cause data corruption in the flash.
It was found that when starting from S4, the BIOS might write to the variable. After the system resumes, the data in the runtime memory will also be restored, resulting in inconsistent data between that in the VARIABLE_MODULE_GLOBAL structure and the actual data. There is already data in the flash area corresponding to NonVolatileLastVariableOffset.
It's suspected that there will also be problems on other platforms. I'd like to know whether other platforms have encountered similar problems and if there are any solutions?
Thanks
zhangchen@loongson.cn
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121028): https://edk2.groups.io/g/devel/message/121028
Mute This Topic: https://groups.io/mt/110712299/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 6726 bytes --]
reply other threads:[~2025-01-20 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=316709e6.1c917.194736e03ba.Coremail.zhangchen@loongson.cn \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox