<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [drm] GPU HANG: ecode 6:0:0x85fffff8"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=104388">104388</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[drm] GPU HANG: ecode 6:0:0x85fffff8
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DRI
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>DRM/Intel
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>fabrice@bellet.info
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Created <span class=""><a href="attachment.cgi?id=136392" name="attach_136392" title="error file">attachment 136392</a> <a href="attachment.cgi?id=136392&action=edit" title="error file">[details]</a></span>
error file

On a thinkpad X220, with a Intel HD Graphics 3000, running a stock version of
Fedora 27 x86_64, and using Xorg instead of Wayland, I can trigger a GPU hang
pretty easily running FlightGear, the flight simulator, when the windows has a
particular size.

The /sys/class/drm/card0/error is attached to this bug.

I tested with Mesa-17.2.2 (packaged in Fedora 27), and also with a custom built
of Mesa-17.3.1, with the same problem.

Here is how to reproduce the bug, for example from a Fedora 27 live Workstation
USB stick (with a Fedora 27 installed on disk, you can skip directly to the dnf
install commands):

- make sure that gdm will use Xorg instead of Wayland :
# rpm -e xorg-x11-server-Xwayland gnome-session-wayland-session --nodeps
- logout liveuser and login again
- verify that Xorg is running.
- free some space on / (the live USB stick may not have enough free space to
hold the 2.5GB of FlightGear scenery data), for example by removing some *big*
packages:
# rpm -qa | grep libreoffice| xargs rpm -e gnome-documents unoconv
# rpm -qa | grep adobe-source | xargs rpm -e
# rpm -qa | egrep '(qemu|libvirt)' | xargs rpm -e gnome-boxes
# rpm -e glibc-all-langpacks java-1.8.0-openjdk-headless
gnome-getting-started-docs  javapackages-tools
# rpm -e  gnome-user-docs fedora-workstation-backgrounds
# rpm -e foomatic-db-ppds cldr-emoji-annotation libpinyin-data
evolution-langpacks evolution ibus-libpinyin foomatic-db  evolution-ews
evolution-help libpinyin foomatic ibus-typing-booster evolution-ews-langpacks
libzhuyin  ibus-libzhuyin
# rpm -e firefox
# rpm -e iwl7260-firmware webkitgtk4-plugin-process-gtk2 qt-x11 unicode-ucd
libkkc-data  dbusmenu-qt sni-qt adwaita-qt4 ibus-qt libkkc  ibus-kkc
- install FlightGear and wmctrl
# dnf install FlightGear wmctrl
- start it using these startup parameters:
$ fgfs --airport=LKPR --aircraft=mibs --timeofday=afternoon --season=summer
--disable-real-weather-fetch --prop:/sim/rendering/multi-sample-buffers=true
--prop:/sim/rendering/multi-samples=2 --disable-rembrandt --enable-freeze
--disable-terrasync --glideslope=6.0 --offset-distance=5 --on-ground=false
--disable-auto-coordination --metar="XXXX 012345Z 15003KT 19SM FEW072 FEW350
25/07 Q1028 NOSIG"
- from another terminal window, resize the FlightGear window to size 1024x717,
and verify with xwininfo that the window has the expected size (if the window
is sticked below the menu top bar in GNOME, it won't resize properly, the bug
also happens if the window is partially offscreen):
$ wmctrl -r FlightGear -e 0,200,200,1024,717
- unfreeze the simulator by hitting the "P" key
- move up the view a dozen times, by hitting the "down arrow" key, you should
see sparse clouds in the sky
- move the "left" or "right" arrow key to rotate the view of the sky.
- the GPU should freeze pretty quickly in this situation (<30seconds)

The window height seems to be an important condition to trigger this crash.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are on the CC list for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>