kernel: [154858.820009] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed.
I'm hoping I can get some advice/help here on this list with the above problem that is causing system lockups. I didn't want to post to the main list as I'm not sure it would be appropriate, I'm not even sure it's appropriate here but I'll give it a try. If someone has a better list to post to please let me know. I have noticed the lockups periodically since 09/13/2014. I can't remember what kernel version was in use then possibly kernel 3.13.0-35-generic or -36. It has continued periodically through versions -39; -40 and now to -43. The last time this has happened was Dec 13 14:40:57 localhost kernel: [154858.820009] [drm:i915_hangcheck_ elapsed] *ERROR* Hangcheck timer elapsed... render ring idle. At times when it locks up I will have a cursor on a black screen and will have to press the power button to restart other times it will lockup whenever I'm in an application. At that time I can usually CTRL>ALT-F1 log in and run 'sudo reboot' to restart the system. Kernel version information is: Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu 3.13.0-43.72-generic 3.13.11.11) I'll be more than willing to submit any and all information anyone needs to help me solve this. One reply I received to my bug report is that I need to update my bios however I don't understand how that would solve the problem I'm having. Thanks in advance for any and all replies/assistance. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 07:35:26 up 21:05, 2 users, load average: 0.42, 0.25, 0.18 Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
On Mon, Dec 15, 2014 at 08:02:13AM -0600, Chris wrote:
I'm hoping I can get some advice/help here on this list with the above problem that is causing system lockups. I didn't want to post to the main list as I'm not sure it would be appropriate, I'm not even sure it's appropriate here but I'll give it a try. If someone has a better list to post to please let me know.
I have noticed the lockups periodically since 09/13/2014. I can't remember what kernel version was in use then possibly kernel 3.13.0-35-generic or -36. It has continued periodically through versions -39; -40 and now to -43. The last time this has happened was Dec 13 14:40:57 localhost kernel: [154858.820009] [drm:i915_hangcheck_ elapsed] *ERROR* Hangcheck timer elapsed... render ring idle. At times when it locks up I will have a cursor on a black screen and will have to press the power button to restart other times it will lockup whenever I'm in an application. At that time I can usually CTRL>ALT-F1 log in and run 'sudo reboot' to restart the system.
Kernel version information is:
Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu 3.13.0-43.72-generic 3.13.11.11)
That's a very old distro-specific kernel, try building a kernel.org release (like 3.18) and see if the problem is still there or not. No one in the community can help with old, distro-specific kernels, except for the distro itself. There are lots of Intel graphic driver changes happening in the kernel, I strongly recommend updating if you have an issue with your hardware. I got 2 _hours_ battery life extension in the 3.17 kernel alone due to Intel driver fixes. good luck, greg k-h
On Mon, 2014-12-15 at 08:58 -0800, Greg KH wrote:
On Mon, Dec 15, 2014 at 08:02:13AM -0600, Chris wrote:
I'm hoping I can get some advice/help here on this list with the above problem that is causing system lockups. I didn't want to post to the main list as I'm not sure it would be appropriate, I'm not even sure it's appropriate here but I'll give it a try. If someone has a better list to post to please let me know.
I have noticed the lockups periodically since 09/13/2014. I can't remember what kernel version was in use then possibly kernel 3.13.0-35-generic or -36. It has continued periodically through versions -39; -40 and now to -43. The last time this has happened was Dec 13 14:40:57 localhost kernel: [154858.820009] [drm:i915_hangcheck_ elapsed] *ERROR* Hangcheck timer elapsed... render ring idle. At times when it locks up I will have a cursor on a black screen and will have to press the power button to restart other times it will lockup whenever I'm in an application. At that time I can usually CTRL>ALT-F1 log in and run 'sudo reboot' to restart the system.
Kernel version information is:
Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu 3.13.0-43.72-generic 3.13.11.11)
That's a very old distro-specific kernel, try building a kernel.org release (like 3.18) and see if the problem is still there or not. No one in the community can help with old, distro-specific kernels, except for the distro itself.
There are lots of Intel graphic driver changes happening in the kernel, I strongly recommend updating if you have an issue with your hardware. I got 2 _hours_ battery life extension in the 3.17 kernel alone due to Intel driver fixes.
good luck,
greg k-h
That's what I thought Greg but wanted to make sure. AFAIK I'm not having any hardware related issues but I would like to know what the 'Hangcheck timer' is. Possibly you can enlighten me? Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 11:57:50 up 2 min, 1 user, load average: 2.78, 1.92, 0.78 Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
On Mon, Dec 15, 2014 at 11:59:27AM -0600, Chris wrote:
On Mon, 2014-12-15 at 08:58 -0800, Greg KH wrote:
On Mon, Dec 15, 2014 at 08:02:13AM -0600, Chris wrote:
I'm hoping I can get some advice/help here on this list with the above problem that is causing system lockups. I didn't want to post to the main list as I'm not sure it would be appropriate, I'm not even sure it's appropriate here but I'll give it a try. If someone has a better list to post to please let me know.
I have noticed the lockups periodically since 09/13/2014. I can't remember what kernel version was in use then possibly kernel 3.13.0-35-generic or -36. It has continued periodically through versions -39; -40 and now to -43. The last time this has happened was Dec 13 14:40:57 localhost kernel: [154858.820009] [drm:i915_hangcheck_ elapsed] *ERROR* Hangcheck timer elapsed... render ring idle. At times when it locks up I will have a cursor on a black screen and will have to press the power button to restart other times it will lockup whenever I'm in an application. At that time I can usually CTRL>ALT-F1 log in and run 'sudo reboot' to restart the system.
Kernel version information is:
Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu 3.13.0-43.72-generic 3.13.11.11)
That's a very old distro-specific kernel, try building a kernel.org release (like 3.18) and see if the problem is still there or not. No one in the community can help with old, distro-specific kernels, except for the distro itself.
There are lots of Intel graphic driver changes happening in the kernel, I strongly recommend updating if you have an issue with your hardware. I got 2 _hours_ battery life extension in the 3.17 kernel alone due to Intel driver fixes.
good luck,
greg k-h
That's what I thought Greg but wanted to make sure. AFAIK I'm not having any hardware related issues but I would like to know what the 'Hangcheck timer' is. Possibly you can enlighten me?
That looks like a driver-specific timer, the code would tell you more, take a look at it! greg k-h
On Mon, 15 Dec 2014 10:01:54 -0800, Greg KH said:
On Mon, Dec 15, 2014 at 11:59:27AM -0600, Chris wrote:
That's what I thought Greg but wanted to make sure. AFAIK I'm not having any hardware related issues but I would like to know what the 'Hangcheck timer' is. Possibly you can enlighten me?
That looks like a driver-specific timer, the code would tell you more, take a look at it!
I'm pretty sure that's a timer for the i915 driver that detects if the GPU has gone into an infinite loop due to (usually) buggy programming from the operating system....
On Mon, 2014-12-15 at 13:43 -0500, Valdis.Kletnieks@vt.edu wrote:
On Mon, 15 Dec 2014 10:01:54 -0800, Greg KH said:
On Mon, Dec 15, 2014 at 11:59:27AM -0600, Chris wrote:
That's what I thought Greg but wanted to make sure. AFAIK I'm not having any hardware related issues but I would like to know what the 'Hangcheck timer' is. Possibly you can enlighten me?
That looks like a driver-specific timer, the code would tell you more, take a look at it!
I'm pretty sure that's a timer for the i915 driver that detects if the GPU has gone into an infinite loop due to (usually) buggy programming from the operating system....
Thank you Valdis as far as the OS we're talking about Ubuntu not the bios correct? Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 14:12:54 up 2:17, 1 user, load average: 0.26, 0.18, 0.15 Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
On Mon, 15 Dec 2014 14:19:32 -0600, Chris said:
On Mon, 2014-12-15 at 13:43 -0500, Valdis.Kletnieks@vt.edu wrote:
I'm pretty sure that's a timer for the i915 driver that detects if the GPU has gone into an infinite loop due to (usually) buggy programming from the operating system....
Thank you Valdis as far as the OS we're talking about Ubuntu not the bios correct?
More specifically, the i915 is actually a fully programmable CPU in its own right, but it's a crazy morass of interrupts and circular buggers and race conditions. The operating system (Ubuntu or what have you) actually send the i915 a program of what to display, and the i915 goes off and does it. Of course, missing a single interrupt or an off-by-one error in a circular buffer will cause the i915 to go off the rails and usually get hung in a hard loop. (It doesn't help that the i915 has a ton of wonky restrictions of the form "you can do this during a vertical retrace period, but only during the first half of a horizontal retrace". And yes, I'm pretty sure it actually enforces vertical and horizontal retrace timings on LCDs. Silly, huh? ;)
On Mon, 2014-12-15 at 16:11 -0500, Valdis.Kletnieks@vt.edu wrote:
On Mon, 15 Dec 2014 14:19:32 -0600, Chris said:
On Mon, 2014-12-15 at 13:43 -0500, Valdis.Kletnieks@vt.edu wrote:
I'm pretty sure that's a timer for the i915 driver that detects if the GPU has gone into an infinite loop due to (usually) buggy programming from the operating system....
Thank you Valdis as far as the OS we're talking about Ubuntu not the bios correct?
More specifically, the i915 is actually a fully programmable CPU in its own right, but it's a crazy morass of interrupts and circular buggers and race conditions. The operating system (Ubuntu or what have you) actually send the i915 a program of what to display, and the i915 goes off and does it. Of course, missing a single interrupt or an off-by-one error in a circular buffer will cause the i915 to go off the rails and usually get hung in a hard loop.
(It doesn't help that the i915 has a ton of wonky restrictions of the form "you can do this during a vertical retrace period, but only during the first half of a horizontal retrace". And yes, I'm pretty sure it actually enforces vertical and horizontal retrace timings on LCDs. Silly, huh? ;)
I believe I understand Valdis, what kind of actions would need to be taken to track this down, if it's possible, or to simply fix the problem once and for all? -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 15:16:18 up 3:21, 3 users, load average: 0.17, 0.19, 0.18 Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
On Mon, 15 Dec 2014 15:17:32 -0600, Chris said:
I believe I understand Valdis, what kind of actions would need to be taken to track this down, if it's possible, or to simply fix the problem once and for all?
The assumption is "this problem" is only one problem. At last count, there's been like 947 similar bugs with the i915 (possibly a slight exaggeration). About all you can do here is turn on i915 debugging and dump the entrails that result on the i915 maintainers and hope they can figure out what went wrong *this* time....
On Mon, 2014-12-15 at 17:54 -0500, Valdis.Kletnieks@vt.edu wrote:
On Mon, 15 Dec 2014 15:17:32 -0600, Chris said:
I believe I understand Valdis, what kind of actions would need to be taken to track this down, if it's possible, or to simply fix the problem once and for all?
The assumption is "this problem" is only one problem. At last count, there's been like 947 similar bugs with the i915 (possibly a slight exaggeration). About all you can do here is turn on i915 debugging and dump the entrails that result on the i915 maintainers and hope they can figure out what went wrong *this* time.... After more Googling I see a bug report has already been submitted for this exact same issue. -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 17:56:13 up 6:01, 1 user, load average: 0.01, 0.09, 0.12 Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
On Mon, 2014-12-15 at 21:04 -0500, Valdis.Kletnieks@vt.edu wrote:
On Mon, 15 Dec 2014 17:57:38 -0600, Chris said:
After more Googling I see a bug report has already been submitted for this exact same issue.
Well, that simplifies it a lot for you. :)
Most definitely, now working on adding as much info as I can about what I've experienced. Thanks to you and Greg for your timely assistance. I really appreciate it. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 20:08:30 up 8:13, 1 user, load average: 0.14, 0.18, 0.16 Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
participants (3)
-
Chris -
Greg KH -
Valdis.Kletnieks＠vt.edu