Bug 552395 - Kernel error messages about DRM, EIR and video mode
Summary: Kernel error messages about DRM, EIR and video mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-04 21:46 UTC by danhouw
Modified: 2010-07-08 13:21 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-07 09:57:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 15187 0 None None None Never

Description danhouw 2010-01-04 21:46:20 UTC
Description of problem:
-----------------------
After Fed 12 new installation and on each boot, the boot sequence throws :
1. once :
a render error detected, EIR: 0x00000010
[drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
this before the graphical boot squence
2. continuously :
[drm] DAC-6: set mode 640x480 0
[drm] DAC-6: set mode 640x480 0

My laptop (Dell Inspiron 510m) work in 1400x1050 (Runlevel 5 and 3) at the end of the boot but the /var/log/messages still grows.

Is there something to improve in the config to avoid the log noise ?

Log output :
------------
[drm] Initialized drm 1.1.0 20060810

i915 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11

integrated sync not supported
[drm] DAC-6: set mode 640x480 0
integrated sync not supported
fbcon: inteldrmfb (fb0) is primary device
render error detected, EIR: 0x00000010
[drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
[drm] LVDS-8: set mode 1400x1050 10
Console: switching to colour frame buffer device 175x65
fb0: inteldrmfb frame buffer device
registered panic notifier
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
dracut: Starting plymouth daemon
[drm] DAC-6: set mode 640x480 0
[drm] DAC-6: set mode 640x480 0
...
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
...
[drm] DAC-6: set mode 640x480 0
[drm] DAC-6: set mode 640x480 0
...
integrated sync not supported
[drm] DAC-6: set mode 640x480 0
[drm] DAC-6: set mode 640x480 0
...
etc.

Version : kernel 2.6.31.5-127.fc12.i686
---------

How reproducible: Each boot
-----------------

Additional info:
----------------
lspci -v =>
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 0164
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at f0000000 (32-bit, prefetchable) [size=128M]
	Memory at faf80000 (32-bit, non-prefetchable) [size=512K]
	I/O ports at c000 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [d0] Power Management version 1
	Kernel driver in use: i915
	Kernel modules: i915
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
	Subsystem: Dell Device 0164
	Flags: bus master, fast devsel, latency 0
	Memory at e8000000 (32-bit, prefetchable) [size=128M]
	Memory at faf00000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [d0] Power Management version 1

xrandr =>
Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 2048 x 2048
LVDS1 connected 1400x1050+0+0 (normal left inverted right x axis y axis) 305mm x 228mm
   1400x1050      60.0*+   60.0  
   1280x1024      60.0  
   1280x960       60.0  
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
VGA1 disconnected (normal left inverted right x axis y axis)
DVI1 disconnected (normal left inverted right x axis y axis)

Comment 1 Bruno Matos 2010-01-13 15:32:01 UTC
Hello,

Same to me with kernel 2.6.31.9-174.fc12.i686.PAE. I have an IBM with intel graphics card, that is always freezing.

More details, please ask.

Thanks.

Comment 2 Alberto 2010-01-30 11:10:25 UTC
I have a related problem: my Dell Latitude D505 (i915 graphic chipset) flashes red-green-blue-black-white from very early in kernel boot sequence, even before starting services. I got this in messages log:

J
Jan 30 11:53:05 pamovi11 klogd: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:1e/input/input7
Jan 30 11:53:05 pamovi11 klogd: ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
Jan 30 11:53:05 pamovi11 klogd: ACPI Warning (nspredef-0437): \_SB_.PCI0.VID2._DOD: Return Package has no elements (empty) [20090320]
Jan 30 11:53:05 pamovi11 klogd: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:24/input/input8
Jan 30 11:53:05 pamovi11 klogd: ACPI: Video Device [VID2] (multi-head: yes  rom: no  post: no)
Jan 30 11:53:05 pamovi11 klogd: [drm] Initialized drm 1.1.0 20060810
Jan 30 11:53:05 pamovi11 klogd: i915 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Jan 30 11:53:05 pamovi11 klogd: integrated sync not supported
Jan 30 11:53:05 pamovi11 klogd: [drm] DAC-6: set mode 640x480 0
Jan 30 11:53:05 pamovi11 klogd: integrated sync not supported

This is booting with kernel-2.6.30.10-105.2.4.fc11.i586. However, when I boot with kernel-2.6.29.6-99.fc10.i686, everything's fine.

Comment 3 Alberto 2010-02-10 10:55:09 UTC
It looks like the kernel is erroneously detecting the graphics hardware as i915, while it's a 855GM. I just added the option i915.modeset=0 to switch off KMS and now it works OK.

Comment 4 Bruno Matos 2010-02-10 12:18:43 UTC
(In reply to comment #3)
> It looks like the kernel is erroneously detecting the graphics hardware as
> i915, while it's a 855GM. I just added the option i915.modeset=0 to switch off
> KMS and now it works OK.    

Thanks, it worked for me too!

Makes things a little bit ugly, but its ok until it's fixed...

Comment 5 Robert de Rooy 2010-02-15 10:37:57 UTC
@ Alberto, it is saying i915 because that is what the driver is called. It supports the older 855 chips also. And disabling KMS disables these codepaths, so you do not get the error. But that will not be an option any more with F13 as Intel has removed the old UMS support from their Xorg driver, so it is important to get it fixed. Also I have a suspicion your problem is different and unrelated to this bug report.

In any case, I am seeing the same i915_handle_error on my old ThinkPad X40 with 855GM, and found an upstream bugzilla.kernel.org report on it.
http://bugzilla.kernel.org/show_bug.cgi?id=15187

Comment 6 Eason 2010-02-18 10:56:15 UTC
Hi all,

I had the same problem after upgraded my ThinkPad X40 from Fedora 11 to 12.

The kernel version: 2.6.31.12-174.2.19

If I added the option i915.modeset=0,then I got a blank sreen. Any idea?

Thanks

Comment 7 Robert de Rooy 2010-02-20 08:28:31 UTC
Upstream bug report was closed with the following comments:

Comment #4 From  Jesse Barnes   2010-02-19 20:33:15   (-) [reply] -------

These errors should be fixed now; turned out to be a bad alignment in our
framebuffer code.

------- Comment #5 From Jesse Barnes 2010-02-19 20:37:05 (-) [reply] -------

If you still see hangs with the drm-intel-next intel branch, please open a new
bug since this particular one should be fixed now (the EIR errors on load).

---------

So now it is waiting for these fixes to be merged into the Fedora F12 kernel

Comment 8 Robert de Rooy 2010-03-08 13:03:29 UTC
Not seeing this any more with kernel-2.6.32.9-70.fc12.x86_64 out of updates-testing

Comment 9 John DeDourek 2010-03-08 14:06:50 UTC
Fixed for me with kernel-2.6.32.9-67.fc12.i686 from updates.

Comment 10 danhouw 2010-03-08 16:43:34 UTC
With the last available fedora kernel (kernel-2.6.32.9-67.fc12.i686), both messages disappeared.

"render error detected, EIR: 0x00000010" is gone from initial boot console.
Fedora logo comes up a lot faster during boot sequence.

"[drm] DAC-6: set mode 640x480 0" is no more flooding the /var/log/meesages.

So this bug seems to be resolved.

But another new (for me) negative message appears now :
"[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own."
This appears only once in the /var/log/meesages, and without any bad effect.
This message is already related in Bug 539709.

Comment 11 John DeDourek 2010-03-08 16:57:57 UTC
Yes, I see this too.

Comment 12 John DeDourek 2010-03-08 17:27:12 UTC
Actually, my log files show that this error occurred as far back as 
Feb 10, which predates kernel 2.6.31.12-174.2.19.fc12.  I can't check
further back because only latest five logs (five weeks) and latest 3
kernels are kept.

Comment 13 Robert de Rooy 2010-07-07 09:57:05 UTC
closing this as resolved in current release, based on various comments


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