Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • intel intel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 860
    • Issues 860
    • List
    • Boards
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • drm
  • intelintel
  • Issues
  • #2176
Closed (moved) (moved)
Open
Issue created Jul 14, 2020 by Euan de Kock@euan

Blender hangs gnome session

I am experiencing the same issue as the bug reported here: #2097 (closed).

When running blender, it will freeze the display after a short period of working. The actual steps to recreate it don't appear to follow an exact pattern, but it will generally freeze after a few minutes of activity. When it is frozen, the mouse still moves, but no action can be initiated. Although the screen continues to show the blender screen, the program has actually crashed and is no longer running.

My only resolution is to switch to a console (ctrl-alt-F3) and kill everything to force a new login session.

It has only recently started, and I suspect it was an upgraded driver. I have tried running blender 2.81 and 2.83 and the latest 2.83.2 build. The earlier version used to work perfectly (including the 2.81 version I tested above).

I have run blender under both XOrg and Wayland, and have booted into a few older kernels too I get the error with all of them.

My current machine is a fairly recent Huawei MateBook X. running Fedora 32. I have the NVidia drivers installed, but the modules are not loaded in memory at all during this activity, and haven't been since a fresh power cycle.

uname -m: x86_64 uname -r: 5.7.8-200.fc32.x86_64

DMIDecode for the Motherboard:

Base Board Information Manufacturer: HUAWEI Product Name: MACH-WX9-PCB Version: M17 Serial Number: BB8310193B000618 Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0

Contents of the /sys/class/drm/card0/error are attached: error.bz2

The system log reports this:

[ 449.015366] i915 0000:00:02.0: Resetting rcs0 for preemption time out [ 449.015404] i915 0000:00:02.0: blender[4298] context reset due to GPU hang [ 449.085902] i915 0000:00:02.0: GPU HANG: ecode 9:1:85df9ffd, in blender [4298] [ 449.085903] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 449.085903] Please file a new bug report at https://gitlab.freedesktop.org/drm/intel/issues/new. [ 449.085904] Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details. [ 449.085904] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 449.085904] The GPU crash dump is required to analyze GPU hangs, so please always attach it. [ 449.085905] GPU crash dump saved to /sys/class/drm/card0/error

Second attachment is a video showing the screen behaviour after the crash. The animation is sensitive to mouse and keyboard activity

VID_20200714_202113

Many Thanks,

Euan de Kock. Perth, WA, Australia.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking