Blender/System Freeze. Cycles on "Viewport Shading/Render" when Compute Device is NOT the display device. #44094
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#44094
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
Debian Testing. Kernel 3.19.4/4.0.0rc2
2×GPU (GTX 580/750ti)
nvidia version 346.47
2×Multiple display setup 1 monitor for each GPU.
Blender Version
2.72.b+dfsg0-3 (debian)
2.73a (official)
2.74 RC2 (official)
Short description of error
System/Compute Device/CUDA allows for selecting any or multiple supported devices.
This works fine for rendering and there appears to be no problems as multiple GPU's are utilized for rendering purposes.
However, if Viewport Shading/Render is selected and the CUDA device(s) is not the main display or multiple devices that contains a device that is not the main display device - blender will crash.
I've tested this loading blender to display from either GPU and render to the non-display GPU with no problems unless "Viewport Shading/Render" is selected then blender will freeze (without errors) and at times a system freeze (if display != :0 and I can't kill blender).
Let me know if you require any further information.
Regards.
Joules.
Exact steps for others to reproduce the error
Any simple cycles render test.
Changed status to: 'Open'
Added subscriber: @joules-2
Added subscriber: @Sergey
I'm using mutliple videocards here on debian, and blender institute uses such a setups as well, so it'll be likely some specific setup..
Some questions:
No SLI.
Just to make it a little more concise (and it also doesn't freeze down my entire system).
GTX 580 is connected to a display.
GTX 750ti is disconnected from a display.
The following scenarios is consistent.
Blender: Works as expected.
Compute Device/CUDA/Geforce GTX 580 + 750 Ti
Render/Device/GPU Compute
(Render) F12.
Note:
When Compute Device/CUDA/Geforce GTX 580 is set (display GPU).
Viewport Shading:Render+Cycles Render [Shift+z] also works as expected.
Blender: Fails - Blender Freezes. (KILL required)
Compute Device/CUDA/Geforce GTX 580 + 750 Ti OR Geforce GTX 750 Ti
Render/Device/GPU Compute
Viewport Shading:Render+Cycles Render [Shift+z]
Note: The opposite is also True (750Ti connected to a display 580 not).
Let me know if you require anything else.
Heres a screenshot of the freeze screen. This is with the 750Ti as the display GPU for this monitor and the 580 disconnected from any display or xscreen. I took this while testing if the opposite situation also caused a freeze (so it can't be specific to any GPU).
Regards.
Changed status from 'Open' to: 'Resolved'
I can confirmed that disabling Vt-d (Intel ® VT for Direct I/O) within the bios resolves this bug for this particular system (Dell T7500).
Regards,
Joules.
That's an interesting observation. We could now investigate it deeper once we've got access to such hardware :)
Thanks for the information and happy blending!
Added subscriber: @edekbul
Hi,
I have similar or the same problem. I have two cards, GTX 660Ti(screen attached) and GTX 780Ti. View port is working only with 660Ti selected, any combination with 780Ti results in freeze. I have new Gigabyte GA-990FXA-UD5 motherboard and i have IOMMU setting on (same as Intel ® VTbut for AMD?). It is impossible to turn off IOMMU because all usb devices stop working with this option disabled (http://ubuntuforums.org/showthread.php?t=2143433&page=2). I need this option enabled for Xen also, so I would prefer to find workaround...
UPDATE
It turns out that it is possible to make:"GRUB_CMDLINE_LINUX="iommu=soft" in grub, and leave IOMMU option ON in Bios!. Now everything works well, USB ports, cycles, both cards in all configurations!!!:)
..."
sudo nano /etc/default/grub
input your password
then find the line that says: GRUB_CMDLINE_LINUX=""
then make it this: GRUB_CMDLINE_LINUX="iommu=soft"
save the file
then run this in the terminal:
sudo update-grub
"...
Can you confirm that this issue does not present itself when IOMMU is disabled in the BIOS?
When IOMMU is disabled in the BIOS my USB ports doesent work , including mouse and keyboard. I was not able to check if viewport work with IOMMU disabled. Now i have "GRUB_CMDLINE_LINUX="iommu=soft" and IOMMU enabled in bios and everything works well.
With "GRUB_CMDLINE_LINUX="iommu=soft" set and IOMMU turned off in BIOS, viewport rendering is working fine. The only scenario when viewport rendering is not working is when you dont set "GRUB_CMDLINE_LINUX="iommu=soft" and HAVE IOMMU turned in BIOS ON.