Bug 94109 - Sometimes, when taking Chrome out of full-screen mode, the whole system freezes and needs a cold reboot
Summary: Sometimes, when taking Chrome out of full-screen mode, the whole system freez...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: highest critical
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-12 09:28 UTC by Behrang Saeedzadeh
Modified: 2016-07-21 14:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log file and anything under /var/logs that contains i965 (6.74 KB, text/plain)
2016-02-12 09:28 UTC, Behrang Saeedzadeh 		Details
When the screen freezes with Chrome's "invisible window" marked with markers (10.10 MB, image/png)
2016-02-15 13:24 UTC, Behrang Saeedzadeh 		Details
Contains two log files (chrome_debug-freeze.log and chrome_debug-no-freeze.log) (50.18 KB, application/gzip)
2016-02-15 14:11 UTC, Behrang Saeedzadeh 		Details
View All

Description Behrang Saeedzadeh 2016-02-12 09:28:10 UTC 
Created attachment 121703 [details]
Xorg.0.log file and anything under /var/logs that contains i965

Machine specs:

uname -m: x86_64
uname -r: 4.2.0-27-generic
Distro: Ubuntu 15.10
Machine: Lenovo ThinkCentre M900 with Skylake Core i7 6700
Chipset: Q170
Display connector: DP 1.2

---

I added "drm.debug=0x1e log_buf_len=1M" to Grub's config (/etc/default/grub):

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.debug=0x1e log_buf_len=1M"
GRUB_CMDLINE_LINUX="drm.debug=0x1e log_buf_len=1M"

but running "cat /sys/class/drm/card0/error" showed no errors:

   no error state collected

---

 
Reproducability: Cannot be reproduced all the time, but I've seen quite a few similar bug reports associated with Intel GPUs:

* http://ubuntuforums.org/showthread.php?t=2113179
* http://unix.stackexchange.com/questions/91912/chrome-freezes-ubuntu-13-04

However if I use Chrome as my main browser, it at least happens one per day, if not two or three times per day.

---

Installed libva libraries:

* libva-drm1/unknown,now 1.6.1-1 amd64 [installed]
* libva-egl1/unknown,now 1.6.1-1 amd64 [installed]
* libva-glx1/unknown,now 1.6.1-1 amd64 [installed]
* libva-tpi1/unknown,now 1.6.1-1 amd64 [installed]
* libva-wayland1/unknown,now 1.6.1-1 amd64 [installed]
* libva-x11-1/unknown,now 1.6.1-1 amd64 [installed,automatic]
* libva1/unknown,now 1.6.1-1 amd64 [installed]
* libvariable-magic-perl/wily,now 0.58-1 amd64 [installed]

Couldn't find any vaapi packages, but here are some potentially related packages:

* i965-va-driver/unknown,now 1.6.1-1 amd64 [installed]
* java-common/wily,now 0.52 all [installed,automatic]
* libva-drm1/unknown,now 1.6.1-1 amd64 [installed]
* libva-egl1/unknown,now 1.6.1-1 amd64 [installed]
* libva-glx1/unknown,now 1.6.1-1 amd64 [installed]
* libva-tpi1/unknown,now 1.6.1-1 amd64 [installed]
* libva-wayland1/unknown,now 1.6.1-1 amd64 [installed]
* libva-x11-1/unknown,now 1.6.1-1 amd64 [installed,automatic]
* libvdpau-va-gl1/wily,now 0.3.4-3 amd64 [installed]
* va-driver-all/unknown,now 1.6.1-1 amd64 [installed]
* vdpau-va-driver/wily,now 0.7.4-4 amd64 [installed,automatic]

Any package with intel in the package name:

* intel-gpu-tools/unknown,now 1.12-1 amd64 [installed]
* intel-linux-graphics-installer/unknown,now 1.2.1-0intel2 amd64 [installed]
* intel-microcode/wily,now 3.20150121.1 amd64 [installed]
* libdrm-intel1/wily,now 2.4.64-1 amd64 [installed,automatic]
* xserver-xorg-video-intel/wily,now 2:2.99.917+git20150808-0ubuntu4 amd64 [installed,automatic]

Mesa packages:

* libegl1-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libgl1-mesa-dri/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libgl1-mesa-glx/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libglapi-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libgles1-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libgles2-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libglu1-mesa/wily,now 9.0.0-2 amd64 [installed,automatic]
* libwayland-egl1-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]


libdrm packages:

* libdrm-amdgpu1/wily,now 2.4.64-1 amd64 [installed,automatic]
* libdrm-intel1/wily,now 2.4.64-1 amd64 [installed,automatic]
* libdrm-nouveau2/wily,now 2.4.64-1 amd64 [installed,automatic]
* libdrm-radeon1/wily,now 2.4.64-1 amd64 [installed,automatic]
* libdrm2/wily,now 2.4.64-1 amd64 [installed,automatic]



If anything else is needed, please let me know. 
If need be you can also remotely login to my machine.
Comment 1 Behrang Saeedzadeh 2016-02-12 10:24:15 UTC 
Here's a video that shows the problem: https://www.youtube.com/watch?v=74sB1-8tAdA
Comment 2 haihao 2016-02-15 02:38:46 UTC 
Can you run your browser without libva libraries ? I don't think it is a libva related issue if you can't find any error in /sys/class/drm/card0/error.
Comment 3 Behrang Saeedzadeh 2016-02-15 02:52:01 UTC 
Hi @haiho,

Sorry, I am very new to the Linux graphics stack.

Do you by any chance know how can I run Chrome without libva libraries? I have just recently learned a tiny bit about Linux graphics and it is very confusing to me: mesa, gallium, xv, gl, va, drm, dri (?), etc. etc.

Should I just temporarily uninstall the libva libraries? Or does Chrome accept a commandline flag to disable i t?

Cheers,
Behrang
Comment 4 haihao 2016-02-15 04:30:39 UTC 
Please uninstall the libva libraries fist then run Chrome.
Comment 5 Behrang Saeedzadeh 2016-02-15 13:22:25 UTC 
You were right. It was not due to the libva libaries.

Last night I reinstalled my system on a new SSD that I had got and it only had this libva:

libva1:amd64 1.6.0-1

Removing that also removed:

libavcodec-ffmpeg56:amd64 7:2.7.6-0ubuntu0.15.10.1

However I could reproduce the issue by just opening and closing Chrome multiple times. Last time I opened it, it froze the whole system with the exception of the mouse:

Here's a photo I took from the monitor when this happened:

https://dl.dropboxusercontent.com/u/34024/Ubuntu%2015.10%20Chrome%20Crash/Chrome%20Crash%20under%20Ubuntu%2015.10%20-%20with%20markers.png

Chrome pops up an invisible rectangle for a few seconds and then the borders of the rectangle remains on the screen but other than that everything freezes.

Could you please let me know what should I be looking at next?
Comment 6 Behrang Saeedzadeh 2016-02-15 13:24:05 UTC 
Created attachment 121763 [details]
When the screen freezes with Chrome's "invisible window" marked with markers
Comment 7 Behrang Saeedzadeh 2016-02-15 14:11:52 UTC 
Created attachment 121764 [details]
Contains two log files (chrome_debug-freeze.log and chrome_debug-no-freeze.log)

I ran Chrome with the following logging/debugging flags to see if I can see anything particularly suspicious:

--enable-logging 
--v=1 
--enable-gpu-service-tracing 
--enable-gpu-client-tracing 
--log-gpu-control-list-decisions 
--enable-extension-activity-logging 
--enable-gpu-command-logging

I have attached two files, one called chrome_debug-freeze.log and one called chrome_debug-no-freeze.log.

The first one contains logging information gathered when Chrome froze the whole system as soon as I opened it.

The second one contains logging information for a non freezing Chrome session (having said that, sometimes Chrome starts properly and then crashes while watching a video, etc.)

Both logs contain heaps of ERRORs. However here's a grep for ERROR on the chrome_debug-freeze.log file:

[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketSize
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketData
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetToken
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketSize
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketData
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetToken
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: kTraceBeginCHROMIUM
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [.CompositorWorker-0x2747f4e11580]cmd: SetBucketSize
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [.CompositorWorker-0x2747f4e11580]cmd: SetBucketSize

I will share this bug report with the Chrome team as well. Most of the errors seem to be related to OpenGL ES 2.0, but I am not sure if Chrome is using this (https://code.google.com/archive/p/gles2-bc/) version of gles2 or another implementation.
Comment 8 Behrang Saeedzadeh 2016-02-15 14:34:49 UTC 
List of potentially related packages:

* libegl1-mesa/wily,now 11.0.2-1ubuntu4
* libgl1-mesa-dri/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libgl1-mesa-glx/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libglapi-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libglew1.10/wily,now 1.10.0-3 amd64 [installed,automatic]
* libglewmx1.10/wily,now 1.10.0-3 amd64 [installed,automatic]
* libglib2.0-0/wily,now 2.46.1-1 amd64 [installed,automatic]
* libglib2.0-bin/wily,now 2.46.1-1 amd64 [installed,automatic]
* libglib2.0-data/wily,now 2.46.1-1 all [installed,automatic]
* libglibmm-2.4-1v5/wily,now 2.45.41.is.2.44.0-0ubuntu2 amd64 [installed,automatic]
* libglu1-mesa/wily,now 9.0.0-2 amd64 [installed,automatic]
* libcogl-common/wily,now 1.20.0-2 all [installed,automatic]
* libcogl-pango20/wily,now 1.20.0-2 amd64 [installed,automatic]
* libcogl-path20/wily,now 1.20.0-2 amd64 [installed,automatic]
* libcogl20/wily,now 1.20.0-2 amd64 [installed,automatic]

The bug reported in Chromium: https://code.google.com/p/chromium/issues/detail?id=586926
Comment 9 haihao 2016-02-16 00:55:12 UTC 
So it isn't a libva issue, I will closed it as 'notourbug'. Please file a new bug to ask helps from graphics guys if you think your issue is related to OpenGL ES.
Comment 10 Behrang Saeedzadeh 2016-02-16 01:02:50 UTC 
Isn't it possible to change the product field?
Comment 11 haihao 2016-02-16 04:50:46 UTC 
Yes, you can change the product field. But I was thinking the first comments might confuse others.
Comment 12 Behrang Saeedzadeh 2016-02-16 04:54:55 UTC 
Which product should I use? Can't see anything OpenGL related.
Comment 13 haihao 2016-02-16 06:41:16 UTC 
According to report's new comment, this isn't a libva issue and might be related to OpenGL.
Comment 14 Behrang Saeedzadeh 2016-02-16 07:02:37 UTC 
One way that I could reproduce this issue was by opening and closing Chrome multiple times in a row and suddenly my whole system freezes.

Here are some Chrome specific command-line flags that might come in handy when trying to find the issue:

--blacklist-accelerated-compositing 
--blacklist-webgl 
--disable-accelerated-2d-canvas 
--disable-accelerated-compositing 
--disable-accelerated-layers 
--disable-accelerated-video 
--disable-accelerated-video-decode 
--disable-gpu 
--disable-gpu-compositing 
--disable-gpu-driver-bug-workarounds 
--disable-gpu-process-prelaunch 
--disable-gpu-program-cache 
--disable-gpu-rasterization 
--disable-gpu-shader-disk-cache 
--disable-gpu-vsync 
--disable-gpu-watchdog 
--disable-map-image 
--disable-threaded-compositing 
--log-gpu-control-list-decisions 
--disable-accelerated-fixed-root-background 
--disable-accelerated-overflow-scroll 
--disable-pinch 
--disable-universal-accelerated-overflow-scroll 
--disable-webrtc-hw-decoding 
--disable-webrtc-hw-encoding 
--enable-deferred-filters 

I have also reported the bug to Chromium's bug tracker and some communication with them might help fix this issue sooner rather than later:

https://code.google.com/p/chromium/issues/detail?id=586926

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.