Ticket #8379 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

secure-boot no longer freezes the dcon.

Reported by: cscott Owned by: mstone
Priority: normal Milestone: 8.2.0 (was Update.2)
Component: ofw - open firmware Version: Development build as of this date
Keywords: blocks:8.2.0 Cc: mstone, dsd
Action Needed: test in release Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Testing q2e15 with signed 713, although you should be able to duplicate with any signed build:

The secure-boot word does not seem to be freezing the dcon, resulting in no pretty boot (we see linux clear the screen and the "bird" show up, messages scroll, etc).

Using a dev key and typing 'freeze boot' at the ofw prompt correctly invokes pretty boot, so the fault seems to lie in the secure-boot word.

Change History

Changed 5 years ago by cscott

  • cc mstone, dsd added

Changed 5 years ago by wmb@…

  • status changed from new to closed
  • resolution set to fixed

Fixed by svn 928. The problem was that the invocation of "dcon-freeze" had been moved to a slightly earlier point in the secure-startup sequence, so the that "dcon-unfreeze" that makes the first progress dot visible was undoing it.

The solution is for that progress dot code to check the current frozenness state and restore it.

Changed 5 years ago by cscott

In q2e17, which is in joyride and is being added to 8.1.3.

Changed 5 years ago by cscott

  • status changed from closed to reopened
  • next_action changed from never set to approve for release
  • resolution deleted

Approval request for 8.2.

Changed 5 years ago by cscott

  • owner changed from wmb@… to mstone
  • status changed from reopened to new

Changed 5 years ago by mstone

  • next_action changed from approve for release to add to release

Approved, and thanks for the prompt fix. Why were previous firmwares not tested in secure mode earlier as part of their release process?

Changed 5 years ago by mstone

  • keywords blocks:8.2.0 added

Changed 5 years ago by cscott

This is the first time (apparently) we used q2eXX to boot a signed build. Although perhaps we should have seen this in 711? I don't know if the bug was introduced before q2e12 or after.

Changed 5 years ago by cscott

  • next_action changed from add to release to test in release

Checked into repo; should be in 760 and later.

Changed 5 years ago by cscott

  • status changed from new to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.