Issue metadata
Sign in to add a comment
|
Black screen on samus post migration to 61 |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome 61.0.3163.51 (Official Build) beta (64-bit) Revision 0 Platform 9765.31.0 (Official Build) beta-channel samus Firmware Version Google_Samus.6300.174.0 ARC 4279895 JavaScript V8 6.1.534.22 Flash 26.0.0.137 Filed feedback at https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:abodenha&lReport=71498976665 Was on beta channel on 61. Got prompted to restart to update. Restarted and came back to new start screen which seemed to work fine. Signed in and got taken through the OS update flow (ext4 migration I assume). Device restarted on its own when that finished (I’m assuming it finished. I left it unattended.) Signed in. Start screen was unresponsive for approx 1s then both of my displays went black. After a few seconds a few lines appeared on the primary display. They seemed to match bounding boxes of where I’d expect scrollbars to be. Mouse worked fine. I was able to grab the window edges near the boxes on the screen and move window edges around but redraw seemed incomplete. Disconnected external display. Everything that had been on external moved to internal, but still hosed. Reconnected display and everything moved back to external where I’d expect it to be, but still hosed. Restarting machine resolved the issue.
,
Aug 24 2017
,
Aug 30 2017
abodeti@ does this still repro on latest build? can you please confirm?
,
Sep 1 2017
Just failed for me again after a restart. Might be something about the USB-C doc I'm using. I don't think this has anything to do with startscreen removing that. If no one else is able to repro this we can probably remove releaseblock. oshima@ can you take a quick look at the log in the feedback report and see if anything stands out?
,
Sep 5 2017
sg! Thanks for confirming. removing RBS.
,
Sep 6 2017
,
Sep 6 2017
This may indeed ext4 migration related. skuhne@ had the same issue and looks like it has some issue in reading system settings. [1393:1507:0906/103101.033273:WARNING:name_value_pairs_parser.cc(55)] Key block_devmode already has value (error), ignoring new value: 0 [1393:1507:0906/103101.033319:WARNING:name_value_pairs_parser.cc(55)] Key rlz_brand_code already has value ZZAD, ignoring new value: ZZAD [1393:1507:0906/103101.035089:WARNING:name_value_pairs_parser.cc(55)] Key gbind_attribute already has value =CisKIDRx2ASs2meGitGH--f3DT2SHEF5zja2aQ37y_OsYVUaEAAaBXNhbXVzELaixpcH, ignoring new value: =CisKIDRx2ASs2meGitGH--f3DT2SHEF5zja2aQ37y_OsYVUaEAAaBXNhbXVzELaixpcH [1393:1507:0906/103101.035112:WARNING:name_value_pairs_parser.cc(55)] Key ubind_attribute already has value =CisKIJsDfg5Owxn9YMPRU0TWfsyGCtNFKRmt59BsvO-de3jiEAEaBXNhbXVzEMDysnI=, ignoring new value: =CisKIJsDfg5Owxn9YMPRU0TWfsyGCtNFKRmt59BsvO-de3jiEAEaBXNhbXVzEMDysnI= [1393:1507:0906/103101.035154:WARNING:name_value_pairs_parser.cc(55)] Key initial_locale already has value en-US, ignoring new value: en-US [1393:1507:0906/103101.035165:WARNING:name_value_pairs_parser.cc(55)] Key initial_timezone already has value America/Los_Angeles, ignoring new value: America/Los_Angeles [1393:1507:0906/103101.035174:WARNING:name_value_pairs_parser.cc(55)] Key keyboard_layout already has value xkb:us::eng, ignoring new value: xkb:us::eng [1393:1507:0906/103101.035182:WARNING:name_value_pairs_parser.cc(55)] Key region already has value us, ignoring new value: us [1393:1507:0906/103101.035190:WARNING:name_value_pairs_parser.cc(55)] Key rlz_brand_code already has value ZZAD, ignoring new value: ZZAD [1393:1507:0906/103101.035198:WARNING:name_value_pairs_parser.cc(55)] Key ActivateDate already has value 2014-49, ignoring new value: 2014-49 [1393:1507:0906/103101.035205:WARNING:name_value_pairs_parser.cc(55)] Key check_enrollment already has value 1, ignoring new value: 1 [1393:1507:0906/103101.035212:WARNING:name_value_pairs_parser.cc(55)] Key block_devmode already has value (error), ignoring new value: 0 hashimoto-san, can you take a look? abodenha@, the log doesn't seem to contain /var/log/ui. Is this regression?
,
Sep 6 2017
,
Sep 7 2017
IIUC the log pasted in comment #7 is generated by chromeos/system/statistics_provider.cc, which parses output of /usr/bin/crossystem command. So I think the log has nothing to do with encryption migration. Also, I can find similar lines in the chrome_system_log section of chrome://system on my chell which isn't affected by this problem. Seems samus has a few other USB-C hub related screen issues ( issue 758342 , issue 750379 ). Probably, this bug is also one of them, as abodenha@ has said in comment #4? > skuhne@ had the same issue Was he using any USB-C dock or external monitors?
,
Sep 7 2017
> Was he using any USB-C dock or external monitors? No it was plain samus + internal display. Both cases happened after update, and rebooting a few times fixed it. Unfortunately, we don't have dmesg log because these feedbacks are filed after restart. (I got logs from skuhne@'s device) There are multiple reports about the similar issue after update. Let me find more info.
,
Sep 7 2017
Not sure it is related to here. In this bug 757641 , I found some graphics issue staring from 9738.0.0 / 61.0.3154.0. Maybe some kernel changes caused this. https://bugs.chromium.org/p/chromium/issues/detail?id=757641#c25
,
Sep 26 2017
,
Oct 4 2017
I have/had the same issue on the Pixel 2. Device is enterprise enrolled, but I experienced this issue only with an additional gmail account. Sent feedback after reboot. I removed and re-added the account and did not experience it again since then.
,
Oct 4 2017
No longer convinced this is the same as bug 758820
,
Oct 4 2017
This just happened again on upgrading to 61.0.3163.113. I filed feedback again. At the very least we need to hold 61 stable on samus until this is resolved.
,
Oct 4 2017
Working theory on bug 758820 is that the buffer for passing command line to the zygote is too small (a recurrance of ancient bug 77230 that was never properly fixed) This could be the same root cause, but it's hard to tell.
,
Oct 4 2017
I could repro the 758820 behavior by opening youtube video when I got this. This happened twice after my samus shutdown due to out of battery, and I'm going to reproduce it on my samus + test image.
,
Oct 5 2017
There is a fix in flight to increase the buffer size -> https://chromium-review.googlesource.com/#/c/chromium/src/+/701396/ Adding merge-approval for it
,
Oct 6 2017
I believe this is dup of 758820.
,
Oct 9 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 12 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by abodenha@chromium.org
, Aug 24 20172.9 MB
2.9 MB View Download
3.2 MB
3.2 MB View Download
3.2 MB
3.2 MB View Download
2.5 MB
2.5 MB View Download