| Summary: | Minnowboard UEFI hangs for "grub reboot" and UEFI Shell "bcfg boot mv 01 04" | ||
|---|---|---|---|
| Product: | [Hardware Platforms] MinnowBoard MAX Firmware | Reporter: | Bill Mills <wmills> |
| Component: | minnowboard-uefi-firmware | Assignee: | chao zhang <chao.b.zhang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | danders, scott.a.garman, sjolley.yp.pm, warthog9, wmills |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | MinnowBoard | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Bill Mills
2014-05-09 20:56:00 UTC
Additional information:
I built upstream tianocore OVMF target for QEMU.
In QEMU I tried:
bcfg mv 02 03
It did not do what I expected there either.
The command just reset the virtual "PC" and the firmware just started over
So I think the minnow specific part of that is probibly related to
the grub reboot command not working.
It seems that some methods of the Firmware self reset don't work.
However, the UEFI Shell command "reset" works fine.
BTW: My use of bcfg below was incorrect. (The bug is still valid) For anyone that finds this bug, here is how the bcfg boot mv command works. I was trying to "save" a boot entry into a new entry at the end. If only 00, 01, 02, 03 were defined I was trying to save 01 to a new 04 entry so I could then move 02 to 01. The above is a misconception of how bcfg boot mv works. What it _really_ does is a reorder. bcfg boot mv 02 00 will: old -> new 00 -> 01 01 -> 02 02 -> 01 So specifying a new entry is not valid. Evidently this cause tianocore to reboot the system. In other platforms this reboot works, on Minnow it goes into a funny state. I would concentrate on the grub "reboot" command part of this bug report. Chao, any thoughts on this? David Anders, are we possibly hitting a hardware issue related to reset? WRT HW Bug:
I meant to document that the UEFI Shell command to reboot ("reset" ??) *does* work.
[ I am not near a board right now.]
So there is at least one reset mechanisum that does work and at least one that does not.
BTW: I saw the same bug using the Angstrom image's Gnome menus. I don't remember if I was trying shutdown or reboot.
For bcfg usage, please reference uefi shell spec. For the reset issue, which switch do you use in shell? -s - Performs a shutdown -w - Performs a warm boot -c - Performs a cold boot Do you know how grub calls uefi rt service ResetSystem? MinnowBoard v1 has reached new feature EOL, FW development is done as are new hardware features. If you feel EXCEEDINGLY strongly about an issue please re-open it for discussion but be aware that we are recommending individuals migrate to the MAX platform. |