public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
* [edk2-devel] Problems with modifying variables after S4 recovery
@ 2025-01-17  8:42 张辰
  0 siblings, 0 replies; only message in thread
From: 张辰 @ 2025-01-17  8:42 UTC (permalink / raw)
  To: devel; +Cc: gaoliming, lichao, 钱东彦, michael.d.kinney

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-01-20 10:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-17  8:42 [edk2-devel] Problems with modifying variables after S4 recovery 张辰

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox