HIP related bugs #109431

New Issue

YimingWu · 2023-06-28T04:47:19+02:00

YimingWu commented

2023-06-28 04:47:19 +02:00

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:

Open

#111685 5700xt 22.20.27.09.230330 hangs (not sure if this is real crash yet)
#112608 6950 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.3-300.fc39.x86_64) crash without backtrace, Fedora Linux 39

Closed

~~#100353 Cycles HIP rendered viewport crashes system/GPU on Linux with RDNA2 GPU~~
~~#109417 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.~~
~~#109562 libamdhip64.so library location/install issue~~
~~#111546 Crash on 23.8.1 with Radeon RX 6800XT~~
~~#111569 Crash on 23.7.2.230718~~
~~#112177 "Instant crash on high polygon", User pref erroneously shows two identical AMD cards instead of one.~~
~~#110392 Crash on driver AMD Adrenaline 23.7.1 and 23.7.2 but fine on AMD Adrenaline 23.5.2.~~
~~#109553 "Out of memory" when HIP is on but fine when off.~~
~~#109415 Geometry appears to be tearing up~~
~~#110459 Crashes~~
~~#112163 HIP binary kernel not found~~
~~#109811 Linux crash with HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid.~~
~~#111019 HIP and HIPRT Support for GFX1037 (AMD Radeon 610M iGPU)~~
~~#110777 AMD Radeon Pro W6800 not detected~~

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: ## Open - #111685 5700xt `22.20.27.09.230330` hangs (not sure if this is real crash yet) - #112608 6950 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.3-300.fc39.x86_64) crash without backtrace, Fedora Linux 39 ## Closed - ~~#100353 Cycles HIP rendered viewport crashes system/GPU on Linux with RDNA2 GPU~~ - ~~#109417 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.~~ - ~~#109562 libamdhip64.so library location/install issue~~ - ~~#111546 Crash on `23.8.1` with `Radeon RX 6800XT`~~ - ~~#111569 Crash on `23.7.2.230718`~~ - ~~#112177 "Instant crash on high polygon", User pref erroneously shows two identical AMD cards instead of one.~~ - ~~#110392 Crash on driver `AMD Adrenaline 23.7.1` and `23.7.2` but fine on `AMD Adrenaline 23.5.2`.~~ - ~~#109553 "Out of memory" when HIP is on but fine when off.~~ - ~~#109415 Geometry appears to be tearing up~~ - ~~#110459 Crashes~~ - ~~#112163 HIP binary kernel not found~~ - ~~#109811 Linux crash with `HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid.`~~ - ~~#111019 HIP and HIPRT Support for GFX1037 (AMD Radeon 610M iGPU)~~ - ~~#110777 AMD Radeon Pro W6800 not detected~~

👍 3

YimingWu added this to the 3.6 LTS milestone 2023-06-28 04:47:19 +02:00

YimingWu added the

Status

Needs Info from Developers

labels 2023-06-28 04:47:20 +02:00

YimingWu added this to the Render & Cycles project 2023-06-28 04:47:22 +02:00

Pratik Borhade commented

2023-06-28 06:08:14 +02:00

cc @BrianSavery

Pratik Borhade referenced this issue

2023-06-29 07:18:17 +02:00

Blender 3.6 crash with RT enable #109477

Pratik Borhade referenced this issue

2023-07-04 06:56:09 +02:00

Issue with Cycles Rendering Mode - Unexpected Blender Closure #109668

Brian Savery (AMD) commented

2023-07-06 05:39:38 +02:00

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.

👍 1

YimingWu referenced this issue

2023-07-24 06:00:36 +02:00

Cycles HIP device crash on rendering on latest AMD Adrenaline Driver #110392

Pratik Borhade referenced this issue

2023-08-29 12:09:02 +02:00

Entering rendered view crashes blender #111569

Cyril commented

2023-09-06 21:00:52 +02:00

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

YimingWu commented

2023-09-07 05:40:38 +02:00

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.

Brecht Van Lommel commented

2023-09-07 12:29:29 +02:00

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

Cyril referenced this issue

2023-09-07 15:01:49 +02:00

Crash during render with AMD HIP on Linux #112084

Cyril commented

2023-09-07 15:02:57 +02:00