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

Issue 788712 link

Starred by 1 user
Status: WontFix
Owner:
█ youcheng@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
chromeos-factory-eng@google.com
saintlou@google.com
josa...@google.com
puneetster@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

factory: cannot cutoff battery due to lack of libfmap

Project Member Reported by youcheng@chromium.org, Nov 27 2017 
Test Image: 9998.8.0
Factory Toolkit: a509ad13c341a8cd82e01014420a1844c8735816

Steps to reproduce:
Run "gooftool wipe_in_place".

Logs:
See the attachment (stdout/stderr from cutoff.sh).

+ crossystem battery_cutoff_request=1
/usr/sbin/mosys: error while loading shared libraries: libfmap.so.0: cannot open shared object file: No such file or directory
waitpid() or mosys error
Parameter battery_cutoff_request is read-only

The TmpChroot created in "py/gooftool/wipe.py" doesn't include /usr/lib, which contains libfmap.so.0, which seems to be used directly by mosys and indirectly by crossystem.
cutoff.out
454 bytes Download
cutoff.err
6.6 KB Download

Comment 1 by youcheng@chromium.org, Nov 28 2017

Status: WontFix (was: Assigned)
wipe.py does check the dependency of mosys by lddtree.
The reason I got this issue is that I replaced mosys with a wrapping shell script for brand code.
We should either use a proper mosys executable or add the required libraries into wipe.py.
►

Sign in to add a comment