[Bug 88805] New: MinnowBoard MAX DRM hang on linux-next 3.19-rc5 2015-02-26

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 26 09:51:58 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=88805

            Bug ID: 88805
           Summary: MinnowBoard MAX DRM hang on linux-next 3.19-rc5
                    2015-02-26
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: dvhart at linux.intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 112836
  --> https://bugs.freedesktop.org/attachment.cgi?id=112836&action=edit
MinnowBoard MAX linux-next 3.19-rc5 2015-01-26 dmesg drm.debug=0x7

Olof Johanson originally reported his MinnowBoard MAX hung using linux-next
3.19-rc5+, I reproduced this using linux-next from 2015-01-26. His dmesg is
here:

http://arm-soc.lixom.net/bootlogs/next/next-20150123/minnowmax-x86-minnowmax_defconfig.html

My dmesg is attached, the final drm messages leading to the hang follow:

...
[    1.673003] [drm] Initialized drm 1.1.0 20060810
[    1.679809] [drm] Memory usable by graphics device = 2048M
[    1.685985] [drm] Replacing VGA console driver
[    1.693153] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.700581] [drm] Driver supports precise vblank timestamp query.
[    1.736168] vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    1.988096] [drm] failed to retrieve link info, disabling eDP

This was bisected to:

commit fc72355f5c04c40f2916a07e9f8d4b357e2e0a93
Author:     Mika Kuoppala <mika.kuoppala at linux.intel.com>
AuthorDate: Mon Jan 19 16:20:43 2015 +0200
Commit:     Daniel Vetter <daniel.vetter at ffwll.ch>
CommitDate: Tue Jan 20 12:36:57 2015 +0100

    drm/i915: Consolidate forcewake code

Which appears to be related to the patch Jani V created to resolve a similar
issue for this board:

commit 05adaf1f101f25f40f12c29403e6488f0e45f6b6
Author: Jani Nikula <jani.nikula at intel.com>
Date:   Fri May 9 14:52:34 2014 +0300

    drm/i915/vlv: reset VLV media force wake request register

Jani confirms:
"""
That's the fix all right.
However there's

[    2.032075] [drm] failed to retrieve link info, disabling eDP

in the logs suggesting the minnowmax tries to initialize eDP which it
doesn't have. That's a VBT problem in itself, but since

commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date:   Fri Jan 9 14:21:14 2015 +0200

    drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

we don't register HDMI if there's an eDP in the same port...

Potentially two problems I think.
"""

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150126/72bac153/attachment.html>


More information about the intel-gfx-bugs mailing list