Cycles GPU render crashes when using Subsurface Scattering shader #80283

New Issue

Aron Bergman · 2020-08-31T16:26:15+02:00

Aron Bergman commented

2020-08-31 16:26:15 +02:00

System Information
Operating system: (Linux Mint 19.3) Linux-5.4.0-42-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: AMD Radeon RX 5700 XT (NAVI10, DRM 3.38.0, 5.4.0-42-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-30 21:49, hash: 429afe0c62
Also confirmed not to work with 2.83.5
Worked: (newest version of Blender that worked as expected)

Short description of error
Rendering with Cycles GPU makes the computer "halt", i.e. the screen freezes (though mouse movement works) and I can't switch to a login terminal (CTRL+ALT+F[1,2,3,...]).
Seems to be caused by the Subsurface Scattering shader, see logs.
When rendering, it says "Loading render kernels" and after a while it switches to "Compiling render kernels". After a couple moments, the computer stops responding.
Works fine with Cycles CPU.

Exact steps for others to reproduce the error
Delete the Cycles cache (~/.cache/cycles). (This may not be necessary, but I've always done this before testing)
Create a fresh project and select the cube.
Go to the Shader tab, delete the default Principled BSDF shader.
Add a Subsurface Scattering shader (and connect it to the Material Output).
Switch from Eevees to Cycles GPU.
Press F12 to render.

system-info.txt

These logs were generated by running ./blender > <file>.log 2>&1
The default.log is the output of rendering the default cube. bug.log is produced by following the above steps.

default.log

bug.log

**System Information** Operating system: (Linux Mint 19.3) Linux-5.4.0-42-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: AMD Radeon RX 5700 XT (NAVI10, DRM 3.38.0, 5.4.0-42-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-30 21:49, hash: `429afe0c62` Also confirmed not to work with 2.83.5 Worked: (newest version of Blender that worked as expected) **Short description of error** Rendering with Cycles GPU makes the computer "halt", i.e. the screen freezes (though mouse movement works) and I can't switch to a login terminal (CTRL+ALT+F[1,2,3,...]). Seems to be caused by the Subsurface Scattering shader, see logs. When rendering, it says "Loading render kernels" and after a while it switches to "Compiling render kernels". After a couple moments, the computer stops responding. Works fine with Cycles CPU. **Exact steps for others to reproduce the error** Delete the Cycles cache (~/.cache/cycles). (This may not be necessary, but I've always done this before testing) Create a fresh project and select the cube. Go to the Shader tab, delete the default Principled BSDF shader. Add a Subsurface Scattering shader (and connect it to the Material Output). Switch from Eevees to Cycles GPU. Press F12 to render. [system-info.txt](https://archive.blender.org/developer/F8825730/system-info.txt) These logs were generated by running `./blender > <file>.log 2>&1` The `default.log` is the output of rendering the default cube. `bug.log` is produced by following the above steps. [default.log](https://archive.blender.org/developer/F8825729/default.log) [bug.log](https://archive.blender.org/developer/F8825728/bug.log)

Aron Bergman commented

2020-08-31 16:26:15 +02:00

Added subscriber: @weerox

gabe2252 commented

2020-08-31 20:16:27 +02:00

Added subscriber: @gabe2252

Aron Bergman commented

2020-09-02 13:01:58 +02:00

I've been generating some more log files using ./blender -b <args> <file> -f 1 > <logfile> 2>&1.

<file> is the path to either of these files, where bug.blend is generated by following the steps to reproduce the error as stated in the description. default.blend is the default cube with rendering set to Cycles GPU.
bug.blend

default.blend

<args> can be 4 different things.

Nothing
--log "*" --log-level -1
--debug
--debug-all

Here are the log files that was generated.
bug.1.log

I will compare these logs and see if I can find anything that seems relevant.

I've been generating some more log files using `./blender -b <args> <file> -f 1 > <logfile> 2>&1`. `<file>` is the path to either of these files, where `bug.blend` is generated by following the steps to reproduce the error as stated in the description. `default.blend` is the default cube with rendering set to Cycles GPU. [bug.blend](https://archive.blender.org/developer/F8832609/bug.blend) [default.blend](https://archive.blender.org/developer/F8832610/default.blend) `<args>` can be 4 different things. - Nothing - `--log "*" --log-level -1` - `--debug` - `--debug-all` Here are the log files that was generated. [bug.1.log](https://archive.blender.org/developer/F8832639/bug.1.log) [bug.2.log](https://archive.blender.org/developer/F8832640/bug.2.log) [bug.3.log](https://archive.blender.org/developer/F8832641/bug.3.log) [bug.4.log](https://archive.blender.org/developer/F8832642/bug.4.log) [default.1.log](https://archive.blender.org/developer/F8832646/default.1.log) [default.2.log](https://archive.blender.org/developer/F8832648/default.2.log) [default.3.log](https://archive.blender.org/developer/F8832647/default.3.log) [default.4.log](https://archive.blender.org/developer/F8832649/default.4.log) I will compare these logs and see if I can find anything that seems relevant.

Aron Bergman commented

2020-09-02 14:14:43 +02:00

After looking through the log files the only thing that stands out is that rendering stops at tile 74/510 in all 4 logs.

To figure out which tile it was that caused the problem I changed the Tile Order to Left to Right and rendered bug.blend again. I expected it to crash on another tile this time, but it didn't, it froze on tile 74/510 again and the 74th tile (using Left to Right order) just contains the background.

I did some more experiments and managed to get into a terminal (CTRL+ALT+F[1,2,3,...]) after Blender crashed but before the computer froze completely. When trying to log in, the kernel sent out messages about amdgpu page faults, so this is probably a driver problem and not a problem with Blender. Though I still think it is peculiar that it stops at tile 74 irregardless of tile order.

After looking through the log files the only thing that stands out is that rendering stops at tile 74/510 in all 4 logs. To figure out which tile it was that caused the problem I changed the Tile Order to Left to Right and rendered `bug.blend` again. I expected it to crash on another tile this time, but it didn't, it froze on tile 74/510 again and the 74th tile (using Left to Right order) just contains the background. I did some more experiments and managed to get into a terminal (CTRL+ALT+F[1,2,3,...]) after Blender crashed but before the computer froze completely. When trying to log in, the kernel sent out messages about `amdgpu` page faults, so this is probably a driver problem and not a problem with Blender. Though I still think it is peculiar that it stops at tile 74 irregardless of tile order.

Aron Bergman commented

2020-09-02 14:41:31 +02:00

Here is the kern.log output concerning amdgpu, if anyone is interested.
amdgpu.log

Here is the `kern.log` output concerning `amdgpu`, if anyone is interested. [amdgpu.log](https://archive.blender.org/developer/F8833125/amdgpu.log)

Aron Bergman commented

2020-09-02 19:11:45 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Aron Bergman closed this issue

2020-09-02 19:11:45 +02:00

Aron Bergman self-assigned this 2020-09-02 19:11:45 +02:00

Aron Bergman commented

2020-09-02 19:11:46 +02:00

Yes, this was a driver problem, downgraded from amdgpu-pro 20.30 to amdgpu-pro 20.10 and now it works great!

Yes, this was a driver problem, downgraded from `amdgpu-pro 20.30` to `amdgpu-pro 20.10` and now it works great!

gabe2252 commented

2020-09-02 23:00:36 +02:00

Sweet! Can you test if this bug is present on that driver? https://developer.blender.org/T79724 It seems to be another 5700xt driver issue.

Aron Bergman commented

2020-09-03 10:16:43 +02:00

In #80283#1007881, @gabe2252 wrote:
Sweet! Can you test if this bug is present on that driver? https://developer.blender.org/T79724 It seems to be another 5700xt driver issue.

Woops, that freezes my computer too, using the older version of the driver...

> In #80283#1007881, @gabe2252 wrote: > Sweet! Can you test if this bug is present on that driver? https://developer.blender.org/T79724 It seems to be another 5700xt driver issue. Woops, that freezes my computer too, using the older version of the driver...

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles GPU render crashes when using Subsurface Scattering shader #80283