fizz: external monitor (LG USB-C) does not come back up after reboot. |
||||
Issue descriptionChrome Version: (copy from chrome://version) OS: ToT What steps will reproduce the problem? (1) get an auto-update on normal mode fizz device and reboot via the UI (2) wait for machine to reboot and re-login What is the expected result? both displays connect (1 x hdmi, 1 x USB-C) What happens instead? only the HDMI screen comes back. This has happened several times for me and I believe consistently after a update-induced reboot. Here's one feedback report, https://listnr.corp.google.com/report/85583342437 filing the freshest one now w/ pointer to this bug.
,
Sep 21
More Feedback logs https://listnr.corp.google.com/report/85674253078 "2nd external display (LG USB-C) did not come up after auto-update reboot. feedback for crbug.com/887731 marcheu@ tbroch@"
,
Sep 25
In modetest the DP monitor (usb-c) is reported as disconnected. So it's a USB-C side issue. Todd, can you take a look?
,
Sep 25
I'll take a look. Which LG monitor are we talking about?
,
Sep 25
LG 27UD88
,
Sep 27
I'm not able to reproduce it. I tried to emulate the update recorded in https://listnr.corp.google.com/report/85674253078: - AU from 10139.117.0 to 10139.141.0 - normal mode - Both SPI ROMs are write protected After reboot, both monitors (LG 27UD88 and HP Z27n) showed pictures normally. update_engine says: Starting firmware updater (//usr/sbin/chromeos-firmwareupdate --mode=autoupdate) Command: //usr/sbin/chromeos-firmwareupdate --mode=autoupdate Model is sion Starting Google_Fizz firmware updater v4 (autoupdate)... - Updater package: [RO:Google_Fizz.10139.137.0 RW:Google_Fizz.10139.141.0 / EC:fizz_v1.1.7855-3f7093143] - Current system: [RO:Google_Fizz.10139.117.0 , ACT:Google_Fizz.10139.141.0 / EC:fizz_v1.1.7881-6c20727c6] - Write protection: Hardware: ON, Software: Main=ON - import root_key from keyset/rootkey.sion: success successfully saved new image to: models/fizz_137ro_141rw/bios.bin Firmware keys changed to set [sion]. * invoke: flashrom -p host -r _current/models/fizz_137ro_141rw/bios.bin Firmware update available: Google_Fizz.10139.141.0. * invoke: flashrom -p host --fast-verify -w models/fizz_137ro_141rw/bios.bin -i RW_SECTION_B On reboot EC update may occur. Firmware update (autoupdate) completed. Finished after 22 seconds. Firmware update completed. Starting command: //usr/share/cros/cr50-set-board-id.sh unknown Command: //usr/share/cros/cr50-set-board-id.sh unknown ERROR: Flag has been set differently. ignored: cr50-set-board-id failure (3). Finished after 0 seconds. Failed Command: //usr/share/cros/cr50-set-board-id.sh unknown - Exit Code 3 Starting command: //usr/share/cros/cr50-update.sh / Command: //usr/share/cros/cr50-update.sh / Finished after 11 seconds. cr50 setup complete. ChromeosChrootPostinst complete Syncing filesystem at end of postinst... I don't know if cr50 update (or its error for setting board-id) is related . I ran cr50-set-board-id.sh and cr50-update.sh as recorded but saw no reproduction.
,
Oct 2
Another update for me and another occurrence https://listnr.corp.google.com/report/85697640120 simply rebooting fixed the problem.
,
Nov 20
This still fails on every AU for me I believe.
,
Dec 12
+abodeti@ to repro this issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by tbroch@chromium.org
, Sep 20