CUDA error: Illegal address in cuCtxSyncronize() #43780

Closed
opened 2015-02-22 18:39:46 +01:00 by Giuseppe De Marco · 9 comments

System Information
Debian jessie 8 and Ubuntu 14.04 with a GTX690

Blender Version
2.73a hash bbf09d9

Linux maker 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 GNU/Linux

same fault on Ubuntu 14.04, same blender version.

I'm running the rendering, avoiding this fault, decreasing materials dinamics ( noise, voronoi, too many nodes with high scales and details ) and increasing world streight ( global illumination ).

I'm using CuDA on a GTX690, using all its kepler (x2) core.
The same video card is used for Xorg.

Is there any experience avoiding this faults, decoupling cuda card from xorg ?
Example, I could use an intel for Xorg and let the Cuda works on a dedicated card.

If needed I can upload the faulty blend for tests.

**System Information** Debian jessie 8 and Ubuntu 14.04 with a GTX690 **Blender Version** 2.73a hash bbf09d9 Linux maker 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 GNU/Linux same fault on Ubuntu 14.04, same blender version. I'm running the rendering, avoiding this fault, decreasing materials dinamics ( noise, voronoi, too many nodes with high scales and details ) and increasing world streight ( global illumination ). I'm using CuDA on a GTX690, using all its kepler (x2) core. The same video card is used for Xorg. Is there any experience avoiding this faults, decoupling cuda card from xorg ? Example, I could use an intel for Xorg and let the Cuda works on a dedicated card. If needed I can upload the faulty blend for tests.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @demarcog83

Added subscriber: @demarcog83
Member

Added subscriber: @MartijnBerger

Added subscriber: @MartijnBerger
Member

The same video card is used for Xorg. <--- most likely cause is that your are running out of vram.

run nvidia_smi and see how close you get to running out

The same video card is used for Xorg. <--- most likely cause is that your are running out of vram. run nvidia_smi and see how close you get to running out

Added subscriber: @Sergey

Added subscriber: @Sergey

Two possibilities here:

  • Either your scene is too complex to be rendered o nthe display GPU (because CUDA sets a time limit on how long you can run the kernel)
  • Or you're running out of VRAM.

In any case, having full logs from the terminal would help. And as was mentioned above, check how much physical VRAM is being allocated (it'll be more than blender reports because of the fragmentation and memory used by the kernel itself).

Two possibilities here: - Either your scene is too complex to be rendered o nthe display GPU (because CUDA sets a time limit on how long you can run the kernel) - Or you're running out of VRAM. In any case, having full logs from the terminal would help. And as was mentioned above, check how much physical VRAM is being allocated (it'll be more than blender reports because of the fragmentation and memory used by the kernel itself).

Yes, you're right
I moved monitor plug and xorg to the intel card, then I configured mesa glx with

update-alternatives --config glx 

this permits me to leave nvidia glx support inside the system without purge it and breaking drivers and cuda dependencies.
Now I'm rendering my animation without any problems, GPU video card is now completely dedicated to rendering/HPC and all is calm on western side.

thank you guys

Yes, you're right I moved monitor plug and xorg to the intel card, then I configured mesa glx with ``` update-alternatives --config glx ``` this permits me to leave nvidia glx support inside the system without purge it and breaking drivers and cuda dependencies. Now I'm rendering my animation without any problems, GPU video card is now completely dedicated to rendering/HPC and all is calm on western side. thank you guys

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2015-03-05 11:00:23 +01:00

Time to close then. :)

Time to close then. :)
Sign in to join this conversation.
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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#43780
No description provided.