uefirttime - Avoid using TimeZone 2047
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Firmware Test Suite |
Fix Released
|
Undecided
|
Ivan Hu |
Bug Description
FWTS uefirttime test tries to change the TimeZone to 0 (UTC) if it is not already 0. Otherwise, it tries to change it to 2047 (local time): https:/
Some systems do not support the 2047 local time, and enforces time to always be in UTC. This can for instance be either an enforced BIOS behavior, or configurable via a user BIOS Setup option.
an the FWTS test avoid using this potentially problematic TZ value (with the special "local time" meaning), and instead use another UTC value (e.g. 01 for UTC+1) to confirm the TimeZone change functionality? This is similar to what SCT does in pre-boot testing of the same Get/SetTime interface: https:/
If there is a need to test "local time" support, maybe that can be a separate test, since not all platforms support local time.
Changed in fwts: | |
assignee: | nobody → Ivan Hu (ivan.hu) |
Changed in fwts: | |
status: | In Progress → Fix Committed |
Changed in fwts: | |
status: | Fix Committed → Fix Released |
@Samer
Thanks for the info.
Could you provide the fwts result logs for those that haven't the "local time" support?
So that I could figure out how's the uefirttime test going.