[Bug 72351] New: [GM45] oops in iowrite32 after long hibernation

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Mon Mar 17 13:52:41 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=72351

            Bug ID: 72351
           Summary: [GM45] oops in iowrite32 after long hibernation
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.10.0-rc7
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jhyeon at gmail.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 129791
  --> https://bugzilla.kernel.org/attachment.cgi?id=129791&action=edit
Kernel oops in syslog

I am experiencing a regression that reveals itself after resume from a long
hibernation.  The symptom is that the X11 display freezes after the kernel
emits an oops.

This seems to depend on the video chipset.  A paging request failure occurs on
Thinkpad X200 Tablet with the Intel GM45 chipset whereas there is no problem on
Thinkpad X220 Tablet with Intel HD Graphics 3000.

This problem does not occur if the hibernation is short.  I can reproduce the
error reliably if the hibernation lasts for several hours.

I use the compositing window manager, compiz 0.8.8.

Since this problem depends on the kernel version, I performed a bisection.  The
first bad commit is:

commit 17fec8a08698bcab98788e1e89f5b8e7502ababd
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Jul 4 00:23:33 2013 +0100

    drm/i915: Use Graphics Base of Stolen Memory on all gen3+

    So I made the mistake of missing that the desktop and mobile chipsets
    have different layouts in their PCI configurations, and we were
    incorrectly setting the wrong physical address for stolen memory on
    mobile chipsets.

    Since all gen3+ are actually consistent in the location of the GBSM
    register in the PCI configuration space on device 2 (the GPU), use it.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Daniel Vetter <daniel.vetter at ffwll.ch>
    [danvet: Drop cc: stable and fudge conflicts.]
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>


Let me attach: kernel oops in syslog, Xorg.0.log, bisection log

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list