Opened 5 years ago

Closed 5 years ago

Last modified 20 months ago

#11745 closed defect (fixed)

os32 doesn't boot w. serial console, on XO-1.75

Reported by: wad Owned by:
Priority: high Milestone:
Component: kernel Version: Development build as of this date
Keywords: Cc: quozl, greenfeld, martin.langhoff
Blocked By: Blocking:
Deployments affected: Action Needed: no action
Verified: no


I've upgrade a couple of XO-1.75 C1 laptops to 11.3.1_xo1.75-32, and have lost the ability to use the serial console. When I enable the serial console, either using the check key or by editing olpc.fth to set serial-enable to true, the kernel crashes on boot. It prints crash info on the display, but nothing is output on the serial port.

This is easily reproducible.

Change History (8)

comment:1 Changed 5 years ago by cjb

  • Cc quozl cerlyn added
  • Component changed from not assigned to kernel

Can someone upload a photo or video of the failing boot kernel log, please?

comment:2 Changed 5 years ago by cjb

  • Cc greenfeld added; cerlyn removed

comment:3 Changed 5 years ago by Quozl

  • Action Needed changed from diagnose to code
  • Milestone changed from Not Triaged to 11.3.1

Can be avoided using "false to use-fdt?" before boot.

Per Chris and discussion on #olpc-devel, this patch matches the symptom and appears to be a fix.

comment:4 Changed 5 years ago by greenfeld

  • Cc martin.langhoff added

This patch likely has to be added to -ramp.

comment:5 Changed 5 years ago by Quozl

  • Action Needed changed from code to add to build


comment:6 Changed 5 years ago by martin.langhoff

  • Action Needed changed from add to build to test in build

comment:7 Changed 5 years ago by greenfeld

  • Action Needed changed from test in build to no action
  • Resolution set to fixed
  • Status changed from new to closed

We can boot with the serial console enabled (in verbose mode) or disabled (default) on a XO-1.75 in 11.3.1 os885.

comment:8 Changed 20 months ago by Quozl

  • Milestone 11.3.1 deleted

Milestone 11.3.1 deleted

Note: See TracTickets for help on using tickets.