<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>6306</bug_id>
          
          <creation_ts>2014-05-09 20:56:00 +0000</creation_ts>
          <short_desc>Minnowboard UEFI hangs for &quot;grub reboot&quot; and UEFI Shell &quot;bcfg boot mv 01 04&quot;</short_desc>
          <delta_ts>2015-01-26 22:27:36 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>12</classification_id>
          <classification>Hardware Platforms</classification>
          <product>MinnowBoard MAX Firmware</product>
          <component>minnowboard-uefi-firmware</component>
          <version>unspecified</version>
          <rep_platform>MinnowBoard</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Bill Mills">wmills</reporter>
          <assigned_to name="chao zhang">chao.b.zhang</assigned_to>
          <cc>danders</cc>
    
    <cc>scott.a.garman</cc>
    
    <cc>sjolley.yp.pm</cc>
    
    <cc>warthog9</cc>
    
    <cc>wmills</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>43227</commentid>
    <comment_count>0</comment_count>
    <who name="Bill Mills">wmills</who>
    <bug_when>2014-05-09 20:56:00 +0000</bug_when>
    <thetext>The commands in the Summary cause the HDMI to go to colorful snow, the board locks up, and the reset button does not work.

I am not sure but I thought the chip was getting hot.
I did not leave it in that state for very long.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43398</commentid>
    <comment_count>1</comment_count>
    <who name="Bill Mills">wmills</who>
    <bug_when>2014-05-17 10:33:43 +0000</bug_when>
    <thetext>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 &quot;PC&quot; 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&apos;t work.

However, the UEFI Shell command &quot;reset&quot; works fine.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43423</commentid>
    <comment_count>2</comment_count>
    <who name="Bill Mills">wmills</who>
    <bug_when>2014-05-20 13:43:40 +0000</bug_when>
    <thetext>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 &quot;save&quot; 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 -&gt; new
00 -&gt; 01
01 -&gt; 02
02 -&gt; 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 &quot;reboot&quot; command part of this bug report.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43462</commentid>
    <comment_count>3</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2014-05-21 19:06:44 +0000</bug_when>
    <thetext>Chao, any thoughts on this?

David Anders, are we possibly hitting a hardware issue related to reset?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43465</commentid>
    <comment_count>4</comment_count>
    <who name="Bill Mills">wmills</who>
    <bug_when>2014-05-21 19:27:06 +0000</bug_when>
    <thetext>WRT HW Bug:  

I meant to document that the UEFI Shell command to reboot (&quot;reset&quot; ??) *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&apos;s Gnome menus.  I don&apos;t remember if I was trying shutdown or reboot.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43482</commentid>
    <comment_count>5</comment_count>
    <who name="chao zhang">chao.b.zhang</who>
    <bug_when>2014-05-22 02:18:34 +0000</bug_when>
    <thetext>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?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>48312</commentid>
    <comment_count>6</comment_count>
    <who name="John &apos;Warthog9&apos; Hawley">warthog9</who>
    <bug_when>2015-01-26 22:27:36 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>