Bug 177041 - When browsing Google Map's Satellite view in Chrome or Firefox the screen freezes and goes black, occasionally control is returned to user
Summary: When browsing Google Map's Satellite view in Chrome or Firefox the screen fr...
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: Alpha Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-07 23:05 UTC by Kyle Gottfried
Modified: 2017-01-19 04:31 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.4.0-38-generic #57-Ubuntu
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg after the error occured, dmesg after a similiar error occured browing a WebGL website, dpkl -l listing (105.05 KB, application/gzip)
2016-10-07 23:05 UTC, Kyle Gottfried
Details

Description Kyle Gottfried 2016-10-07 23:05:55 UTC
Created attachment 241161 [details]
dmesg after the error occured, dmesg after a similiar error occured browing a WebGL website, dpkl -l listing

When viewing the satellite view in Google Maps with Google Chrome or Firefox the screen will become unresponsive and then go black. This occurs on other websites too but this is the most reproducible. Occasionally the screen returns and control is given back to the user, but often only the mouse works and desktop elements will not move around the screen when clicked and dragged.

I have a Radeon 390x graphics card, a MSI Z97 Gaming 5 Motherboard and am running Kubuntu 16.04.1 LTS. This is a dual boot device with Windows 10 and have not seen any hardware issues in the Event Viewer. I filed this log here as the file that appeared in the dmesg log is part of the linux project "/build/linux-R0TiM8/linux-4.4.0/drivers/gpu/drm/radeon/radeon_object.c".
Comment 1 Michel Dänzer 2016-10-12 09:12:33 UTC
Can you try a newer kernel, ideally 4.8.y? I seem to remember running into this before, but no longer with current kernels. Unfortunately, I don't remember specifically how this was fixed.
Comment 2 Kyle Gottfried 2016-10-22 15:49:37 UTC
This is resolved with upgrading to Ubuntu 16.10 (uses kernel 4.8), will follow a backport request with Ubuntu. If anyone knows the commit that resolves this issue please post.

Note You need to log in before you can comment on or make changes to this bug.