Blender + AMD Ryzen 7 5700U on Linux occasionally crashing Blender and compositor #96408
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#96408
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Guix w/ Linux 5.16.11 (mostly upstream, via nonguix channel)
Graphics card: AMD Ryzen 7 5700U with Radeon Graphics
Blender Version
Broken: 3.0.1
Worked: (unknown)
Blender on Ryzen 5700U occasionally crashes Blender and the desktop compositor (if using an accelerated one like Gnome Shell... it also happens on XFCE, but less often). This happens most often, I think, when either switching to or opening a file with the viewport set to the camera (eg numpad 0).
The errors spit out to dmesg are:
After which, a bunch of messages like:
will appear in dmesg or at the STTY, if eg pressing ctrl-alt-f1.
I'm guessing it's something to do with code associated with rendering from the camera view but not other views.
Exact steps for others to reproduce the error
Two paths:
if that doesn't crash it the first time, try a few more times!
OR
Repeat if necessary!
I have also commented on this Linux kernel thread, which seems related: https://bugzilla.kernel.org/show_bug.cgi?id=205089#c34
Added subscriber: @ChristopherWebber
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Archived'
As mentioned in the bugzilla thread, a GPU reset happened and the kernel recovered, but neither Blender or your compositor could handle the GPU reset, so you get the latter error message.
But regardless, GPU resets are outside of the scope of Blender development, this should be handled in the trackers of the kernel or your user space driver, which is probably Mesa. You could attach an API trace for them to be able to replicate the issue without needing to install Blender.
HI,
Thank you @OmarSquircleArt. This issue is closed now, so maybe you won't see me asking this, but what could I do to produce such an API trace? I don't know where to begin.
I did find some issues in Mesa that seem relevant, btw:
@ChristopherWebber You can use this tool (http://apitrace.github.io/) to record a number of frames where the issue happens, then attach that file to the interested developers to replay it on their end. It is not clear if it will be helpful to them, but it will at least save them the time of installing Blender.