PSA: 2GB boards converting back to 32 bit

[David James]

Hi folks,

I've just pushed CLs to convert all boards with 2GB of RAM back to 32bit. This impacts x86-alex, x86-mario, x86-zgb, and kiev. This change helps us use less memory.

The next time you sync, please run build_packages, and your old 64-bit build root will be moved out of the way automatically, and a new build root will be created with a 32-bit installation. 32 bit prebuilts are already available, so the conversion should be relatively fast and painless.

If you don't need the old 64-bit buildroot, you can delete it. It will be stored under /build/ with a '64' suffix.

Note: If you update developer images on the device using the devserver, you will need to run stateful_update (/usr/local/bin) after the next update.  You will know you will need to do this if you start getting any "cannot execute binary file" errors. That error indicates you are trying to run a 64-bit executable (from stateful from your previous installation) from a 32-bit kernel. If you update using image_to_live or cros_target_to_live, the stateful partition is already updated as part of the update process.

Let me know if you have problems, thanks!

Cheers,

David

[Mike Frysinger]

On Mon, May 14, 2012 at 5:17 PM, David James <david...@google.com> wrote:
> If you don't need the old 64-bit buildroot, you can delete it. It will be
> stored under /build/ with a '64' suffix.

minor, but it'll have a ".64bit" suffix
-mike

[Nikita Kostylev]

I've synced to latest chromium-os sources and started full rebuild with

./setup_board --board=x86-alex --force

Now both ./setup_board and /build_packages fail with

=== Complete: job linux-headers-3.1 (0m8.0s) ===

Failed cross-armv7a-cros-linux-gnueabi/linux-headers-3.1 (in 0m8.0s). Your build has failed.

Pending 1/1, [Time 0m21.7s Load 3.03 1.28 0.71]

cros_setup_toolchains: Unhandled exception:

Traceback (most recent call last):

  File "/home/nkostylev/trunk/chromite/bin/cros_setup_toolchains", line 77, in <module>

    ret = target()

  File "/home/nkostylev/trunk/chromite/scripts/cros_setup_toolchains.py", line 604, in main

    UpdateToolchains(options.usepkg, options.deleteold, options.hostonly, targets)

  File "/home/nkostylev/trunk/chromite/scripts/cros_setup_toolchains.py", line 568, in UpdateToolchains

    UpdateTargets(targets, usepkg)

  File "/home/nkostylev/trunk/chromite/scripts/cros_setup_toolchains.py", line 465, in UpdateTargets

    cros_build_lib.RunCommand(cmd)

  File "/home/nkostylev/trunk/chromite/lib/cros_build_lib.py", line 418, in RunCommand

    raise RunCommandError(msg, cmd_result)

chromite.lib.cros_build_lib.RunCommandError: Failed command "['/home/nkostylev/trunk/chromite/bin/parallel_emerge', '--oneshot', '--update', '--getbinpkg', '--usepkgonly', '<=cross-armv7a-cros-linux-gnueabi/linux-headers-3.1']", cwd=None, extra env=None

ERROR   : script called:  '--fast' '--usepkg'

ERROR   : Backtrace:  (most recent call is last)

ERROR   :   file update_chroot, line 92, called: die_err_trap 'sudo $(type -p cros_setup_toolchains) ${TOOLCHAIN_FLAGS}' '1'

ERROR   : 

ERROR   : Command failed:

ERROR   :   Command 'sudo $(type -p cros_setup_toolchains) ${TOOLCHAIN_FLAGS}' exited with nonzero code: 1

ERROR   : script called: ./setup_board '--board=x86-alex' '--force'

ERROR   : Backtrace:  (most recent call is last)

ERROR   :   file setup_board, line 365, called: die_err_trap '"${SRC_ROOT}/scripts"/update_chroot ${UPDATE_ARGS}' '1'

ERROR   : 

ERROR   : Command failed:

ERROR   :   Command '"${SRC_ROOT}/scripts"/update_chroot ${UPDATE_ARGS}' exited with nonzero code: 1

ERROR   :   (Note bash sometimes misreports "command not found" as exit code 1 instead of 127)

2012/5/15 David James <david...@google.com>

--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Mike Frysinger]

this is unrelated to David's PSA. please file a bug.
-mike