#12564 closed defect (fixed)

[CL4] Can’t boot machine after run “memetest” in OFW.

Reported by: tomyin Owned by: Quozl
Priority: low Milestone: 4-firmware
Component: ofw - open firmware Version: not specified
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: no action
Verified: no

Description (last modified by Quozl)

OS: 31030o4
OFW: Q7B16
EC: 0.3.12

Procedure:

  • Input “memtest” in OFW.
  • Press esc key to stop “memtest” after it run several cycle.
  • Input “boot” to boot machine. It shows “Scan for: OLPCOFW failed”.

Attachments (1)

boot failed.jpg (917.5 KB) - added by tomyin 22 months ago.
boot failed

Download all attachments as: .zip

Change History (3)

Changed 22 months ago by tomyin

boot failed

comment:1 Changed 22 months ago by Quozl

  • Action Needed changed from never set to add to release
  • Component changed from not assigned to ofw - open firmware
  • Description modified (diff)
  • Milestone changed from Not Triaged to 4-firmware
  • Owner set to Quozl
  • Status changed from new to assigned

Thanks. Reformatted ticket description to meet trac coventions, improving readability.

Reproduced symptom.

Diagnosis: this is due to diag-switch? being left set after memtest is stopped. When diag-switch? is set, the default boot is via network. The default network name is OLPCOFW.

Fixed in svn 3564 by saving and restoring the value.

Test build: http://dev.laptop.org/~quozl/q7b16jc.rom

Test case:

  • type memtest, press enter,
  • press enter once more so that only one cycle of test is run,
  • once the test has completed, try to boot, the expected result is to boot into Linux.

Will be in next release.

comment:2 Changed 22 months ago by Quozl

  • Action Needed changed from add to release to no action
  • Resolution set to fixed
  • Status changed from assigned to closed

Is in Q7B17.

Note: See TracTickets for help on using tickets.