|Summary:||[845G] Video is not initializing|
|Product:||DRI||Reporter:||Joe N <noble>|
|Component:||DRM/Intel||Assignee:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|Status:||CLOSED NOTOURBUG||QA Contact:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|i915 platform:||i915 features:|
Description Joe N 2015-05-17 18:00:47 UTC
Created attachment 115858 [details] Linux error file - sent from Windows computer Dmesg reported: [drm] GPU crash dump saved to /sys/class/drm/card0/error [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. i915: render error detected, EIR: 0x00000010 [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking i915: render error detected, EIR: 0x00000010
Comment 1 Chris Wilson 2015-05-17 19:53:32 UTC
In this circumstance, the drm.debug=6 (set on the grub kernel commandline) dmesg is vital.
Comment 2 Joe N 2015-05-17 22:18:34 UTC
This is a Dell Dimension 2400 with 1GB of main memory. It's running CentOS 6+ latest updates.
Comment 3 Ander Conselvan de Oliveira 2015-05-18 06:06:45 UTC
Joe, as Chris requested on comment 1, please add drm.debug=6 to your kernel command line and then attach the output of the dmesg command to this bug report.
Comment 4 Joe N 2015-05-18 22:34:30 UTC
Created attachment 115886 [details] Here's dmesg w/ drm.debug=6 Added the command to the kernel line in /boot/grub/grub.conf kernel line to generate this file. Guys, thanks for looking into this so quickly.
Comment 5 Joe N 2015-05-19 00:51:23 UTC
Fyi my monitor is an Acer S201HL 20inich.
Comment 6 Ander Conselvan de Oliveira 2015-05-19 06:54:06 UTC
Unfortunately we cannot give support for your kernel version, which is over 5 years old now. However, it seems your distro have backported a newer i915 driver to it, so you should ask them for support. If you can reproduce the issue with a recent kernel, please reopen.