New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 612833 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Update beaglebone_servo to R52-8316.0.0

Reported by jrbarnette@chromium.org, May 18 2016

Issue description

We need to update beaglebone_servo in the lab to use
R52-8316.0.0.  We want this principally to pick up
the CLs that switched us to the 4.4 kernel on beaglebone,
notably this one:
    https://chromium-review.googlesource.com/#/c/340033/

We want to do this separately so that we can have a simpler
blamelist, in case there's a problem.  We want to use 8316.0.0
specifically for the same reason.

I've already specifically tested the build to confirm that it's
safe to update to the build, and if necessary, to downgrade back
to the current build.  So, the worst case (beaglebone-shaped bricks
in the lab) has been ruled out.

 
This is on its way to the lab:

$ atest stable_version modify -b beaglebone_servo -i R52-8316.0.0
Stable version for board beaglebone_servo is changed from R52-8281.0.0 to R52-8316.0.0.

Status: Verified (was: Started)
Well, this update was much more eventful than expected, and
in unexpected ways.  See this post mortem:
    https://docs.google.com/document/d/1jkmIvX4xZfZyA4DyHWun-u7Ua1PY4OvV_gCLK1dzkqg/edit

However, at this point, we're running the 4.4 kernel in the
lab, at least for the beablebones that survived...

Sign in to add a comment