HIP related bugs #109431

New Issue

There are multiple bug reports following the release of 3.6 on the stability and the consistency of HIP, combine them here for easier access:

#109415 Geometry appears to be tearing up
#109417 #110459 Crashes
#109418 #109421 Material appears to be white
#109477 #110841 crash with RT enable
#109521 HIP binary kemel for this graphics card compute capability (9.0) not found.
#109553 "Out of memory" when HIP is on but fine when off.
- ~~#110126 Under-reporting memory usage on windows+AMD, could be the same cause as the above one.~~ Mis-categrization, This one does not have HIP enabled.
#109562 libamdhip64.so library location/install issue
#109811 Linux crash with HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid.
#110392 #111198 Crash on driver AMD Adrenaline 23.7.1 and 23.7.2 but fine on AMD Adrenaline 23.5.2.
#111546 Crash on 23.8.1 with Radeon RX 6800XT
#111569 Crash on 23.7.2.230718
#111685 5700xt 22.20.27.09.230330 hangs (not sure if this is real crash yet)
#112177 "Instant crash on high polygon", User pref erroneously shows two identical AMD cards instead of one.
#112608 6950 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.3-300.fc39.x86_64) crash without backtrace, Fedora Linux 39

There are multiple bug reports following the release of 3.6 on the stability and the consistency of HIP, combine them here for easier access: - #109415 Geometry appears to be tearing up - #109417 #110459 Crashes - #109418 #109421 Material appears to be white - #109477 #110841 crash with RT enable - #109521 HIP binary kemel for this graphics card compute capability (9.0) not found. - #109553 "Out of memory" when HIP is on but fine when off. - ~~#110126 Under-reporting memory usage on windows+AMD, could be the same cause as the above one.~~ Mis-categrization, This one does not have HIP enabled. - #109562 libamdhip64.so library location/install issue - #109811 Linux crash with `HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid.` - #110392 #111198 Crash on driver `AMD Adrenaline 23.7.1` and `23.7.2` but fine on `AMD Adrenaline 23.5.2`. - #111546 Crash on `23.8.1` with `Radeon RX 6800XT` - #111569 Crash on `23.7.2.230718` - #111685 5700xt `22.20.27.09.230330` hangs (not sure if this is real crash yet) - #112177 "Instant crash on high polygon", User pref erroneously shows two identical AMD cards instead of one. - #112608 6950 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.3-300.fc39.x86_64) crash without backtrace, Fedora Linux 39

cc @BrianSavery

Thanks. We're also looking at the linux viewport issue. The one thing I'll mention is that a few of the reports mention using 23.5 driver. For Windows with HIPRT users should stick to https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-40-51-06-blender-3-6-beta as mentioned in the release notes.

Hello. I'm not sure if I should have created a new issue or found an existing one that appears to have the same problem I encountered: crash during Cycles rendering with AMD HIP. I use Linux Mint 20.2, Linux kernel 6.2.0-3, GPU Radeon RX 6600, Blender 3.6.3 Release Candidate

When running from terminal, an error message appears before crash "Memory access fault by GPU node-1 (Agent handle: 0x7feed4dc1000) on address 0x7fed00007000. Reason: Page not present or supervisor privilege.".

The problem occurred only with one .blend file. I tried a couple of others and rendering works without issues. The problem file is Blender 3.2 splash screen. After cleaning up the scene, I narrowed down the cause. The crash happen when there are two objects in the scene, one having Cast Shadow Caustics (located in Object Properties > Shading > Caustics) enabled and another having Receive Shadow Caustics enabled, and a light source with Shadow Caustics enabled (located in Object Data Properties > Light). The objects must be in the camera view.

There is one thing that I have not been able to figure out. When experimenting with the splash screen scene, there is no crash if only the object with Cast Shadow Caustics enabled (water) is visible in the camera, but crashes when object with Receive Shadow Caustics enabled (ship) is visible. But when I experimented with the default Blender scene, by duplicating the cube and setting those parameters, Blender crashed independently of which of the objects is visible in the camera, even if only the cube with Cast Shadow Caustics is visible, which does not cause a crash in the splash screen scene.

I uploaded both scenes. In order to reduce size I replaced the boat mesh in the cleaned up splash screen scene with a cube (I replaced it in the Edit mode to preserve other parameters).

Hello. I'm not sure if I should have created a new issue or found an existing one that appears to have the same problem I encountered: crash during Cycles rendering with AMD HIP. I use Linux Mint 20.2, Linux kernel 6.2.0-3, GPU Radeon RX 6600, Blender 3.6.3 Release Candidate When running from terminal, an error message appears before crash "Memory access fault by GPU node-1 (Agent handle: 0x7feed4dc1000) on address 0x7fed00007000. Reason: Page not present or supervisor privilege.". The problem occurred only with one .blend file. I tried a couple of others and rendering works without issues. The problem file is [Blender 3.2 splash screen](https://cloud.blender.org/p/gallery/629f23f908e12d4ff15241d3). After cleaning up the scene, I narrowed down the cause. The crash happen when there are two objects in the scene, one having Cast Shadow Caustics (located in Object Properties > Shading > Caustics) enabled and another having Receive Shadow Caustics enabled, and a light source with Shadow Caustics enabled (located in Object Data Properties > Light). The objects must be in the camera view. There is one thing that I have not been able to figure out. When experimenting with the splash screen scene, there is no crash if only the object with Cast Shadow Caustics enabled (water) is visible in the camera, but crashes when object with Receive Shadow Caustics enabled (ship) is visible. But when I experimented with the default Blender scene, by duplicating the cube and setting those parameters, Blender crashed independently of which of the objects is visible in the camera, even if only the cube with Cast Shadow Caustics is visible, which does not cause a crash in the splash screen scene. I uploaded both scenes. In order to reduce size I replaced the boat mesh in the cleaned up splash screen scene with a cube (I replaced it in the Edit mode to preserve other parameters).

Blender-3.2-Splash-Screen.blend

108 KiB

default.blend

905 KiB

there is no crash if only the object with Cast Shadow Caustics enabled (water) is visible in the camera, but crashes when object with Receive Shadow Caustics enabled (ship) is visible.

This is a useful piece of information. Also thanks for the test file!

@BrianSavery @Sayak-Biswas or maybe @brecht may want to take a look.

> there is no crash if only the object with Cast Shadow Caustics enabled (water) is visible in the camera, but crashes when object with Receive Shadow Caustics enabled (ship) is visible. This is a useful piece of information. Also thanks for the test file! @BrianSavery @Sayak-Biswas or maybe @brecht may want to take a look.

Please create a new issue, let's not use this one to go into specific bugs.

Please create a new issue, let's not use this one to go into specific bugs.

#112084

> Please create a new issue, let's not use this one to go into specific bugs. #112084

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

HIP related bugs #109431