Lingzhu,
I have another idea after reading you comment.
> If the firmware is broken, the variable interfaces probably are also broken
> and can't be used to erase variable.
I see, you are concerned that a set_variable service may not work correctly.
If so, the set_variable service should be disabled in addition to get_next_variable service.
On the other hands, if Linux can boot up, a get_variable service probably works.
Therefore, efivars should be initialized by enabling just get_variable service.
> Users need to reset nvram to a known clean state, but often the hardware doesn't provide such
> facility.
What we can do is to notify that the firmware/hardware is broken with printk.
Seiji
��.n��������+%������w��{.n�����{����* jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
