DRM Intel i915 errors

Hi,
After going out of blank mode, my external VGA monitor will randomly refuse to work (the primary laptop monitor works fine). This seems to be fixable only by rebooting.
Those errors show up in dmesg just after booting the computer :
[lun. avril 20 09:15:34 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 09:15:35 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 09:15:53 2015] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[lun. avril 20 09:15:53 2015] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Those show up every few minutes or so :
[lun. avril 20 12:35:30 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 12:38:29 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:15:04 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:23:17 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:23:30 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:23:49 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:24:03 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:57:58 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[lun. avril 20 13:58:11 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
When coming out of blank mode, those show up :
[lun. avril 20 14:16:06 2015] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[lun. avril 20 14:16:06 2015] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to start channel equalization
[lun. avril 20 14:16:07 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
I've already changed the acceleration method to UXA, without results (although I believe the problem show up less frequently but I'm unsure).
Any idea ?
Thanks in advance

Hi gentledevil,
There is a similar thread here https://bbs.archlinux.org/viewtopic.php?id=184857 and also a couple of bug reports [1] [2]. Unfortunately there is no solution yet.
gentledevil wrote:[lun. avril 20 12:35:30 2015] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
Also, searching the kernel bug tracker for the error above leads to the the following report that may be related https://bugzilla.kernel.org/show_bug.cgi?id=90951

Similar Messages

Configure a intel i915 (Solved)

I need help to configure a intel i915 chipset, I installed the 3ddesktop package, and the command "3ddesk" gives me this message:
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Daemon started. Run 3ddesk to activate.
Server not found after waiting 5 seconds.
Could not find server.
Try starting manually (3ddeskd)
Then I tried with "3ddeskd" and got:
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Daemon started. Run 3ddesk to activate.
And so it goes and goes, then the command glxgears gives me this other message:
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual
So, I guess my card is not configured properly, so how can I make it work on xorg 7?
this is my xorg.conf:
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
# Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "latam"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mouse0"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "HPvs15"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5, 35.15, 35.5
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-70
EndSection
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "** Intel i810 (generic) [i810]"
Driver "i810"
#VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "** Intel i810 (generic) [i810]"
Monitor "HPvs15"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
[/list]

Here's a copy of my Xorg.conf designed for i810/i910, just copy the contents over your xorg.conf (make backup!!) and adjust it to your needs (u may want to change the keyboard layout)
This xorg conf work with nomal as well as Xinerama by doing
startx -- -layout Xinerama
:arrow: http://arch.pastebin.com/613767

Intel i915 hangs

Hi,
Recently my system has been exhibiting seemingly random freezes once every couple days. All of a sudden, nothing responds except I can still move the mouse cursor around; typing has no effect, trying to switch to a tty does nothing. The system still responds to ping though. Sshd isn't running by default so I couldn't try logging in from another machine.
For what it's worth it happened once when I used Firefox, and another time when I was doing Java development.
When it's stuck like that I just force reboot the thing. I don't really know what's going on -- although if I had to guess, the most likely culprit would be something related to X, bumblebee or bbswitch. How could I be sure though? In what log files (or other things) could I look to find out what has crashed?
Thanks for any input!
Last edited by ilikepie (2012-02-29 19:25:37)

I do have RC6 enabled but I only see the hangcheck errors with the mainline kernel, not the lts version. Although my laptop may have overheated on Monday evening (when it woke up from suspend in transit and I didn't realise), I didn't get any of these errors at that time even though the mainline kernel was in use. Rather I got such errors earlier in the day. Generally speaking, my laptop does not run especially hot (at least in comparison with my old one!) and so I certainly don't think it is an overheating issue in my case. grepping i915 in kernel.log:
Mar 25 16:27:30 localhost kernel: [125351.620968] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 25 16:27:30 localhost kernel: [125351.620982] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 25 16:27:30 localhost kernel: [125351.622711] i915 0000:00:02.0: setting latency timer to 64
Mar 25 21:05:36 localhost kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=<UUID> ro quiet add_efi_memmap resume=/dev/disk/by-uuid/<UUID> pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1
Mar 25 21:05:36 localhost kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=<UUID> ro quiet add_efi_memmap resume=/dev/disk/by-uuid/<UUID> pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1
Mar 25 21:05:36 localhost kernel: [ 2.786357] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar 25 21:05:36 localhost kernel: [ 2.786364] i915 0000:00:02.0: setting latency timer to 64
Mar 25 21:05:36 localhost kernel: [ 2.879557] i915 0000:00:02.0: irq 40 for MSI/MSI-X
Mar 25 21:05:36 localhost kernel: [ 3.693054] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Mar 26 12:27:16 localhost kernel: [18335.425865] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 26 12:27:16 localhost kernel: [18335.425879] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 26 12:27:16 localhost kernel: [18335.427586] i915 0000:00:02.0: setting latency timer to 64
Mar 26 12:35:32 localhost kernel: [18834.108099] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 12:35:38 localhost kernel: [18840.120747] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 12:35:45 localhost kernel: [18847.936499] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 12:35:45 localhost kernel: [18847.936513] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
Mar 26 12:35:45 localhost kernel: [18847.954065] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 291299 at 291290, next 291304)
Mar 26 12:55:28 localhost kernel: [20030.749987] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 12:55:34 localhost kernel: [20036.762624] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 12:55:40 localhost kernel: [20042.778602] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 12:55:40 localhost kernel: [20042.778667] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 991598 at 991589, next 991605)
Mar 26 13:25:31 localhost kernel: [21832.875276] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 13:25:37 localhost kernel: [21838.887919] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 13:25:43 localhost kernel: [21844.900559] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 13:25:43 localhost kernel: [21844.900594] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 2053554 at 2053551, next 2053574)
Mar 26 13:25:49 localhost kernel: [21851.246493] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 13:25:55 localhost kernel: [21857.259141] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 13:26:01 localhost kernel: [21863.271772] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 26 13:26:01 localhost kernel: [21863.271839] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 2053595 at 2053575, next 2053597)
Mar 26 13:59:50 localhost kernel: [23892.078870] Modules linked in: fuse aes_x86_64 cryptd aes_generic cpufreq_ondemand coretemp rfcomm bnep ip6t_REJECT ip6t_LOG nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT ipt_LOG xt_limit xt_recent xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_conexant joydev snd_hda_intel uvcvideo snd_hda_codec arc4 snd_hwdep snd_pcm snd_page_alloc snd_timer iwlwifi thinkpad_acpi videodev nvram snd v4l2_compat_ioctl32 mac80211 iTCO_wdt tpm_tis btusb bluetooth media atl1c iTCO_vendor_support cfg80211 serio_raw soundcore rts_pstor(C) mei(C) rfkill tpm psmouse wmi i2c_i801 thermal battery evdev pcspkr tpm_bios ac acpi_cpufreq mperf processor freq_table ext4 crc16 jbd2 mbcache usbhid hid sd_mod ahci libahci libata scsi_mod ehci_hcd usbcore usb_common i915 video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm i2c_core
Mar 26 22:17:49 localhost kernel: [ 2.562799] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar 26 22:17:49 localhost kernel: [ 2.562806] i915 0000:00:02.0: setting latency timer to 64
Mar 26 22:17:49 localhost kernel: [ 2.664602] i915 0000:00:02.0: irq 40 for MSI/MSI-X
Mar 26 22:17:49 localhost kernel: [ 3.488876] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Mar 26 22:24:41 localhost kernel: [ 463.839027] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 26 22:24:41 localhost kernel: [ 463.839041] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 26 22:24:41 localhost kernel: [ 463.840793] i915 0000:00:02.0: setting latency timer to 64
Mar 26 22:48:29 localhost kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=<UUID> ro quiet add_efi_memmap resume=/dev/disk/by-uuid/<UUID> pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1
Mar 26 22:48:29 localhost kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=<UUID> ro quiet add_efi_memmap resume=/dev/disk/by-uuid/<UUID> pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1
Mar 26 22:48:29 localhost kernel: [ 3.836110] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar 26 22:48:29 localhost kernel: [ 3.836117] i915 0000:00:02.0: setting latency timer to 64
Mar 26 22:48:29 localhost kernel: [ 3.927448] i915 0000:00:02.0: irq 40 for MSI/MSI-X
Mar 26 22:48:29 localhost kernel: [ 4.683794] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Mar 27 11:54:37 localhost kernel: [12884.470794] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 27 11:54:37 localhost kernel: [12884.470808] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 27 11:54:37 localhost kernel: [12884.472925] i915 0000:00:02.0: setting latency timer to 64
Mar 27 13:07:42 localhost kernel: [17265.136961] Modules linked in: fuse aes_x86_64 cryptd aes_generic coretemp rfcomm bnep ip6t_REJECT ip6t_LOG nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT ipt_LOG xt_limit xt_recent xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables nls_cp437 vfat fat joydev snd_hda_codec_hdmi snd_hda_codec_conexant arc4 uvcvideo videodev v4l2_compat_ioctl32 media iwlagn thinkpad_acpi snd_hda_intel snd_hda_codec mac80211 snd_hwdep snd_pcm nvram snd_page_alloc snd_timer snd iTCO_wdt btusb soundcore rts_pstor(C) bluetooth mei(C) wmi cfg80211 atl1c i2c_i801 serio_raw psmouse rfkill iTCO_vendor_support pcspkr tpm_tis thermal battery tpm tpm_bios evdev ac acpi_cpufreq mperf processor ext4 crc16 jbd2 mbcache usbhid hid sd_mod ahci libahci libata scsi_mod ehci_hcd usbcore i915 video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm i2c_core
Mar 27 20:39:37 localhost kernel: [41052.392955] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 27 20:39:37 localhost kernel: [41052.392969] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 27 20:39:37 localhost kernel: [41052.395084] i915 0000:00:02.0: setting latency timer to 64
Mar 28 09:46:36 localhost kernel: [60281.034170] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 28 09:46:36 localhost kernel: [60281.034184] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 28 09:46:36 localhost kernel: [60281.036271] i915 0000:00:02.0: setting latency timer to 64
Mar 28 13:57:51 localhost kernel: [75063.283483] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 28 13:57:51 localhost kernel: [75063.283507] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 28 13:57:51 localhost kernel: [75063.285919] i915 0000:00:02.0: setting latency timer to 64
Mar 28 22:56:56 localhost kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=<UUID> ro quiet add_efi_memmap resume=/dev/disk/by-uuid/<UUID> pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1
Mar 28 22:56:56 localhost kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=<UUID> ro quiet add_efi_memmap resume=/dev/disk/by-uuid/<UUID> pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1
Mar 28 22:56:56 localhost kernel: [ 3.833207] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar 28 22:56:56 localhost kernel: [ 3.833214] i915 0000:00:02.0: setting latency timer to 64
Mar 28 22:56:56 localhost kernel: [ 3.924413] i915 0000:00:02.0: irq 40 for MSI/MSI-X
Mar 28 22:56:56 localhost kernel: [ 4.710371] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Mar 29 15:51:17 localhost kernel: [17898.288307] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 29 15:51:17 localhost kernel: [17898.288322] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 29 15:51:17 localhost kernel: [17898.290403] i915 0000:00:02.0: setting latency timer to 64
Mar 29 21:58:24 localhost kernel: [37602.220789] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 29 21:58:24 localhost kernel: [37602.220813] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 29 21:58:24 localhost kernel: [37602.223185] i915 0000:00:02.0: setting latency timer to 64
Mar 30 15:13:57 localhost kernel: [51582.920102] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Mar 30 15:13:57 localhost kernel: [51582.920116] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
Mar 30 15:13:57 localhost kernel: [51582.922059] i915 0000:00:02.0: setting latency timer to 64
The only plausible overheating occurred between around 19:30 and 22:30/23:00 on 25 March. And, as I say, I get these problems repeatedly with the mainline kernel when the machine is nowhere near overheating. (The laptop doesn't feel especially hot, the fan isn't especially fast, reported temperatures are typically below 50, with a critical level being 100.)
Last edited by cfr (2012-03-30 16:30:30)

[SOLVED] Audio over HDMI stopped working? (Intel/i915)

My audio over HDMI was working fine until recently and I can't figure out what's stopped it from working... My configs haven't changed and aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav gives no errors, but no sound can be heard. There are no errors/messages in dmesg either.
My graphics card uses the Intel i915 chipset (Asus laptop).
Config stuff:
/etc/asound.conf:
pcm.!default {
type hw
card 0
device 3
ctl.!default {
type hw
card 0
device 3
aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
Any ideas?
Last edited by Minsc (2014-06-19 01:04:29)

Yeah I checked and everything is fine... this is really weird!
I've tested audio over HDMI on windows, so I know it's not the cable/HDMI port. I've looked through my pacman.log (I tend to update daily) and the only thing I can see which could affect it is a kernel update and intel-dri. I tried downgrading those and re-tested, to no avail.
I also installed pulseaudio and pulseaudio-alsa before it stopped working. This could have broken it, but I've since uninstalled them and replaced /etc/asound.conf with my original, so that rules those out; unless there is something else that pulse could have broken?
Cheers
Last edited by Minsc (2013-01-28 07:42:59)

DRM Batch Client Error - ORA03135 connection lost contact

Hi All,
We have the DRM 11g installed on Windows machine and migrated this server recently to a new datacenter(DC1) however the database connected to this DRM server is still on the original datacenter(DC2).
DRM works fine after the migration except for few issues in the nightly jobs scheduled on DRM server for doing exports. The scheduled job is invoking DRM batch client and failing with the following error.
Unexpected error in drm-batch-client: Error received from DRM Process Manager service using address: net.tcp://localhost:5210/Oracle/Drm/ProcessManager/: ORA-03135: connection lost contact
However this error does not occur if we restart the DRM services(thru config console) and rerrun the batch client automatically. Looks like DRM is loosing connectivity to the application server process , is it anything do with the timeouts between IIS and Weblogic server ?
Any insights on this problem would be really helpful.
Thanks,
RB

Hi RB,
This isn't going to be connection between IIS and Weblogic as DRM does not use Weblogic (aside from the manual configuration for the DRM web service). The error that you're getting is being returned from your database server and seems to indicate that the connection to the Oracle database server has been dropped for some reason. There are some suggestions on what to do to try and resolve the ORA-03135 error here ORA-03135 Connection Lost Contact Tips
Regards
Craig

DRM-79819: Encryption error: Config file encryption is not valid for this m

Hi ALL,
Suddenly we got this error while running an export via batch utility. any ideas?
Error: DRM-79819: Encryption error: Config file encryption is not valid for this machine.

This could be an issue with your drm-config.xml file, the file that stores the DRM configuration information defined in the DRM Console. If a drm-config.xml was restored from an old backup or copied from another machine, this could well be the issue.
In this case, you can run the DRM Console to update the file and correct it. You may see a one-time error reported when the DRM Console starts up, but the Console app should correct the file automatically after reporting the error to the user.
If this does not resolve your issue, review the Windows App Event Log, to determine which DRM Server process(es) are also reporting this error (to narrow down any other potential issues with a config file for one of the DRM Server executables). I am guessing this error was observed in just the DRM Batch client, but related Event Log should also be present in the App Event Log.
HTH.
*** An additional note, if your issue proves to be the one above, you may need re-enter passwords on your defined Database Connections for defined DRM Apps. Try just re-running the DRM Console and re-saving the config initially, but be aware this may be a required additional step, re-entering the DB passwords after the updated encryption has been applied to the stored drm-config.xml file.
Edited by: 680314 on Jan 19, 2013 11:52 AM

Error authSwf / authSwf.3329.10600: Internal DRM or DRM server security error

Watching XFINITY on xtv.comcast.net was working fine for the last few days until just recently - when I try to log in it says "adding device" even though they should already be added, and eventually comes up with this error: Error authSwf / authSwf.3329.10600: Internal DRM or DRM server security error I've reinstalled flash player, rebooted my computer, rebooted the DVR, cleared all cache/cookies, you name it. Nothing works. This is in both in the latest versions of Firefox and Chrome. Called XFINITY phone support twice and was told I was being "transferred" then disconnected twice...frustrating.

if you're having the error on Google Chrome, go to settings | then at the bottom click advanced settings | then under privacy click on content settings | scroll down about two thirds down and under protected content click on the allow identifiers box. Milage may vary but worked for me when nothing else would. Before I found this fix, Firefox worked for me so you could try that as well. Just FYI when Comcast says engineers are working on the problem, all that means is that every once in a while a rep comes online and says engineers are working on it. It's been way over a year and the only fix they've ever suggested is reinstall flash. Takes a brilliant engineer to make that suggestion. Hope this helps someone.

DRM Intel Errors

Hi !
From a fresh installation, I got multiple errors during booting process.
I activated mmio_debug=1 as suggested into journalctl logs entries.
This is the log (I got 25 times similar logs during log process)
Appreciate any idea
belette
WARNING: CPU: 3 PID: 226 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug+0x6d/0x80 [i915]()
Nov 17 17:21:35 archfit kernel: [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt
Nov 17 17:21:35 archfit kernel: Unclaimed register detected after reading register 0x650c0
Nov 17 17:21:35 archfit kernel: Modules linked in: snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 nls_cp437 vfat fat iTCO_wdt iTCO_vendor_
Nov 17 17:21:35 archfit kernel: dm_crypt dm_mod sd_mod crc_t10dif crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel at
Nov 17 17:21:35 archfit kernel: CPU: 3 PID: 226 Comm: systemd-udevd Not tainted 3.17.2-1-ARCH #1
Nov 17 17:21:35 archfit kernel: Hardware name: CompuLab Ltd. Intense-PC2 (IPC2)/Intense-PC2 (IPC2), BIOS IPC2_3.330.2 X64 08/29/2014
Nov 17 17:21:35 archfit kernel: 0000000000000000 000000007c6450cc ffff880406237190 ffffffff815367d0
Nov 17 17:21:35 archfit kernel: ffff8804062371d8 ffff8804062371c8 ffffffff8107054d ffff8804068e0000
Nov 17 17:21:35 archfit kernel: 00000000000650c0 0000000000000000 00000000000650c0 ffff8804068e0000
Nov 17 17:21:35 archfit kernel: Call Trace:
Nov 17 17:21:35 archfit kernel: [<ffffffff815367d0>] dump_stack+0x4d/0x6f
Nov 17 17:21:35 archfit kernel: [<ffffffff8107054d>] warn_slowpath_common+0x7d/0xa0
Nov 17 17:21:35 archfit kernel: [<ffffffff810705cc>] warn_slowpath_fmt+0x5c/0x80
Nov 17 17:21:35 archfit kernel: [<ffffffffa04d516d>] hsw_unclaimed_reg_debug+0x6d/0x80 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04d81f3>] gen6_read32+0x93/0x150 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04e7868>] haswell_write_eld+0x78/0x450 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04ed467>] intel_write_eld+0x67/0xa0 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa0506271>] intel_ddi_pre_enable+0x51/0x1f0 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04f0fa4>] haswell_crtc_enable+0x3d4/0xa70 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04bb477>] ? i915_gem_object_ggtt_unpin+0x47/0x90 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04eb5da>] __intel_set_mode+0x87a/0x16d0 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04f3da6>] intel_set_mode+0x16/0x30 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04f4f54>] intel_crtc_set_config+0xaf4/0xef0 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffff8119f7e1>] ? alloc_pages_current+0xb1/0x160
Nov 17 17:21:35 archfit kernel: [<ffffffffa039b324>] drm_mode_set_config_internal+0x64/0xe0 [drm]
Nov 17 17:21:35 archfit kernel: [<ffffffffa03d51a3>] restore_fbdev_mode+0xb3/0xe0 [drm_kms_helper]
Nov 17 17:21:35 archfit kernel: [<ffffffffa03d51f3>] drm_fb_helper_restore_fbdev_mode_unlocked+0x23/0x40 [drm_kms_helper]
Nov 17 17:21:35 archfit kernel: [<ffffffffa03d7418>] drm_fb_helper_set_par+0x28/0x70 [drm_kms_helper]
Nov 17 17:21:35 archfit kernel: [<ffffffffa050008a>] intel_fbdev_set_par+0x1a/0x60 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffff8130b3b8>] fbcon_init+0x578/0x600
Nov 17 17:21:35 archfit kernel: [<ffffffff81383a08>] visual_init+0xb8/0x120
Nov 17 17:21:35 archfit kernel: [<ffffffff81385f26>] do_bind_con_driver+0x176/0x3f0
Nov 17 17:21:35 archfit kernel: [<ffffffff81386744>] do_take_over_console+0xb4/0x1b0
Nov 17 17:21:35 archfit kernel: [<ffffffff8130b4a3>] do_fbcon_takeover+0x63/0xd0
Nov 17 17:21:35 archfit kernel: [<ffffffff8130fb1d>] fbcon_event_notify+0x6cd/0x7d0
Nov 17 17:21:35 archfit kernel: [<ffffffff8108f02d>] notifier_call_chain+0x4d/0x70
Nov 17 17:21:35 archfit kernel: [<ffffffff8108f3f7>] __blocking_notifier_call_chain+0x47/0x60
Nov 17 17:21:35 archfit kernel: [<ffffffff8108f426>] blocking_notifier_call_chain+0x16/0x20
Nov 17 17:21:35 archfit kernel: [<ffffffff81315e6b>] fb_notifier_call_chain+0x1b/0x20
Nov 17 17:21:35 archfit kernel: [<ffffffff8131806e>] register_framebuffer+0x20e/0x360
Nov 17 17:21:35 archfit kernel: [<ffffffffa03d7247>] drm_fb_helper_initial_config+0x377/0x520 [drm_kms_helper]
Nov 17 17:21:35 archfit kernel: [<ffffffffa04d8d18>] ? hsw_write32+0xa8/0x160 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa0500c6f>] intel_fbdev_initial_config+0x1f/0x30 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffffa0526c81>] i915_driver_load+0x1051/0x10b0 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffff8147059b>] ? netlink_broadcast_filtered+0x12b/0x380
Nov 17 17:21:35 archfit kernel: [<ffffffff812ac300>] ? kobj_ns_drop+0x50/0x50
Nov 17 17:21:35 archfit kernel: [<ffffffff812ac638>] ? kobject_uevent_env+0x178/0x540
Nov 17 17:21:35 archfit kernel: [<ffffffff813a7a57>] ? get_device+0x17/0x30
Nov 17 17:21:35 archfit kernel: [<ffffffff813ad7d5>] ? klist_class_dev_get+0x15/0x20
Nov 17 17:21:35 archfit kernel: [<ffffffff8152abf8>] ? klist_node_init+0x38/0x60
Nov 17 17:21:35 archfit kernel: [<ffffffff8152acb6>] ? klist_add_tail+0x46/0x50
Nov 17 17:21:35 archfit kernel: [<ffffffff813a933b>] ? device_add+0x1db/0x6d0
Nov 17 17:21:35 archfit kernel: [<ffffffffa0394fcd>] drm_dev_register+0xad/0x100 [drm]
Nov 17 17:21:35 archfit kernel: [<ffffffffa03978d8>] drm_get_pci_dev+0xd8/0x200 [drm]
Nov 17 17:21:35 archfit kernel: [<ffffffffa049145b>] i915_pci_probe+0x3b/0x60 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffff812e6835>] local_pci_probe+0x45/0xa0
Nov 17 17:21:35 archfit kernel: [<ffffffff812e6785>] ? pci_match_device+0xe5/0x110
Nov 17 17:21:35 archfit kernel: [<ffffffff812e6991>] pci_device_probe+0x101/0x150
Nov 17 17:21:35 archfit kernel: [<ffffffff813ac7f3>] driver_probe_device+0xa3/0x410
Nov 17 17:21:35 archfit kernel: [<ffffffff813acc2b>] __driver_attach+0x8b/0x90
Nov 17 17:21:35 archfit kernel: [<ffffffff813acba0>] ? __device_attach+0x40/0x40
Nov 17 17:21:35 archfit kernel: [<ffffffff813aa613>] bus_for_each_dev+0x73/0xc0
Nov 17 17:21:35 archfit kernel: [<ffffffff813ac27e>] driver_attach+0x1e/0x20
Nov 17 17:21:35 archfit kernel: [<ffffffff813abe60>] bus_add_driver+0x180/0x250
Nov 17 17:21:35 archfit kernel: [<ffffffff813ad4c4>] driver_register+0x64/0xf0
Nov 17 17:21:35 archfit kernel: [<ffffffff812e5f9b>] __pci_register_driver+0x4b/0x50
Nov 17 17:21:35 archfit kernel: [<ffffffffa0397b0a>] drm_pci_init+0x10a/0x140 [drm]
Nov 17 17:21:35 archfit kernel: [<ffffffffa0570000>] ? 0xffffffffa0570000
Nov 17 17:21:35 archfit kernel: [<ffffffffa0570089>] i915_init+0x89/0x90 [i915]
Nov 17 17:21:35 archfit kernel: [<ffffffff81002148>] do_one_initcall+0xd8/0x210
Nov 17 17:21:35 archfit kernel: [<ffffffff811ac176>] ? kfree+0x196/0x1a0
Nov 17 17:21:35 archfit kernel: [<ffffffff811905a2>] ? __vunmap+0xa2/0x100
Nov 17 17:21:35 archfit kernel: [<ffffffff810f222c>] load_module+0x1dcc/0x26a0
Nov 17 17:21:35 archfit kernel: [<ffffffff810ee750>] ? store_uevent+0x70/0x70
Nov 17 17:21:35 archfit kernel: [<ffffffff810f2bcd>] SyS_init_module+0xcd/0x120
Nov 17 17:21:35 archfit kernel: [<ffffffff8153c7a9>] system_call_fastpath+0x16/0x1b
Nov 17 17:21:35 archfit kernel: ---[ end trace 445ee4af8ac4aba4 ]---
Last edited by belette (2014-11-18 18:05:28)

I suspect passing the kernel parameter "nomodeset" would avoid the boot-time errors (worth checking at least for diagnostic purposes). I don't know if this would impact later loading when X starts.
I also had all sorts of intel graphics related issues several weeks ago. Switching from the default 'sna' to 'uxa' acceleration avoided all the errors, but did lead to reduced performance. This reduction, however, was only noticable in a couple very graphics-intensive programs I use (bioacoustic analysis with an 'interactive' multi-layered spectrogram). Luckily for me, 'sna' has worked fine since 3.17. But following some of the history of these issues it seems to affect each bit of hardware differently so it is really hard to compare notes other than suggesting alternative acceleration methods as a potential fix/work-around.

Intel i915, kernel output if lid opened too fast

I have an Intel graphics card, and acpid set up to turn off/on the screen based on the lid events (with vbetool's dpms ability).
At times, if I open the lid too fast, I get this output if I'm on a tty:
[drm:intel_enable_transcoder] *ERROR* failed to enable transcoder 0
I'm not quite sure what to do about it. Other than having the lid open event sleep for 1 second, that seems to have fixed it for now.
Just wanted to see if anyone else experienced this, had any advice, or thought this should be submitted as a bug report.

I have an Intel graphics card, and acpid set up to turn off/on the screen based on the lid events (with vbetool's dpms ability).
At times, if I open the lid too fast, I get this output if I'm on a tty:
[drm:intel_enable_transcoder] *ERROR* failed to enable transcoder 0
I'm not quite sure what to do about it. Other than having the lid open event sleep for 1 second, that seems to have fixed it for now.
Just wanted to see if anyone else experienced this, had any advice, or thought this should be submitted as a bug report.

Error on Intel no error on PPC

I am developing a cocoa core data document program on both a MacBook (intel) and a mac mini (ppc). On the PPC, the project compiles and runs fine, but on the Intel, it compiles fine, but at runtime I get the following error.
2007-05-07 14:54:19.942 myProgram[5361] * -[NSBundle load]: Error loading code /Library/InputManagers/SIMBL/SIMBL.bundle/Contents/MacOS/SIMBL for bundle /Library/InputManagers/SIMBL/SIMBL.bundle, error code 2 (link edit error code 0, error number 0 ())
The error does not prevent it from running. In fact it does not seem to affect the functioning of the program at all. But I would like to know what is causing this error to show up and how to fix it. In case it might be relevant: each of the two projects (PPC and Intel) includes a framework that I wrote (so that my custom view would have a data binding in Interface Builder). The custom view appears to work with both versions.
Any ideas about what could be causing the problem and how to fix it? Thank you in advance.
I am using Xcode 2.4.1.

You have an outdated version of SIMBL that is not Univeral Binary. If you get the latest version or just remove SIMBL, the error should go away.
Developers should be careful with 3rd party system additions.They can introduce errors or hide them.

Intel log errors in Xorg.0.log

My Xorg.0.log is filled every second or so with the following block and it gradually grows larger and larger (ten thousands of lines):
[ 114.832] (II) intel(0): Printing DDC gathered Modelines:
[ 114.832] (II) intel(0): Modeline "1280x800"x0.0 69.32 1280 1292 1356 1416 800 803 806 816 -hsync -vsync (49.0 kHz)
[ 114.867] (II) intel(0): EDID vendor "SEC", prod id 19522
Why is this? Is there some way to stop whatever intel function from doing so? Lately, I have experienced Xorg crashing for unknown reasons, but I don't know if it's related. I have both the intel-dri 7.11-1 package and xf86-video-intel 2.15.0-2 installed.
Any advice would be helpful.
Last edited by roygbiv (2011-09-05 14:12:01)

Thanks, but it didn't change the matter. However, I'm getting more serious log errors:
$ tail /var/log/Xorg.0.log
[ 83.558] (II) intel(0): Modeline "1280x800"x0.0 69.32 1280 1292 1356 1416 800 803 806 816 -hsync -vsync (49.0 kHz)
[ 2513.587] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable
[ 3343.637] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable
[ 5166.039] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 5176.719] (II) Open ACPI successful (/var/run/acpid.socket)
[ 5176.719] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 5176.729] (II) intel(0): EDID vendor "SEC", prod id 19522
[ 5176.729] (II) intel(0): Printing DDC gathered Modelines:
[ 5176.729] (II) intel(0): Modeline "1280x800"x0.0 69.32 1280 1292 1356 1416 800 803 806 816 -hsync -vsync (49.0 kHz)
[ 5176.770] (--) SynPS/2 Synaptics TouchPad: touchpad found
My daemons:
DAEMONS=(syslog-ng dbus netfs ntpd crond acpid wicd alsa laptop-mode !slim)
I have googled this "bad drawable" issue but no solutions are out there. AFAIK this is the reason for my Xorg strange behaviour. Any similar experience, or maybe suggestions to share with me, guys/girls? What logs or configs should I post here?
Last edited by roygbiv (2011-09-05 14:24:01)

Intel RAID error in Device Manager after updating Intel Matrix Storage Console

The latest in my catalogue of problems arose after updating Intel Matrix Storage Console (IMSC) ...
Lost my RAID volume, but both drives were OK. However, IMSC seemed to be freezing, so I thought I'd install the latest version from Intel. Once installed, it gave me errors saying a plug in was not found, followed by messages saying that the SATA and RAID drivers were not installed. Device Manager thinks the drivers are OK, but the yellow triangle with the ! is shown against the Intel RAID driver. Tried un-installing and re-installing the controller, updating the drivers, different versions of IMSC and still get the yellow triangle with the !
I have been having trouble with the RAID0 set up for weeks so wonder if it has finally died? I'm out of ideas. Can anyone help?
This post gives more details of the history and PC configuration: https://forum-en.msi.com/index.php?topic=121960.0

Quote from: NovJoe on 23-March-09, 14:53:31
Why don't you want to follow up with your previous thread?
It'll be confusing when you started multiple threads linking to the issue.
Sorry, I haven't posted here much so I'm not familiar with the protocols. I just thought it would be less confusing to make this a separate issue. I linked them to avoid duplicating info on my config & h/w

Intel driver error

Morning,
First sorry for my english.
My laptop is HP ProBook 4730s.
Yesterday I reinstall my WIN7 (Windows 7 Ultimate x64).
I try to intall the drivers, but when I install the VGA it write an error "This computer does not meet the minimum requirements set for software installation".
I try some intel driver, and reisntall the windows, but the problem is still.
How can I solve the problem?
Thank you for the help.

Hi:
Your notebook probably has the amd/intel switchable graphics and if that is the case you only need to install the amd graphics driver, which installs the drivers for both the amd and Intel gpu's.
If your notebook has that graphics configuration, you cannot and should not try to install the standalone Intel graphics driver.
http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=5060895&sp...

DRM Batch Client error during export

Hello,
I am experiencing an error when using the DRM Batch Client to execute export books. The same export process fails sometimes and runs to completion successfully at other times. When it fails, it does not always fail in the same place within the export process, and the error is as follows:
2/2/2011 8:31:40 PM - ERemotableException with message: "Server was unable to process request. ---> Error during Export. Export was unable to run. Error: Timeout expired" while running Export Book
2/2/2011 8:31:40 PM - => ERROR: Data Relationship Management Server returned error: "Server was unable to process request. ---> Error during Export. Export was unable to run. Error: Timeout expired."
2/2/2011 8:31:40 PM - *** MDMConnect stopping ***
Because this issue is sporadic, it seems like there could be a few possible causes:
1. Network issues
2. SQL connection/time-out issues -- These particular exports are writing to SQL tables versus flat files
3. Am wondering if there are any known issues with the MDMConnect? Or are there time-out settings we can adjust?
We currently have our in-house IT chasing down any possible network or SQL issues. Does anyone know of any issues with the batch client, or have ideas on any other possible causes? Any help is greatly appreciated. Thanks!
EJ

There is a timeout setting in DRM system preferences and there are mulitlple session timeout settings in IIS that you may need to configure. Try the system preference first. For very large jobs, ie. hundreds of thousands of nodes with hundreds of properties per node, you'll need to update settings in IIS as well.

Intel i915 and displayport mst freeze entire kernel

Hi folks,
My lenovo laptop (t440s) came with the Ultra dock that has displayport on the back. I use a displayport cable to connect to a monitor. When I connect to the dock, the monitor works just fine, but if I ever try to "xrandr --output DP2-1 --off" it or disconnect from the dock, the entire kernel hard locks. No response, image on the screen is frozen, and from another computer on the same network I can't ssh or ping.
I put drm.debug=0xf on the boot line, and then repro'd the issue (which repro's every time) and I get the following output right before the crash (see the kernel BUG line)
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_BUSY
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_BUSY
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_MADVISE
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_BUSY
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_BUSY
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_MADVISE
Mar 18 12:13:54 nevada kernel: [drm:drm_ioctl] pid=587, dev=0xe200, auth=1, I915_GEM_THROTTLE
Mar 18 12:13:54 nevada kernel: [drm:intel_hpd_irq_handler] hotplug event received, stat 0x00400000, dig 0x00101210
Mar 18 12:13:54 nevada kernel: [drm:intel_hpd_irq_handler] digital hpd port C - long
Mar 18 12:13:54 nevada kernel: [drm:intel_hpd_irq_handler] Received HPD interrupt on PIN 5 - cnt: 1
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_hpd_pulse] got hpd irq on port C - long
Mar 18 12:13:54 nevada kernel: [drm:intel_hpd_irq_handler] hotplug event received, stat 0x00400000, dig 0x00101210
Mar 18 12:13:54 nevada kernel: [drm:intel_hpd_irq_handler] digital hpd port C - long
Mar 18 12:13:54 nevada kernel: [drm:intel_hpd_irq_handler] Received HPD interrupt on PIN 5 - cnt: 2
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_get_dpcd] DPCD: 12 14 c4 01 00 15 01 83 02 00 00 00 00 00 04
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_get_dpcd] Displayport TPS3 supported
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_probe_oui] Sink OUI: 000000
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_probe_oui] Branch OUI: 90cc24
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_probe_mst] Sink is MST capable
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_hpd_pulse] got hpd irq on port C - long
Mar 18 12:13:54 nevada kernel: [drm:intel_dp_hpd_pulse] MST device may have disappeared 1 vs 1
Mar 18 12:13:54 nevada kernel: BUG: unable to handle kernel NULL pointer dereference at 000000000000004c
There are no other lines after that kernel NULL pointer dereference at 0x4c
I can attach or paste the full dmesg somewhere else if anyone is interested, but I'm confused by the second to last line there, MST device may have disappeared 1 vs 1. From the code (linux-stable at tag v3.18.6):
From drivers/gpu/drm/i915/intel_dp.c:
4559 mst_fail:
4560 /* if we were in MST mode, and device is not there get out of MST mode */
4561 if (intel_dp->is_mst) {
4562 DRM_DEBUG_KMS("MST device may have disappeared %d vs %d\n", intel_dp->is_mst, intel_dp->mst_mgr.mst_state);
4563 intel_dp->is_mst = false;
4564 drm_dp_mst_topology_mgr_set_mst(&intel_dp->mst_mgr, intel_dp->is_mst);
4565 }
4566 put_power:
4567 intel_display_power_put(dev_priv, power_domain);
4568
4569 return ret;
4570 }
So it's locking up either in drm_dp_mst_topology_mgr_set_mst (which doesn't have any debug messages in it in the main path, and does capture a lock) or it's locking up in intel_display_power_put, which ALSO doesn't have debug output. They both acquire mutex's.. looking into this some more. If anyone has seen this issue with displayport, mst, and linux 3.18.6 please let me know

Ok, writing a patch with debug messages to see where this is exactly locking up hopefully...
From 05a0a4758a98f47305165befa81eb61154e15676 Mon Sep 17 00:00:00 2001
From: Jeff Mickey <[email protected]>
Date: Wed, 18 Mar 2015 14:00:28 -0700
Subject: [PATCH] Debugging statements for figuring out this dp mst bug
Signed-off-by: Jeff Mickey <[email protected]>
drivers/gpu/drm/drm_dp_mst_topology.c | 27 ++++++++++++++++++++++-----
drivers/gpu/drm/i915/intel_dp.c | 8 ++++++++
drivers/gpu/drm/i915/intel_pm.c | 3 +++
3 files changed, 33 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c
index f50d884..b0ff4be 100644
--- a/drivers/gpu/drm/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/drm_dp_mst_topology.c
@@ -1827,13 +1827,16 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
int ret = 0;
struct drm_dp_mst_branch *mstb = NULL;
+ DRM_DEBUG_KMS("locking mgr->lock\n");
mutex_lock(&mgr->lock);
- if (mst_state == mgr->mst_state)
+ if (mst_state == mgr->mst_state) {
+ DRM_DEBUG_KMS("goto out_unlock 1\n");
goto out_unlock;
+ }
mgr->mst_state = mst_state;
/* set the device into MST mode */
if (mst_state) {
+ DRM_DEBUG_KMS("inside mst_state\n");
WARN_ON(mgr->mst_primary);
/* get dpcd info */
@@ -1849,9 +1852,11 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
mgr->avail_slots = mgr->total_slots;
/* add initial branch device at LCT 1 */
+ DRM_DEBUG_KMS("calling drm_dp_add_mst_branch_device\n");
mstb = drm_dp_add_mst_branch_device(1, NULL);
if (mstb == NULL) {
ret = -ENOMEM;
+ DRM_DEBUG_KMS("goto out_unlock 2\n");
goto out_unlock;
mstb->mgr = mgr;
@@ -1864,29 +1869,35 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
struct drm_dp_payload reset_pay;
reset_pay.start_slot = 0;
reset_pay.num_slots = 0x3f;
+ DRM_DEBUG_KMS("drm_dp_dpcd_write_payload\n");
drm_dp_dpcd_write_payload(mgr, 0, &reset_pay);
+ DRM_DEBUG_KMS("drm_dp_dpcd_writeb\n");
ret = drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL,
DP_MST_EN | DP_UP_REQ_EN | DP_UPSTREAM_IS_SRC);
if (ret < 0) {
+ DRM_DEBUG_KMS("goto out_unlock 3\n");
goto out_unlock;
/* sort out guid */
+ DRM_DEBUG_KMS("drm_dp_dpcd_read\n");
ret = drm_dp_dpcd_read(mgr->aux, DP_GUID, mgr->guid, 16);
if (ret != 16) {
DRM_DEBUG_KMS("failed to read DP GUID %d\n", ret);
goto out_unlock;
+ DRM_DEBUG_KMS("drm_dp_validate_guid\n");
mgr->guid_valid = drm_dp_validate_guid(mgr, mgr->guid);
if (!mgr->guid_valid) {
+ DRM_DEBUG_KMS("drm_dp_dpcd_write 2\n");
ret = drm_dp_dpcd_write(mgr->aux, DP_GUID, mgr->guid, 16);
mgr->guid_valid = true;
+ DRM_DEBUG_KMS("queue_work\n");
queue_work(system_long_wq, &mgr->work);
ret = 0;
@@ -1895,6 +1906,7 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
mstb = mgr->mst_primary;
mgr->mst_primary = NULL;
/* this can fail if the device is gone */
+ DRM_DEBUG_KMS("drm_dp_dpcd_writeb 2\n");
drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
ret = 0;
memset(mgr->payloads, 0, mgr->max_payloads * sizeof(struct drm_dp_payload));
@@ -1904,11 +1916,16 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
out_unlock:
+ DRM_DEBUG_KMS("unlocking mgr->lock\n");
mutex_unlock(&mgr->lock);
- if (mstb)
+ if (mstb) {
+ DRM_DEBUG_KMS("drm_dp_put_mst_branch_device 2\n");
drm_dp_put_mst_branch_device(mstb);
- return ret;
+ }
+
+ DRM_DEBUG_KMS("returning %d\n", ret);
+ return ret;
EXPORT_SYMBOL(drm_dp_mst_topology_mgr_set_mst);
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 4bcd917..5a3c562 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -4523,24 +4523,29 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd)
if (HAS_PCH_SPLIT(dev)) {
if (!ibx_digital_port_connected(dev_priv, intel_dig_port))
+ DRM_DEBUG_KMS("goto mst_fail 1\n");
goto mst_fail;
} else {
if (g4x_digital_port_connected(dev, intel_dig_port) != 1)
+ DRM_DEBUG_KMS("goto mst_fail 2\n");
goto mst_fail;
if (!intel_dp_get_dpcd(intel_dp)) {
+ DRM_DEBUG_KMS("goto mst_fail 3\n");
goto mst_fail;
intel_dp_probe_oui(intel_dp);
if (!intel_dp_probe_mst(intel_dp))
+ DRM_DEBUG_KMS("goto mst_fail 4\n");
goto mst_fail;
} else {
if (intel_dp->is_mst) {
if (intel_dp_check_mst_status(intel_dp) == -EINVAL)
+ DRM_DEBUG_KMS("goto mst_fail 5\n");
goto mst_fail;
@@ -4549,6 +4554,7 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd)
* we'll check the link status via the normal hot plug path later -
* but for short hpds we should check it now
+ DRM_DEBUG_KMS("drm_modeset_lock\n");
drm_modeset_lock(&dev->mode_config.connection_mutex, NULL);
intel_dp_check_link_status(intel_dp);
drm_modeset_unlock(&dev->mode_config.connection_mutex);
@@ -4566,6 +4572,8 @@ mst_fail:
put_power:
intel_display_power_put(dev_priv, power_domain);
+ DRM_DEBUG_KMS("Returning %d as ret\n", ret);
+
return ret;
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
index 83c7ecf..c5e6f33 100644
--- a/drivers/gpu/drm/i915/intel_pm.c
+++ b/drivers/gpu/drm/i915/intel_pm.c
@@ -6555,6 +6555,7 @@ void intel_display_power_put(struct drm_i915_private *dev_priv,
power_domains = &dev_priv->power_domains;
+ DRM_DEBUG_KMS("locking power_domains->lock\n");
mutex_lock(&power_domains->lock);
WARN_ON(!power_domains->domain_use_count[domain]);
@@ -6570,8 +6571,10 @@ void intel_display_power_put(struct drm_i915_private *dev_priv,
+ DRM_DEBUG_KMS("unlocking power_domains->lock\n");
mutex_unlock(&power_domains->lock);
+ DRM_DEBUG_KMS("intel_runtime_pm_put is being called\n");
intel_runtime_pm_put(dev_priv);
2.3.3

DRM Intel i915 errors

Similar Messages

Maybe you are looking for