Bug 93564 - Display perturbated on Intel(R) 945GME
Summary: Display perturbated on Intel(R) 945GME
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-03 01:01 UTC by bruno
Modified: 2017-03-16 13:12 UTC (History)
1 user (show)

See Also:
i915 platform: I945GM
i915 features: GPU hang


Attachments
compressed /sys/class/drm/card0/error (67.08 KB, text/plain)
2016-01-03 01:01 UTC, bruno
no flags Details

Description bruno 2016-01-03 01:01:16 UTC
Created attachment 120770 [details]
compressed /sys/class/drm/card0/error

On my HP mini laptop (1 GB RAM - 4 GB swap), running Mageia 5:

[    49.872] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20150327
[    49.918] (--) intel(0): Integrated Graphics Chipset: Intel(R) 945GME

when loading multiple apps (LibreOffice + firefox in KDE), I have memory used most completely and a bit of swap. In these conditions, I get lines on the screen appearing in the menu bar of LibreOffice, or completely on the screen preventing me from seeing anything. While looking for a log, I found these indications in dmesg which invited me to create that BR:

[  191.704121] [drm] stuck on render ring
[  191.710428] [drm] GPU HANG: ecode 3:0:0x7fffffc1, in X [1755], reason: Ring hung, action: reset
[  191.710436] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  191.710440] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  191.710443] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  191.710447] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  191.710450] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  192.052208] drm/i915: Resetting chip after gpu hang
[  198.704082] [drm] stuck on render ring
[  198.710463] [drm] GPU HANG: ecode 3:0:0x7fffffc1, in X [1755], reason: Ring hung, action: reset
[  198.766905] [drm:i915_gem_reset [i915]] *ERROR* gpu hanging too fast, banning!
[  198.767070] drm/i915: Resetting chip after gpu hang

Kernel 4.1.13-desktop-2.mga5
lspci:
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
        Subsystem: Hewlett-Packard Company Device 308f
        Flags: bus master, fast devsel, latency 0
        Memory at fe880000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 2
xrandr --verbose
Screen 0: minimum 8 x 8, current 1024 x 600, maximum 32767 x 32767
LVDS1 connected primary 1024x600+0+0 (0x46) normal (normal left inverted right x axis y axis) 222mm x 125mm
        Identifier: 0x42
        Timestamp:  47995
        Subpixel:   horizontal rgb
        Gamma:      1.0:1.0:1.0
        Brightness: 1.0
        Clones:    
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
        EDID: 
                00ffffffffffff002264e903a6570400
                2f13010380160d780a8c85975b538e27
                18505400000001010101010101010101
                0101010101012c150030415850205d23
                9508de7d00000019000000fe00000000
                00000000000000000000000000fc0048
                5344313031504657320a202000000010
                000a20202020202020202020202000d8
        BACKLIGHT: 10 
                range: (0, 10)
        Backlight: 10 
                range: (0, 10)
        scaling mode: Full aspect 
                supported: None, Full, Center, Full aspect
  1024x600 (0x46) 54.200MHz -HSync -VSync *current +preferred
        h: width  1024 start 1117 end 1152 total 1328 skew    0 clock  40.81KHz
        v: height  600 start  641 end  646 total  680           clock  60.02Hz
  800x600 (0x8f) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  640x480 (0x90) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
VGA1 disconnected (normal left inverted right x axis y axis)
        Identifier: 0x43
        Timestamp:  47995
        Subpixel:   unknown
        Clones:    
        CRTCs:      1 0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
        Identifier: 0x44
        Timestamp:  47995
        Subpixel:   no subpixels
        Clones:    
        CRTCs:      2
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 

Killing the apps taking memory render the display usable again
Comment 1 Chris Wilson 2016-01-03 09:58:11 UTC
This is bug 90841. As a quick test, http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ should be disabling the suspect code paths for you,

commit 2788914ea67fa01b869571f0db61bed2ec964ca2
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Dec 30 21:46:37 2015 +0000

    sna: Disable WC mmaps for 945 and older
Comment 2 yann 2017-03-16 13:11:49 UTC
(In reply to Chris Wilson from comment #1)
> This is bug 90841. As a quick test,
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ should be
> disabling the suspect code paths for you,
> 
> commit 2788914ea67fa01b869571f0db61bed2ec964ca2
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Wed Dec 30 21:46:37 2015 +0000
> 
>     sna: Disable WC mmaps for 945 and older

Timeout, so assuming this is fixed by now.

If this issue still occurs, please update your system to latest kernel, then re-test and confirm this is still the case before reporting the issue (Attach as well kernel log and gpu crash dump)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.