i915 graphics errors detected

[kl522]

When I use Knoppix 6.4.4 on my dell notebook with intel graphics, I got
this in the 'dmesg' output. Anyone see the same thing on their i915
intel graphics ? I found many similar posts on the net, but none has
provided with a fix.

 [drm] Initialized drm 1.1.0 20060810
[   33.290603] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   33.290609] i915 0000:00:02.0: setting latency timer to 64
[   33.309484] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
[   33.309487] [drm] MTRR allocation failed.  Graphics performance may suffer.
[   33.312984] i915 0000:00:02.0: irq 45 for MSI/MSI-X
[   33.379226] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   33.380025] render error detected, EIR: 0x00000010
[   33.380025]   IPEIR: 0x00000000
[   33.380025]   IPEHR: 0x00000000
[   33.380025]   INSTDONE: 0xfffffffe
[   33.380025]   INSTPS: 0x00000000
[   33.380025]   INSTDONE1: 0xffffffff
[   33.380025]   ACTHD: 0x02000000
[   33.380025] page table error
[   33.380025]   PGTBL_ER: 0x00100000
[   33.380025] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

[utu]

I've got an Inspiron 1545; dmesg | grep 915 gives me:

[ 21.812915] atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
[ 48.512525] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 48.512531] i915 0000:00:02.0: setting latency timer to 64
[ 48.534182] i915 0000:00:02.0: irq 43 for MSI/MSI-X
[ 48.966912] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

[utu]

dmesg | grep -i error gives, among other things that are probably not pertinent:

[ 48.588813] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[ 48.983136] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[ 48.990094] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[ 48.990099] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.

The backlight problem is a known problem, which doesn't affect me using the laptop
as a desktop.