Periodically video will freeze for no reason at all and no specific time between freezes.

[chris pollock]

What I expect to happen is the video to not freeze every so often.
What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run.

---
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 2095 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6
InstallationDate: Installed on 2014-10-24 (332 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Dell Inc. OptiPlex 780
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-63-generic N/A
 linux-backports-modules-3.13.0-63-generic N/A
 linux-firmware 1.127.15
RfKill:

Tags: trusty
Uname: Linux 3.13.0-63-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0C27VV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.asset.tag: LE0006476
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1497627

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[chris pollock (cpollock)]

An additional note. Based on a bug that I have been supplying information to https://bugs.freedesktop.org/show_bug.cgi?id=75394 because initially there would be an error noted in my syslog "[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle". This error has since stopped being entered into my syslog. The reason that I'm running a non-Ubuntu kernel but instead the most current stable drm-intel kernel from here http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ is that I posted a message about this issue in the Intel-GFX mailing list and was contacted by Chris Wilson, Intel Open Source Technology Centre who had me update to kernel 4.0.0-997-generic. I also updated the driver per his instructions which can be seen in the attached Xorg.0.log. I have also filed a bug report about this previously - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402331 A bug report that I personally filed at freedesktop.org - https://bugs.freedesktop.org/show_bug.cgi?id=91495 can also be referenced for more information. When the freeze happens I'm able to SSH into the desktop from my tablet. I've run some GDB back traces on Gnome-Shell. The one from a freeze in August is attached. The latest freeze was on 10 Sept at 5:03am after a runtime of 16d9h12m. The system was fairly idle at this time as there were no applications running using video such as Firefox or Evolution just background apps.

[penalvch (penalvch)]

chris pollock, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1497627

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[chris pollock (cpollock)]

Well Christopher I've tried that several times even before you asked me to in the post above. Look at the attached screenshot.

[chris pollock (cpollock)]

The description has been updated twice now previously when I ran the command and hit send and just how when I did the same thing. Note this line:

UnreportableReason: The running kernel is not an Ubuntu kernel

Here is where the kernel I'm running came from

http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/

[chris pollock (cpollock)]

As of now I'm booting into the latest 3.13...Ubuntu Kernel. Do I wait until a freeze to run apport-collect or right after I boot?

[chris pollock (cpollock)]

As of 9:43pm 20 Sept I am running - 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

apport information

[chris pollock (cpollock)]

On Mon, 2015-09-21 at 03:09 +0000, Christopher M. Penalver wrote:
> chris pollock, please run it at your earliest convenience only once.
>
Done, all the correct information should now be in the bug report

--
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
07:16:59 up 9:34, 2 users, load average: 0.16, 0.44, 0.32
Ubuntu 14.04.3 LTS, kernel 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14
21:42:59 UTC 2015

[penalvch (penalvch)]

chris pollock, anything change for you with the Vivid enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack ?

[chris pollock (cpollock)]

On Tue, 2015-09-22 at 00:28 +0000, Christopher M. Penalver wrote:
> chris pollock, anything change for you with the Vivid enablement stack
> as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack ?
>
Ok, I'm installing from this command:

sudo apt-get install --install-recommends linux-generic-lts-vivid
xserver-xorg-core-lts-vivid xserver-xorg-lts-vivid
xserver-xorg-video-all-lts-vivid xserver-xorg-input-all-lts-vivid
libwayland-egl1-mesa-lts-vivid

kernel 3.19.0-28 is being installed. After I reboot do you want me to
run the apport-collect ### again?

> ** Description changed:
>
> - This has been going on for over a year. It doesn't matter if I have any
> - applications open such as Evolution or Firefox. It could happen any time
> - during the day when I'm working on the computer or during the night when
> - its' the most idle. Once the video freezes the cursor can still be moved
> - around the desktop however clicking on anything does not work. During
> - this time all background process and cronjobs continue to run.
> + What I expect to happen is the video to not freeze every so often.
> + What happened is that the video froze. This has been going on for over a year. It doesn't matter if I have any applications open such as Evolution or Firefox. It could happen any time during the day when I'm working on the computer or during the night when it's the most idle. Once the video freezes the cursor can still be moved around the desktop however clicking on anything does not work. During this time all background process and cronjobs continue to run.
>
> - Running the command listed below:
> -
> - chris@localhost:~$ cat /proc/version_signature > version.log
> - cat: /proc/version_signature: No such file or directory
> -
> - Of course what I expect to happen is the video to not freeze every so often.
> - What happened is that the video froze.
> -
> - cat release.txt
> - Description: Ubuntu 14.04.3 LTS
> - Release: 14.04
> - ---
> - ApportVersion: 2.14.1-0ubuntu3.13
> - Architecture: amd64
> - CurrentDesktop: GNOME
> - DistroRelease: Ubuntu 14.04
> - InstallationDate: Installed on 2014-10-24 (330 days ago)
> - InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
> - Package: linux (not installed)
> - ProcEnviron:
> - TERM=xterm
> - PATH=(custom, no user)
> - XDG_RUNTIME_DIR=<set>
> - LANG=en_US.UTF-8
> - SHELL=/bin/bash
> - Tags: trusty
> - Uname: Linux 4.0.0-997-generic x86_64
> - UnreportableReason: The running kernel is not an Ubuntu kernel
> - UpgradeStatus: No upgrade log present (probably fresh install)
> - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> - _MarkForUpload: True
> - ---
> - ApportVersion: 2.14.1-0ubuntu3.13
> - Architecture: amd64
> - CurrentDesktop: GNOME
> - DistroRelease: Ubuntu 14.04
> - InstallationDate: Installed on 2014-10-24 (331 days ago)
> - InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
> - Package: linux (not installed)
> - ProcEnviron:
> - TERM=xterm
> - PATH=(custom, no user)
> - XDG_RUNTIME_DIR=<set>
> - LANG=en_US.UTF-8
> - SHELL=/bin/bash
> - Tags: trusty
> - Uname: Linux 4.0.0-997-generic x86_64
> - UnreportableR...

[penalvch (penalvch)]

chris pollock, you do not need to a proper apport-collect more than once to any bug report.

[chris pollock (cpollock)]

I'm curious as to the reason for the report to still be shown as 'incomplete'?

[penalvch (penalvch)]

Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/comments/23 .

[chris pollock (cpollock)]

On Thu, 2015-09-24 at 07:52 +0000, Christopher M. Penalver wrote:
> Please see
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/comments/23
> .
>
I haven't seen a freeze yet however it's only been 2 1/2 days since I
booted into the 3.19...kernel. If/when there is another freeze and since
I can SSH into the desktop from my tablet are there any commands you
wish me to run or any logs you wish captured for the bug report?

--
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
07:28:51 up 2 days, 11:37, 1 user, load average: 0.41, 0.47, 0.32
Ubuntu 14.04.3 LTS, kernel 3.19.0-28-generic #30~14.04.1-Ubuntu SMP Tue
Sep 1 09:32:55 UTC 2015

[chris pollock (cpollock)]

Today, at 15:54:11 the video froze on my system while opening a new tab with Firefox 41.0. At the time of the freeze I was running kernel 3.19.0-28-generic #30~14.04.1-Ubuntu SMP Tue Sep 1 09:32:55 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux and have since updated via an update to kernel 3.19.0-30-generic #33~14.04.1-Ubuntu SMP Tue Sep 22 09:27:00 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux. The cursor would still move but nothing clicked on will open nor can I change to a different window. This came after an uptime of 6d20h6m. I've attached today's syslog which shows that until the time I rebooted after the freeze that background operations were still working. The 2nd boot today was into the new 3.19-30 kernel.

[penalvch (penalvch)]

chris pollock, anything in kern.log during that timeframe (specifically a call trace)? If so, please attach uncompressed, and untarred.

[chris pollock (cpollock)]

On Tue, 2015-09-29 at 00:58 +0000, Christopher M. Penalver wrote:
> chris pollock, anything in kern.log during that timeframe (specifically
> a call trace)? If so, please attach uncompressed, and untarred.
>
I've attached the kern.log from 27/28 September 2015.

--
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
20:22:31 up 3:26, 2 users, load average: 0.33, 0.42, 0.38
Ubuntu 14.04.3 LTS, kernel 3.19.0-30-generic #33~14.04.1-Ubuntu SMP Tue
Sep 22 09:27:00 UTC 2015

[chris pollock (cpollock)]

Today, 30 Sept, 2015 at 13:03:46 video froze again. I was not at home at the time. The uptime when I SSHd into the system was 1d23h10m at 16:06 so you can see it only went about 1d20h before freezing again. As in previous reports the mouse cursor would move and Evolution and Firefox were running. As can be seen by my syslog attachment all background apps continued to function as normal. I've also attached a screenshot this time showing the choppiness of the desktop background after reboot. All other screens look normal, ie..Evo, Firefox and so on.

[chris pollock (cpollock)]

I have discovered this morning that I am able to freeze the video temporarily by going to Evolution and using the scroll wheel to scroll up and down the list of messages the clock will freeze and the screen will flash. This is hard to duplicate however as it only happens so often. I've tried just now to make it happen to no avail. When this is happening I can still switch to a different window however the clock is still frozen. I've noticed that the 'flashing' will sometimes happen when scrolling through posts in Facebook or Twitter using Firefox but the clock doesn't seem to freeze.

[chris pollock (cpollock)]

Today, 2 Oct 2015 at 12:39:07 video froze again. Mouse cursor would move can't switch to any windows. Uptime at freeze was 1d20h12m. I'm attaching:

Gpu-Manager.log (don't know if this means anything)
kern.log
syslog for today until time of reboot
dmesg

[penalvch (penalvch)]

chris pollock, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[chris pollock (cpollock)]

I started out this morning by installing and attempting to boot into the following kernels:

v4.3-rc3-unstable - Boot process would begin but would not complete
v4.3-rc2-unstable - Same as above
v4.3-rc1-unstable - Same as above
v4.2.3-unstable - Boot process completed however I noticed when switching desktop windows a flickering of the video

Currently running kernel 4.2.3-040203-generic #201510030832 SMP Sat Oct 3 12:34:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux at 9:06am 03 Oct 2015.

Will continue to monitor system for video freezes and report if any happen.
Is there anything else you wish me to do?

[chris pollock (cpollock)]

Currently no freeze yet though the uptime is only 19:33:45 up 2 days, 10:27. How long do you wish me to go if I don't see a freeze? Should I drop to the kernel before this one at any time?

[penalvch (penalvch)]

chris pollock, to gather clarity to your Description:
>"What I expect to happen is the video to not freeze every so often."

Could you please provide specifically how often (ex. # times per day)?

To clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/comments/47 does 4.3-rc4 allow you to test to this?

To clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/comments/48 you are still using v4.2.3-unstable?

[chris pollock (cpollock)]

It's usually once a day but not every day. For instance I've gone as many as 10 or 15 days without a freeze but as few as 1 1/2 days which happened just recently. 4.3-rc4 would start the initial boot then all I would see is a black screen. I've gathered the syslog info from that boot attempt and attached it. It must be completing the boot process however since I can SSH into the system from my tablet and run 'sudo reboot'. I could try again and post the dmesg or anything else you'd like me to post. I'm still using 4.2.3-unstable dated 3 Oct 2015 and as I stated above for the almost 2 1/2 days I had it running I had no freezes. Also the video flickering when switching desktop windows has stopped.

[penalvch (penalvch)]

chris pollock, to advise you don't have to attach logs about failed boots given you are using an upstream kernel, which is not supported here in Launchpad.

Despite this, please continue to stress test 4.2.3 for a few more days.

[chris pollock (cpollock)]

Do any of these lines have anything to do with this bug?

[chris pollock (cpollock)]

This morning, 12 Oct 2015 at 9:43am I activated XScreensaver to give more of a stress test to the kernel. System seemed to be running fine with screensaver activating and changing as per my setup. At approximately 3:10pm I looked and noticed a black screen with only the mouse cursor visible. It could be moved and if it happened to alight on a clickable area it would change to the hand tool but remember the screen was black. I saw the following lines in my syslog:

Oct 12 13:43:56 localhost kernel: [578580.434416] [drm:i915_gem_open]
Oct 12 13:44:45 localhost kernel: [578628.874770] [drm:drm_mode_addfb2] [FB:60]
Oct 12 13:44:48 localhost kernel: [578631.820045] [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle

13:44:48 was more than likely the time that the video froze.

The output of cat /sys/class/drm/card0/error shows:

no error state collected

The output of cat /sys/kernel/debug/dri/0/i915_swizzle_info shows

bit6 swizzle for X-tiling = none
bit6 swizzle for Y-tiling = none
DDC = 0x00200010
DDC2 = 0x00300030
C0DRB3 = 0x0030
C1DRB3 = 0x0010

I'm attaching kern.log and dmesg

[penalvch (penalvch)]

chris pollock, could you please test the latest mainline kernel (4.3-rc5) and advise if this issue is reproducible?

[chris pollock (cpollock)]

As with the other 4.3rc* kernels previous to this one the initial boot would start then would go to a black screen. Hard restart with power button required. Syslog entries for this are attached. Back to kernel 4.2.3-040203-generic #201510030832 SMP Sat Oct 3 12:34:31 UTC 2015. Let me know if you wish me to start XScreensaver again or try anything else.

[chris pollock (cpollock)]

I am now able to replicate my video freeze by lowering and raising windows at a fast pace. When doing this my screen will 'flicker' for an instant and at times will continue to flicker. The flicker consists actually of two areas on the screen. I've tried to capture a screen shot when the continuous flicker is happening but as soon as I raise the window for Gnome screen shot the flicker stops. Tonight when lowering and raising windows at a fast pace the freeze occurred. Running

cat /sys/kernel/debug/dri/0/i915_swizzle_info outputted:

bit6 swizzle for X-tiling = none
bit6 swizzle for Y-tiling = none
DDC = 0x00200010
DDC2 = 0x00300030
C0DRB3 = 0x0030
C1DRB3 = 0x0010

Running cat /sys/class/drm/card0/error outputted:

no error state collected

The freeze occurred at 20:07:39 my syslog shows this for that time period

Oct 14 20:07:32 localhost kernel: [171877.801126] [drm:drm_mode_addfb2] [FB:57]
Oct 14 20:07:32 localhost kernel: [171877.838608] [drm:drm_mode_addfb2] [FB:60]
Oct 14 20:07:32 localhost kernel: [171877.926645] [drm:drm_mode_addfb2] [FB:64]
Oct 14 20:07:32 localhost kernel: [171877.944068] [drm:drm_mode_addfb2] [FB:65]
Oct 14 20:07:32 localhost kernel: [171877.975866] [drm:drm_mode_addfb2] [FB:66]
Oct 14 20:07:32 localhost kernel: [171877.993399] [drm:drm_mode_addfb2] [FB:67]
Oct 14 20:07:33 localhost kernel: [171879.439826] [drm:drm_mode_addfb2] [FB:68]
Oct 14 20:07:33 localhost kernel: [171879.462886] [drm:drm_mode_addfb2] [FB:69]
Oct 14 20:07:33 localhost kernel: [171879.480867] [drm:drm_mode_addfb2] [FB:70]
Oct 14 20:07:36 localhost kernel: [171881.525273] [drm:drm_mode_addfb2] [FB:57]
Oct 14 20:07:36 localhost kernel: [171881.660074] [drm:drm_mode_addfb2] [FB:59]
Oct 14 20:07:36 localhost kernel: [171881.676724] [drm:drm_mode_addfb2] [FB:64]
Oct 14 20:07:36 localhost kernel: [171881.710189] [drm:drm_mode_addfb2] [FB:65]
Oct 14 20:07:36 localhost kernel: [171881.726965] [drm:drm_mode_addfb2] [FB:66]
Oct 14 20:07:36 localhost kernel: [171881.743498] [drm:drm_mode_addfb2] [FB:67]
Oct 14 20:07:36 localhost kernel: [171881.786167] [drm:drm_mode_addfb2] [FB:68]

The flicker also appears when switching between window applications such as from window 1 Evolution to window 2 Firefox or any other window.

[chris pollock (cpollock)]

Do I need to open another bug report at Freedesktop. org on this? I've posted about the above on the intel-gfx mailing list however I've not received any kind of a reply. Do I need to revert back to an earlier kernel to see if this still persists?

[chris pollock (cpollock)]

At approximately 19:20 this evening I looked at my desktop monitor and saw that the clock had stopped at 17:44:24. The only thing that shows up in my syslog during that time period is:

Oct 18 17:44:24 localhost kernel: [336093.031878] [drm:drm_mode_addfb2] [FB:59]
Oct 18 17:44:24 localhost kernel: [336093.051163] [drm:drm_mode_addfb2] [FB:60]
Oct 18 17:44:24 localhost kernel: [336093.072544] [drm:drm_mode_addfb2] [FB:62]

The same in my kern.log although I've attached it for your review.

I moved the mouse a few times and the clock suddenly caught up to the correct time.

[chris pollock (cpollock)]

This morning at 08:21:15 video froze when I was switching tabs using Firefox 41.0.2. As usual the cursor would still move. The uptime was 4d 12h when this happened. There are no abnormal outputs in my syslog or my kern.log for that time period. Still using kernel 4.2.3-040203-generic #201510030832 SMP Sat Oct 3 12:34:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[chris pollock (cpollock)]

Since I can now reproduce this bug is there anything else I need to be doing?

[chris pollock (cpollock)]

Today, 24 October, 2015 11:26:22am video froze while I was scrolling through my Twitter feed using Firefox 41.0.2. The uptime on the system since the last freeze was 4d23h54m since the last freeze. I'll attach today's syslog, dmesg and the kern.log from when the freeze happened.

[chris pollock (cpollock)]

Since none of those on the notification list probably want direct emails I'm asking what is being done to rectify this bug and/or what else can I do to try and troubleshoot it? It's becoming very bothersome when every few days I have to stop working on a document because of a video freeze.

[chris pollock (cpollock)]

Another video freeze tonight at 20:20:17 with an uptime of 23d 6h. This happened while I was scrolling through my Twitter feed using Firefox v42.0. Nothing odd noted in the Syslog and as usual all background processes continue to run normally.

[chris pollock (cpollock)]

Video froze today at 12:48pm. I was not in the room at the time and came back to find it frozen at approx 14:15. As I checked to make sure the cursor would still move I clicked on the block showing the different desktop windows I had open the clock began running again. I've attached the kern.log. I'd like to know what all the notations for today that reference the below mean.

kernel: [65411.788745] [drm:drm_mode_addfb2] [FB:57]

[chris pollock (cpollock)]

Video froze this morning after an uptime of 47d 12h 04m. At the time it happened I was using Firefox 43.0.3 and scrolling through timeline on Facebook. No problems are noted in the syslog when this happened. I logged into the system via SSH from my tablet and rebooted into kernel:

Linux localhost 3.19.0-42-generic #48~14.04.1-Ubuntu SMP Fri Dec 18 10:24:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[chris pollock (cpollock)]

Video froze last night, 01/17/2016 21:06:30 after uptime of 14d 12h 40m from the last video freeze. I was running kernel 3.19.0-42-generic #48~14.04.1-Ubuntu SMP Fri Dec 18 10:24:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) at the time. This time the hangcheck error was noted in my syslog

Jan 17 21:17:32 localhost kernel: [1255120.808035] [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle

I did a reboot via SSH from my tablet and loaded the newest 3.19 kernel

3.19.0-43-generic #49~14.04.1-Ubuntu SMP Thu Dec 31 15:44:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

As usual during these freezes the mouse cursor would move but all other actions are frozen. Could not switch to another desktop and so forth.

[chris pollock (cpollock)]

I've been a bit negligent about reporting the last couple of freezes as it seems like nothing is being done about it. So now I'd like to report that on 02/25/2016; 03/08/2016 and 03/11/2016 the video froze, the mouse cursor would move as you can see the attached syslog snippets the system continues to function. I've been running kernel 3.19.0-51-generic #58~14.04.1-Ubuntu SMP Fri Feb 26 22:02:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux since the 03/08/2016 freeze.

Mar 8 14:45:14 localhost kernel: [ 0.000000] Linux version 3.19.0-51-generic (buildd@lgw01-44) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1) ) #58~14.04.1-Ubuntu SMP Fri Feb 26 22:02:58 UTC 2016 (Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13)

The "Hangcheck timer elasped......." error has not shown up in any of these video freezes.

[chris pollock (cpollock)]

As you can see the video froze at 03:44 am this morning but services continued to run in the background as usual

[chris pollock (cpollock)]

One other thing that I've neglected to mention in all of my comments is that the clock that I have on the upper taskbar will freeze also at the exact time of the video freeze although it keeps running internally as shown in my attachment of this morning.