#11089 HIGH 1.75-fi: XO-1.75 B1 brick due to efface-md failure to flash-open (after RTC power fail or sufficient elapsed time)
Zarro Boogs per Child
bugtracker at laptop.org
Tue Aug 16 00:51:37 EDT 2011
#11089: XO-1.75 B1 brick due to efface-md failure to flash-open (after RTC power
fail or sufficient elapsed time)
-------------------------------------------+--------------------------------
Reporter: Quozl | Owner: greenfeld
Type: defect | Status: closed
Priority: high | Milestone: 1.75-firmware
Component: ofw - open firmware | Version: 1.75-B1
Resolution: fixed | Keywords:
Next_action: no action | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-------------------------------------------+--------------------------------
Changes (by Quozl):
* status: new => closed
* next_action: test in release => no action
* resolution: => fixed
Comment:
Yes, the tag was not documented. I've added an entry to the table now.
I'm not sure the documentation is needed, as I think it is a tag that
should not escape the manufacturing process. There are other tags that
are deleted before shipping.
The tag is not required for proper operation. There will have been no
hint about refusing to boot, since the root cause was a defect in
OpenFirmware.
Yes, during the first boot that occurs at least ten days after the value
in the md tag, OpenFirmware will change it. The code that does that is
between lines 1293 and 1302, see
[http://tracker.coreboot.org/trac/openfirmware/browser/cpu/x86/pc/olpc/security.fth#L1302
source].
Yes, it is a bit dangerous, but it is necessary to provide a grace period
for the manufacturer to avoid the deployment security system.
I'm satisfied with the testing so far, so I'm closing this ticket.
--
Ticket URL: <http://dev.laptop.org/ticket/11089#comment:9>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list