Reliable GPU hang on common Intel cards (Linux) #80458

New Issue

Patrice · 2020-09-04T09:12:23+02:00

Patrice commented

2020-09-04 09:12:23 +02:00

System Information
Operating system: Linux Fedora 32
Graphics card: UHD Graphics 620 (rev 07) Intel

Blender Version
Broken: 2.80.x, 2.90.0-x

Short description of error

Blender crashes the computer, freezing, dmesg command shows a GPU Hang error.

Exact steps for others to reproduce the error

Only with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here)

Open the given blend file F8892221 (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs.

I followed the dmesg output that says to create an issue on freedesktop gitlab: https://gitlab.freedesktop.org/drm/intel/-/issues/2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender.

The problem started from 2.80 if I'm not wrong, not with others earlier versions.

**System Information** Operating system: Linux Fedora 32 Graphics card: UHD Graphics 620 (rev 07) Intel **Blender Version** Broken: 2.80.x, 2.90.0-x **Short description of error** Blender crashes the computer, freezing, dmesg command shows a GPU Hang error. **Exact steps for others to reproduce the error** Only with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here) Open the given blend file [F8892221](https://archive.blender.org/developer/F8892221/gpuhangtest.blend) (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs. I followed the dmesg output that says to create an issue on freedesktop gitlab: https://gitlab.freedesktop.org/drm/intel/-/issues/2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender. The problem started from 2.80 if I'm not wrong, not with others earlier versions.

Patrice commented

2020-09-04 09:12:23 +02:00

Added subscriber: @Metal3d

blender-admin commented

2020-09-04 09:12:23 +02:00

#87229 was marked as duplicate of this issue

blender-admin commented

2020-09-04 09:12:23 +02:00

#76529 was marked as duplicate of this issue

blender-admin commented

2020-09-04 09:12:23 +02:00

#79330 was marked as duplicate of this issue

blender-admin commented

2020-09-04 09:12:23 +02:00

#77466 was marked as duplicate of this issue

blender-admin commented

2020-09-04 09:12:23 +02:00

#77923 was marked as duplicate of this issue

Henrik D. commented

2020-09-17 14:51:22 +02:00

Added subscriber: @HDMaster84

Henrik D. commented

2020-09-17 14:51:22 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Henrik D. commented

2020-09-17 14:51:22 +02:00

Can you test if this file causes a hang for you? (just activate lookdev or rendered view)
gpuhangtest.blend

For me it reliably hangs my laptop. More info:

System Information
Operating system: Linux-5.8.0-1-amd64-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.1.7

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-17 11:33, hash: 393b5a231f

Can you test if this file causes a hang for you? (just activate lookdev or rendered view) [gpuhangtest.blend](https://archive.blender.org/developer/F8892221/gpuhangtest.blend) For me it reliably hangs my laptop. More info: **System Information** Operating system: Linux-5.8.0-1-amd64-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.1.7 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-17 11:33, hash: `393b5a231f`

Patrice commented

2020-09-18 08:15:20 +02:00

Hi, sorry for the delay

Yes it crashes my laptop also. I didn't tried with my own build, I only try with official build at this time.

Hi, sorry for the delay Yes it crashes my laptop also. I didn't tried with my own build, I only try with official build at this time.

Patrice commented

2020-09-18 08:19:42 +02:00

And it also crash with my own build (blender 2.90 and blender 2.91-alpha) - I will edit the report so.
Thanks for the axample blend file !

And it also crash with my own build (blender 2.90 and blender 2.91-alpha) - I will edit the report so. Thanks for the axample blend file !

Patrice changed title from ~~Official binary on Fedora 32 makes GPU hang~~ to Fedora 32 makes GPU hang

2020-09-18 08:24:52 +02:00

Henrik D. commented

2020-09-18 10:10:57 +02:00

Changed status from 'Needs User Info' to: 'Confirmed'

Henrik D. commented

2020-09-18 10:10:57 +02:00

Ok so I can confirm that this is a valid issue not just with my system. It's also not special to the common UHD Graphics 620, because I had other Intel cards hanging as well in the same way (I will provide Information about them when I get a chance to do it). No problems with Nvidia though.

What I dont know yet is if it is related to EEVEE or if it will also happen in normal viewport shading mode. I have a feeling it does also happen with only viewport shading but more rare and less controllable.

EDIT: It totally does crash with viewport shading if you just enter xray mode in the test file I provided. But you need to increase the array count to about 10000 first.

Ok so I can confirm that this is a valid issue not just with my system. It's also not special to the common UHD Graphics 620, because I had other Intel cards hanging as well in the same way (I will provide Information about them when I get a chance to do it). No problems with Nvidia though. What I dont know yet is if it is related to EEVEE or if it will also happen in normal viewport shading mode. I have a feeling it does also happen with only viewport shading but more rare and less controllable. **EDIT:** It totally does crash with viewport shading if you just enter xray mode in the test file I provided. But you need to increase the array count to about 10000 first.

Henrik D. commented

2020-09-18 10:20:01 +02:00

btw did you mean to write 2.83.5 instead of 2.85?

Also a better title would now be something like "Reliable GPU hang on common Intel cards (Linux)"

btw did you mean to write 2.83.5 instead of 2.85? Also a better title would now be something like "Reliable GPU hang on common Intel cards (Linux)"

Philipp Oeser commented

2020-09-18 10:31:11 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-09-18 10:31:11 +02:00

Got no issues with Material Preview not XRay

**System Information**
Operating system: Linux-5.8.4-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66
version: 2.91.0 Alpha, branch: master (modified), commit date: 2020-09-18 08:12, hash: `rB9a52b30cc0de`

In Rendered Viewport Shading mode, I can confirm a crash (at least in a Debug build), even without the Array modifier on the plane:

GPUShader: Compilation Log :  : FragShader
      | 
 3935 |   node_bsdf_principled_dielectric(unf4, unf5, unf6, unf7, unf8, unf9, unf10, unf11, unf12, unf13, unf14, unf15, unf16, unf17, unf18, unf19, unf20, unf21, unf22, unf23, tmp1, tmp2, cons26, viewposition, cons28, cons29, tmp3, tmp31);
      | 
      | Error:  C0107: Too many arguments to macro node_bsdf_principled_dielectric
      | Error:  C1035: assignment of incompatible types

./bin/blender(BLI_system_backtrace+0x26) [0xb8533b6]
./bin/blender(_BLI_assert_print_backtrace+0x16) [0xb73f11d]
./bin/blender(EEVEE_material_get+0x13a) [0x39c7591]
./bin/blender(EEVEE_volumes_cache_init+0x179) [0x39cf75a]
./bin/blender() [0x39ad63f]
./bin/blender() [0x3993d13]
./bin/blender(DRW_draw_render_loop_ex+0x2be) [0x3995207]
./bin/blender(DRW_draw_view+0x173) [0x3994eed]
./bin/blender() [0x44571ce]
./bin/blender(view3d_main_region_draw+0x43) [0x4457275]
./bin/blender(ED_region_do_draw+0x171) [0x3dd5bdf]
./bin/blender() [0x36b691b]
./bin/blender() [0x36b6ecf]
./bin/blender(wm_draw_update+0xc5) [0x36b74f0]
./bin/blender(WM_main+0x48) [0x36b3f8b]
./bin/blender() [0x326c63e]

Got no issues with Material Preview not XRay ``` **System Information** Operating system: Linux-5.8.4-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66 version: 2.91.0 Alpha, branch: master (modified), commit date: 2020-09-18 08:12, hash: `rB9a52b30cc0de` ``` In Rendered Viewport Shading mode, I can confirm a crash (at least in a Debug build), even without the Array modifier on the plane: ``` GPUShader: Compilation Log : : FragShader | 3935 | node_bsdf_principled_dielectric(unf4, unf5, unf6, unf7, unf8, unf9, unf10, unf11, unf12, unf13, unf14, unf15, unf16, unf17, unf18, unf19, unf20, unf21, unf22, unf23, tmp1, tmp2, cons26, viewposition, cons28, cons29, tmp3, tmp31); | | Error: C0107: Too many arguments to macro node_bsdf_principled_dielectric | Error: C1035: assignment of incompatible types ./bin/blender(BLI_system_backtrace+0x26) [0xb8533b6] ./bin/blender(_BLI_assert_print_backtrace+0x16) [0xb73f11d] ./bin/blender(EEVEE_material_get+0x13a) [0x39c7591] ./bin/blender(EEVEE_volumes_cache_init+0x179) [0x39cf75a] ./bin/blender() [0x39ad63f] ./bin/blender() [0x3993d13] ./bin/blender(DRW_draw_render_loop_ex+0x2be) [0x3995207] ./bin/blender(DRW_draw_view+0x173) [0x3994eed] ./bin/blender() [0x44571ce] ./bin/blender(view3d_main_region_draw+0x43) [0x4457275] ./bin/blender(ED_region_do_draw+0x171) [0x3dd5bdf] ./bin/blender() [0x36b691b] ./bin/blender() [0x36b6ecf] ./bin/blender(wm_draw_update+0xc5) [0x36b74f0] ./bin/blender(WM_main+0x48) [0x36b3f8b] ./bin/blender() [0x326c63e] ```

Philipp Oeser changed title from ~~Fedora 32 makes GPU hang~~ to GPU freeze/crash [Too many arguments to macro node_bsdf_principled_dielectric]

2020-09-18 10:32:54 +02:00

Philipp Oeser commented

2020-09-18 10:40:55 +02:00

Ah, that shader compilation error is because of b248ec9776 [so that doesnt really have to do with the hang/freeze I guess, because b248ec9776 is a very recent commit from yesterday].

So my assumption is that is has to with the Intel cards

Ah, that shader compilation error is because of b248ec9776 [so that doesnt really have to do with the hang/freeze I guess, because b248ec9776 is a very recent commit from yesterday]. So my assumption is that is has to with the Intel cards

Philipp Oeser changed title from ~~GPU freeze/crash [Too many arguments to macro node_bsdf_principled_dielectric]~~ to GPU freeze/crash

2020-09-18 10:41:10 +02:00

Jeroen Bakker commented

2020-09-18 11:50:15 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2020-09-18 11:50:15 +02:00

This issue should be fixed by 940ef1a4e8

This issue should be fixed by 940ef1a4e8

Henrik D. commented

2020-09-18 11:52:47 +02:00

I tried the file on one more system and it did also hang in exactly the same way (hang is the correct term).
It also had KDE just like my first system (may or may not be related?).

System Information
Operating system: Linux-5.7.0-3-amd64-x86_64-with-glibc2.29 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) Intel Open Source Technology Center 3.3 (Core Profile) Mesa 20.1.7

Blender Version
Broken: version: 2.83.5 (official debian version)

I tried the file on one more system and it did also hang in exactly the same way (hang is the correct term). It also had KDE just like my first system (may or may not be related?). **System Information** Operating system: Linux-5.7.0-3-amd64-x86_64-with-glibc2.29 64 Bits Graphics card: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) Intel Open Source Technology Center 3.3 (Core Profile) Mesa 20.1.7 **Blender Version** Broken: version: 2.83.5 (official debian version)

Henrik D. commented

2020-09-18 12:03:49 +02:00

In #80458#1018312, @lichtwerk wrote:
In Rendered Viewport Shading mode, I can confirm a crash (at least in a Debug build), even without the Array modifier on the plane:

In #80458#1018354, @Jeroen-Bakker wrote:
This issue should be fixed by 940ef1a4e8

To be clear the issue from that comment was fixed, not the issue of this bug report.

> In #80458#1018312, @lichtwerk wrote: > In Rendered Viewport Shading mode, I can confirm a crash (at least in a Debug build), even without the Array modifier on the plane: > In #80458#1018354, @Jeroen-Bakker wrote: > This issue should be fixed by 940ef1a4e8 To be clear the issue from that comment was fixed, not the issue of this bug report.

Jeroen Bakker commented

2020-09-18 12:10:54 +02:00

Yes your right, the mentioned commit does not fix this issue.

Henrik D. commented

2020-09-18 12:44:35 +02:00

The issue seems to be Linux specific. I tested it on Windows on following system and it didn't hang the system (although it froze blender in some instances and I had to stop it from the Task Manager, which is fine though)

System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.6999

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29

The issue seems to be Linux specific. I tested it on Windows on following system and it didn't hang the system (although it froze blender in some instances and I had to stop it from the Task Manager, which is fine though) **System Information** Operating system: Windows-10-10.0.17763-SP0 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.6999 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29`

Patrice commented

2020-09-19 10:01:41 +02:00

In #80458#1018285, @HDMaster84 wrote:
Ok so I can confirm that this is a valid issue not just with my system. It's also not special to the common UHD Graphics 620, because I had other Intel cards hanging as well in the same way (I will provide Information about them when I get a chance to do it). No problems with Nvidia though.

I have got crashes and glitches on viewport when I do some animations...

Note that I don't have the previous message from dmesg output since several days (maybe an update that fixes something), that you can see here https://gitlab.freedesktop.org/drm/intel/-/issues/2422 - now, I have got a kernel error (I can see it going to a TTY to check)

Note: to avoid rebooting, on a TTY, sudo init 3 then return to the TTY and sudo init 5 to restart DM... losing done work, but faster to be back on my desktop manager...

> In #80458#1018285, @HDMaster84 wrote: > Ok so I can confirm that this is a valid issue not just with my system. It's also not special to the common UHD Graphics 620, because I had other Intel cards hanging as well in the same way (I will provide Information about them when I get a chance to do it). No problems with Nvidia though. I have got crashes and glitches on viewport when I do some animations... Note that I don't have the previous message from `dmesg` output since several days (maybe an update that fixes something), that you can see here https://gitlab.freedesktop.org/drm/intel/-/issues/2422 - now, I have got a kernel error (I can see it going to a TTY to check) Note: to avoid rebooting, on a TTY, `sudo init 3` then return to the TTY and `sudo init 5` to restart DM... losing done work, but faster to be back on my desktop manager...

Patrice commented

2020-09-19 10:12:54 +02:00

Checking the https://gitlab.freedesktop.org/drm/intel/-/issues/2380#note_611887 comment, it seems that someone found a shader line that is the starting point of the crash.

It seems (I didn't checked yet) that the commit

https://developer.blender.org/rBd712f1f83af881be536ec0d183b7d3025c172684
is where it starts to fail.

So https://developer.blender.org/rBd0ff3434cffa2e056e4f191ead21226f32ea8c15 is the "good one" to work.

Checking the https://gitlab.freedesktop.org/drm/intel/-/issues/2380#note_611887 comment, it seems that someone found a shader line that is the starting point of the crash. It seems (I didn't checked yet) that the commit https://developer.blender.org/rBd712f1f83af881be536ec0d183b7d3025c172684 is where it starts to fail. So https://developer.blender.org/rBd0ff3434cffa2e056e4f191ead21226f32ea8c15 is the "good one" to work.

Henrik D. commented

2020-09-19 11:01:40 +02:00

First of all, thanks for the sudo init trick. I also get a different message in dmesg, might be the update to kernel version 5.8.0. The problem is unchanged though.
I am currently checking the good commit.

First of all, thanks for the `sudo init` trick. I also get a different message in dmesg, might be the update to kernel version 5.8.0. The problem is unchanged though. I am currently checking the good commit.

Henrik D. commented

2020-09-19 11:53:30 +02:00

It's kind of hard to check that commit since it is so old and all the libraries are updated, so it wont compile. A revert seems like a lot of work. I will move on to other things for now.
Also I wanted to mention #77466 here. This is not strictly a duplicate since this is about viewport and eevee while that one is about cycles, but the problem seems really similar.

It's kind of hard to check that commit since it is so old and all the libraries are updated, so it wont compile. A revert seems like a lot of work. I will move on to other things for now. Also I wanted to mention #77466 here. This is not strictly a duplicate since this is about viewport and eevee while that one is about cycles, but the problem seems really similar.

Henrik D. commented

2020-09-19 14:07:55 +02:00

I tested 2.80 though and it still had the same issue with this particular file, so the file might lead to a slighly different problem, than the regular random crashes.

Patrice commented

2020-09-20 01:12:06 +02:00

I also have 5.8.8-200.fc32.x86_64 kernel version, didn't tried older version for a while but you might be right, maybe I'm wrong saying that it works with them. I will download 2.80 version and check again.

It can also be a problem with mesa or intel drivers... as I mentionned my bug report to freedesktop, that can be an issue from something outside Blender, even if it's the only one who crashes the system (for example, Blender is using something that is not used by others softwares).

See https://gitlab.freedesktop.org/drm/intel/-/issues/2380 where a lot of comments seems to speak about the same problem.

I also have 5.8.8-200.fc32.x86_64 kernel version, didn't tried older version for a while but you might be right, maybe I'm wrong saying that it works with them. I will download 2.80 version and check again. It can also be a problem with mesa or intel drivers... as I mentionned my bug report to freedesktop, that can be an issue from something outside Blender, even if it's the only one who crashes the system (for example, Blender is using something that is not used by others softwares). See https://gitlab.freedesktop.org/drm/intel/-/issues/2380 where a lot of comments seems to speak about the same problem.

Patrice commented

2020-09-20 01:25:38 +02:00

OK... tried with 2.80rc3... same problem. I see the texture rendeting and then GPU hangs. It's a bit better (2.90 crashes without any texture preview), but still crashes.

So, that should mean that intel drivers or mesa has a problem... Or... Blender is using something that only crashes on that GPU for any reason.

Also reported here: https://gitlab.freedesktop.org/drm/intel/-/issues/2192

So we're not alone... And unfortunately it seems that we will not be able to use Blender for a while on our laptops...

OK... tried with 2.80rc3... same problem. I see the texture rendeting and then GPU hangs. It's a bit better (2.90 crashes without any texture preview), but still crashes. So, that should mean that intel drivers or mesa has a problem... Or... Blender is using something that only crashes on that GPU for any reason. Also reported here: https://gitlab.freedesktop.org/drm/intel/-/issues/2192 So we're not alone... And unfortunately it seems that we will not be able to use Blender for a while on our laptops...

Patrice commented

2020-09-20 01:29:54 +02:00

#80073 seems to report the same problem

Patrice changed title from ~~GPU freeze/crash~~ to Reliable GPU hang on common Intel cards (Linux)

2020-09-20 08:15:56 +02:00

Patrice commented

2020-09-20 21:54:30 +02:00

OK, I tried something to be sure.

I've installed Pantheon desktop sudo dnf install "pantheon desktop" and tried to open F8892221 .blend file. It's very slow, but no crash. I can switch to other file, use my terminal, and no GPU hang.

So, I suspect something like an OOM on GPU while Gnome is using GPU.

I continue to test, maybe I'm wrong but it seems that I can use Blender using that Desktop Manager. I'm typing this message with F8892221 file opened, with material preview in progress - 10 minutes, no hang.

OK, I tried something to be sure. I've installed Pantheon desktop `sudo dnf install "pantheon desktop"` and tried to open [F8892221](https://archive.blender.org/developer/F8892221/gpuhangtest.blend) .blend file. It's very slow, but no crash. I can switch to other file, use my terminal, and no GPU hang. So, I suspect something like an OOM on GPU while Gnome is using GPU. I continue to test, maybe I'm wrong but it seems that I can use Blender using that Desktop Manager. I'm typing this message with [F8892221](https://archive.blender.org/developer/F8892221/gpuhangtest.blend) file opened, with material preview in progress - 10 minutes, no hang.

Patrice commented

2020-09-22 17:17:46 +02:00

Forget my last comment, it hangs with Pantheon, very later than with Gnome, but it hangs.

AnsonX10 commented

2020-09-23 20:55:38 +02:00

Added subscriber: @AnsonX10

AnsonX10 commented

2020-09-23 20:55:38 +02:00

Are you able to restore functionality of the computer by switching to tty3 or something and restarting your display manager? It may be the same problem I'm having.
I have a HD 630 and it freezes my display manager seemingly randomly when navigating in a 3d viewport. The GPUhangtest.blend file doesn't immediately crash my display manager, but I guarantee it eventually would (it happens on all files I've tried).

It seems to happen much sooner when using X11 and takes much longer to happen when using Wayland (tested on Plasma+SDDM and Gnome+GDM) although it's likely not a time-based difference as much as a "chances of occurring" issue.

Interestingly, I've never had it happen when using an Nvidia GPU (using Nvidia drivers and X11)

Here are my specs:
Linux-5.8.10-arch1-1-x86_64-with-arch 64 Bits
Mesa Intel(R) HD Graphics 630 (KBL GT2) Intel 4.6 (Core Profile) Mesa 20.1.8
Blender 2.91.0 Alpha, branch: master, commit date: 2020-09-22 18:36, hash: 358a8e00bd

Are you able to restore functionality of the computer by switching to tty3 or something and restarting your display manager? It may be the same problem I'm having. I have a HD 630 and it freezes my display manager seemingly randomly when navigating in a 3d viewport. The GPUhangtest.blend file doesn't immediately crash my display manager, but I guarantee it eventually would (it happens on all files I've tried). It seems to happen much sooner when using X11 and takes much longer to happen when using Wayland (tested on Plasma+SDDM and Gnome+GDM) although it's likely not a time-based difference as much as a "chances of occurring" issue. Interestingly, I've never had it happen when using an Nvidia GPU (using Nvidia drivers and X11) Here are my specs: Linux-5.8.10-arch1-1-x86_64-with-arch 64 Bits Mesa Intel(R) HD Graphics 630 (KBL GT2) Intel 4.6 (Core Profile) Mesa 20.1.8 Blender 2.91.0 Alpha, branch: master, commit date: 2020-09-22 18:36, hash: `358a8e00bd`

Patrice commented

2020-09-25 20:04:59 +02:00

@AnsonX10 yes, as I said earlier, that's the case. I go to tty3 and do "init 3", then back one more time to tty3 and "init 5". This resets card's memory, so I can go back to DM (gdm here) but, of course, I lose my non saved work...

It happens less often with Pantheon desktop (I switched to it from Gnome several days ago, it uses Wayland but it seems that it is less heavy for GPU memory. So I can (with crossed fingers, several lucky charm and incantations) use 2.90.1 more than 30 minutes (for now). But I just downloaded Blender 2.90.1, and haven't made a lot of tess (I didn't opened the example blend file).

It seems that it is mesa or intel driver that is faulty. But, in case of, I leave this issue opened if one developper finds something.

I will of course give news about Panthon + Blender 2.91.1 if something goes wrong again.

Thanks for your feedback.

@AnsonX10 yes, as I said earlier, that's the case. I go to tty3 and do "init 3", then back one more time to tty3 and "init 5". This resets card's memory, so I can go back to DM (gdm here) but, of course, I lose my non saved work... It happens less often with Pantheon desktop (I switched to it from Gnome several days ago, it uses Wayland but it seems that it is less heavy for GPU memory. So I can (with crossed fingers, several lucky charm and incantations) use 2.90.1 more than 30 minutes (for now). But I just downloaded Blender 2.90.1, and haven't made a lot of tess (I didn't opened the example blend file). It seems that it is mesa or intel driver that is faulty. But, in case of, I leave this issue opened if one developper finds something. I will of course give news about Panthon + Blender 2.91.1 if something goes wrong again. Thanks for your feedback.

AnsonX10 commented

2020-09-25 20:20:54 +02:00

@Metal3d Oh ok. I missed that message, sorry. (I restart it differently)

At least in my case (SDDM), you actually still have full control of your computer. You just can't see it. So you can control-S to save your work, and even close all your programs properly before restarting your desktop manager. If you can still see your mouse cursor, you're able to click on things too, if needed.

@Metal3d Oh ok. I missed that message, sorry. (I restart it differently) At least in my case (SDDM), you actually still have full control of your computer. You just can't see it. So you can control-S to save your work, and even close all your programs properly before restarting your desktop manager. If you can still see your mouse cursor, you're able to click on things too, if needed.

AnsonX10 commented

2020-10-01 23:06:57 +02:00

I can confirm this same issue occurs in other programs too. So it's (probably) not a Blender-specific issue per se, but we shouldn't necessarily avoid looking into mitigations.

Henrik D. commented

2020-10-01 23:40:04 +02:00

@AnsonX10 can you be a little bit more specific? I didn't have issues in other programs yet, but I don't use many 3D apps.

AnsonX10 commented

2020-10-02 21:27:25 +02:00

@HDMaster84 Well just now I was using FreeCAD on the same Arch system and it crashed my display manager in an identical manner. This led me to believe it could be a Mesa driver problem for Intel graphics. To be honest, I don't know much about how drivers work, so I could be placing the blame in the wrong place. It's even still possible that the causes are different.

Richard Antalik commented

2020-11-26 20:09:07 +01:00

Added subscribers: @Tooniis, @iss, @Newtron, @Heathcliff, @mano-wii, @AcidRain0, @ankitm

Richard Antalik commented

2020-11-26 20:12:28 +01:00

Added subscribers: @mattffly, @Yquux, @kursadk, @Cowhead, @fho, @TimothyDrewFilms, @CepheidVariable, @Tuxgirl, @luc2, @rafaeldomi, @hussam, @dniku, @jhidding

Richard Antalik commented

2020-11-26 20:15:26 +01:00

Added subscribers: @Lendo, @Ravidk, @aialt, @dfelinto, @Mainframed, @HooglyBoogly

Richard Antalik commented

2020-11-26 20:45:28 +01:00

Added subscribers: @BlastedPupil, @MasterF1, @Euan, @GAPsWorld, @Alaska

Matheus commented

2020-11-26 20:50:21 +01:00

Removed subscriber: @mattffly

Gary Parris commented

2020-11-27 10:13:15 +01:00

i have my passthrough GPU working on my hybrid intel CPU i7+GPU 620/AMD R7 GPU laptop. although it doesnt show the GPU selectable in the Opencl system properties, when i am using EEvEE, cycles GPU and Luxcore GPU it works on any Blender v2.80 to v2.92 was the following:

Fedora 32 with AMD Mesa drivers (volcanic islands)

Edit /etc/default/grubto have the following lines and information.GRUB_CMDLINE_LINUX="rhgb quiet splash amdgpu.dc=0 radeon.cik_support=0 amdgpu.cik_support=1"

the (.cik) is used above instead of (.cis) because mine is part of the volcanic islands

make sure permission on folder include root and you_user_profifle as having read+write permissions

then i tend to login in a command console and execute, run" DRI_PRIME=1 /home/User_profile/blender-2.92.0/blender ".

this works for me

i have my passthrough GPU working on my hybrid intel CPU i7+GPU 620/AMD R7 GPU laptop. although it doesnt show the GPU selectable in the Opencl system properties, when i am using EEvEE, cycles GPU and Luxcore GPU it works on any Blender v2.80 to v2.92 was the following: Fedora 32 with AMD Mesa drivers (volcanic islands) Edit **/etc/default/grub**to have the following lines and information.**GRUB_CMDLINE_LINUX="rhgb quiet splash amdgpu.dc=0 radeon.cik_support=0 amdgpu.cik_support=1**" the (.cik) is used above instead of (.cis) because mine is part of the volcanic islands make sure permission on folder include root and you_user_profifle as having read+write permissions then i tend to login in a command console and execute, run" **DRI_PRIME=1 /home/User_profile/blender-2.92.0/blender** ". this works for me

Alaska commented

2020-11-28 23:41:35 +01:00

Removed subscriber: @Alaska

Dmitry Perfilyev commented

2021-01-03 10:37:05 +01:00

Added subscriber: @dp-1

Dmitry Perfilyev commented

2021-01-03 10:37:05 +01:00

If you want hang only blender and not the Xorg completely - turn off acceleration in Xorg config:

/usr/share/X11/xorg.conf.d/20-intel.conf

 Section "Device"
    Identifier  "Intel Graphics"
    Driver      "intel"
    Option      "AccelMethod"  "none"
 EndSection

This could breaks other programs (for me Google Earth doesn't show map entirely )

If you want hang only blender and not the Xorg completely - turn off acceleration in Xorg config: /usr/share/X11/xorg.conf.d/20-intel.conf ``` Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "none" EndSection ``` This could breaks other programs (for me Google Earth doesn't show map entirely )

Diptangshu Dey commented

2021-01-19 09:27:14 +01:00

Added subscriber: @Tha_Hobbist

Gerhard Daniel commented

2021-03-19 12:10:40 +01:00

Added subscriber: @verblendet

Gerhard Daniel commented

2021-03-19 12:30:25 +01:00

me too:
gpuhangtest.blend hangs my laptop; blender frequently crushes after minutes of working( shaders=high risk, no crush while rendering yet)
Linux 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64 GNU/Linux Gnome 3.38.4 X11
Mesa Intel® HD Graphics 530 (SKL GT2)
NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2)
Bumblebee 3.2.1

No othe Software yet provoked a graphic hang

me too: gpuhangtest.blend hangs my laptop; blender frequently crushes after minutes of working( shaders=high risk, no crush while rendering yet) Linux 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64 GNU/Linux Gnome 3.38.4 X11 Mesa Intel® HD Graphics 530 (SKL GT2) NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2) Bumblebee 3.2.1 No othe Software yet provoked a graphic hang

Gary Parris commented

2021-03-19 14:38:15 +01:00

definitely try from the terminal either as user of sudo -i

DRI_PRIME=1 /home/User_profile/blender-2.92.0/blender

or

DRI_PRIME=0 /home/User_profile/blender-2.92.0/blender

definitely try from the terminal either as user of sudo -i DRI_PRIME=1 /home/User_profile/blender-2.92.0/blender or DRI_PRIME=0 /home/User_profile/blender-2.92.0/blender

Gerhard Daniel commented

2021-03-23 11:58:17 +01:00

owning an optimus laptop I use as workaround primusrun blender with no more hangs!! after 30hours of heavy testing. gpuhangtest no problem either :-)

Florian commented

2021-03-23 14:41:48 +01:00

Removed subscriber: @fho

Germano Cavalcante commented

2021-04-08 17:51:16 +02:00

Added subscriber: @melonmousegames

Ravid commented

2021-04-08 17:53:21 +02:00

Removed subscriber: @Ravidk

Pavel Duong commented

2021-04-10 17:23:44 +02:00

Added subscriber: @vignette

Pavel Duong commented

2021-04-10 17:23:44 +02:00

In my past experiences, I have gotten a lot of GPU hangs in dmesg, freezing the screen and forcing me to either restart or kill the desktop environment. Both causing me to lose my unsaved work. After a bit of experimenting it seems (or at least in my case) Blender is unstable on the iris GPU driver. I have been running Blender with forced i965 driver and it hasn't crashed my entire GPU even once for the past 4 months of using this workaround.

Running Blender with MESA_LOADER_DRIVER_OVERRIDE=i965 makes me able to run the gpuhangtest.blend with no issues. This can be a bit worrisome, since if I recall correctly, there was a proposal to drop the i965 driver from MESA's mainline.

Just for the record, I'm dropping system-info reports for both the iris and i965 drivers:
system-info-iris.txt

system-info-i965.txt

In my past experiences, I have gotten a lot of GPU hangs in `dmesg`, freezing the screen and forcing me to either restart or kill the desktop environment. Both causing me to lose my unsaved work. After a bit of experimenting it seems (or at least in my case) Blender is unstable on the `iris` GPU driver. I have been running Blender with forced `i965` driver and it hasn't crashed my entire GPU even once for the past 4 months of using this workaround. Running Blender with `MESA_LOADER_DRIVER_OVERRIDE=i965` makes me able to run the `gpuhangtest.blend` with no issues. This can be a bit worrisome, since if I recall correctly, there was a proposal to drop the `i965` driver from MESA's mainline. Just for the record, I'm dropping `system-info` reports for both the `iris` and `i965` drivers: [system-info-iris.txt](https://archive.blender.org/developer/F9928269/system-info-iris.txt) [system-info-i965.txt](https://archive.blender.org/developer/F9928270/system-info-i965.txt)

Jacob Z commented

2021-04-11 12:51:19 +02:00

Added subscriber: @TooMuchFun

Jacob Z commented

2021-04-11 12:51:19 +02:00

Just a heads up. I have a laptop with intel UHD 630 and a dedicated Nvidia GeForce 1650 GPU on Windows 10, V. 10.01.19041.844 and I am having a similar issue.

Oh, and this has been happening with versions 2.90.0, 2.92.0 and including the latest nightly build: 2.93.0 (April/09/2021)

I try to open a file through the open file dialog and the application immediately hangs. This is very annoying. It will recover a few minutes later but if I attempt to do anything else it will crash.

Does anyone know of a fix??

Just a heads up. I have a laptop with intel UHD 630 and a dedicated Nvidia GeForce 1650 GPU on Windows 10, V. 10.01.19041.844 and I am having a similar issue. Oh, and this has been happening with versions 2.90.0, 2.92.0 and including the latest nightly build: 2.93.0 (April/09/2021) I try to open a file through the open file dialog and the application immediately hangs. This is very annoying. It will recover a few minutes later but if I attempt to do anything else it will crash. Does anyone know of a fix??

Henrik D. commented

2021-04-12 09:20:43 +02:00

@TooMuchFun You are describing something completely different. Please open a new bug report with all the required information (you need to specify a working version for these kind of reports).

Jacob Z commented

2021-04-13 20:36:14 +02:00

Thank you for the direction, Henrik ;D

Jon Doe commented

2021-04-13 20:58:48 +02:00

Removed subscriber: @Mainframed

Christine Lemmer-Webber commented

2021-06-25 02:45:24 +02:00

Added subscriber: @ChristopherWebber

Christine Lemmer-Webber commented

2021-06-25 02:45:24 +02:00

I am running:

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake)

and Blender version 2.92.0.

I can confirm that the test file crashes blender, and indeed my entire desktop, over here.

I've also had weird desktop-destroying issues while doing editing, etc. I haven't figured out if this is separate from issues in the above file.

I initially thought that the error was because of this bug, but it appears that the fix is indeed in 2.92.0 so I no longer think that's the source of the issue. (In fact, the entire file relevant to that patch seems to have been removed and replaced with some new infrastructure, so I dunno.)

Note that others in Guix-land have reported similar issues... I think people running intel cards over there is probably more common (due to them being some of the few cards with reasonably working FOSS drivers).

I am running: > 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) and Blender version 2.92.0. I can confirm that the test file crashes blender, and indeed my entire desktop, over here. I've also had weird desktop-destroying issues while doing editing, etc. I haven't figured out if this is separate from issues in the above file. I initially thought that the error was because of [this bug](https:*developer.blender.org/T72902), but it appears that [the fix](https:*developer.blender.org/rBb7acb8690a4d189868c6e0b57057b6fcd8a5a96d) is indeed in 2.92.0 so I no longer think that's the source of the issue. (In fact, the entire file relevant to that patch seems to have been removed and replaced with some new infrastructure, so I dunno.) Note that [others in Guix-land](https://lists.gnu.org/archive/html/help-guix/2021-03/msg00164.html) have reported similar issues... I think people running intel cards over there is probably more common (due to them being some of the few cards with reasonably working FOSS drivers).

saturniidae commented

2021-07-03 20:43:42 +02:00

Added subscriber: @saturniidae

saturniidae commented

2021-07-03 20:43:42 +02:00

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

with i915 driver on Blender 2.93.0. I can replicate consistently with the test file, but I first encountered the problem on a significantly simpler model. I wasn't even sure if it was Blender at first until I checked the journal, since there was pretty much no lag until everything suddenly froze up.

Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 6:1:f28007f8, in blender [2496]
Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] blender[2496] context reset due to GPU hang

From the looks of it, it's hanging, tries to recover, but then hangs again instantly, as I tend to get a few repetitions of these lines.
I've attached my best recreation of the file I initially froze on, though I haven't been able to recreate the freeze with it. The only real difference in this one should be the positioning of the corners, as I was adjusting them on the X and Y axes and don't know the exact positions they were in, though this is fairly close. screwhole_test_freeze.blend

> 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) with i915 driver on Blender 2.93.0. I can replicate consistently with the test file, but I first encountered the problem on a significantly simpler model. I wasn't even sure if it was Blender at first until I checked the journal, since there was pretty much no lag until everything suddenly froze up. > Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 6:1:f28007f8, in blender [2496] >Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 >Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] blender[2496] context reset due to GPU hang From the looks of it, it's hanging, tries to recover, but then hangs again instantly, as I tend to get a few repetitions of these lines. I've attached my best recreation of the file I initially froze on, though I haven't been able to recreate the freeze with it. The only real difference in this one should be the positioning of the corners, as I was adjusting them on the X and Y axes and don't know the exact positions they were in, though this is fairly close. [screwhole_test_freeze.blend](https://archive.blender.org/developer/F10210628/screwhole_test_freeze.blend)

Ekaitz commented

2021-10-03 22:02:46 +02:00

Added subscriber: @ekaitz

Ekaitz commented

2021-10-03 22:02:46 +02:00

In #80458#1186582, @saturniidae wrote:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

with i915 driver on Blender 2.93.0. I can replicate consistently with the test file, but I first encountered the problem on a significantly simpler model. I wasn't even sure if it was Blender at first until I checked the journal, since there was pretty much no lag until everything suddenly froze up.

Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 6:1:f28007f8, in blender [2496]
Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] blender[2496] context reset due to GPU hang

From the looks of it, it's hanging, tries to recover, but then hangs again instantly, as I tend to get a few repetitions of these lines.
I've attached my best recreation of the file I initially froze on, though I haven't been able to recreate the freeze with it. The only real difference in this one should be the positioning of the corners, as I was adjusting them on the X and Y axes and don't know the exact positions they were in, though this is fairly close. screwhole_test_freeze.blend

I just replicated the issue with the test file of this post, right after it happened with the model I was working on. My error messages look a little bit different, but pretty similar:


Oct  3 21:52:44 localhost vmunix: [35774.167860] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
Oct  3 21:52:44 localhost vmunix: [35774.167877] i915 0000:00:02.0: [drm] blender[12755] context reset due to GPU hang
Oct  3 21:52:44 localhost vmunix: [35774.197793] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85df9ebf, in blender [12755]
Oct  3 21:52:45 localhost vmunix: [35774.871808] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
Oct  3 21:52:45 localhost vmunix: [35774.871827] i915 0000:00:02.0: [drm] blender[12755] context reset due to GPU hang
Oct  3 21:52:45 localhost vmunix: [35774.879501] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dfbfff, in blender [12755]
Oct  3 21:52:54 localhost vmunix: [35784.215617] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
Oct  3 21:52:54 localhost vmunix: [35784.215643] i915 0000:00:02.0: [drm] blender[12755] context reset due to GPU hang
Oct  3 21:52:54 localhost vmunix: [35784.224865] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dfbfff, in blender [12755]

> In #80458#1186582, @saturniidae wrote: >> 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) > with i915 driver on Blender 2.93.0. I can replicate consistently with the test file, but I first encountered the problem on a significantly simpler model. I wasn't even sure if it was Blender at first until I checked the journal, since there was pretty much no lag until everything suddenly froze up. >> Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 6:1:f28007f8, in blender [2496] >>Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 >>Jul 03 12:26:31 velvetant kernel: i915 0000:00:02.0: [drm] blender[2496] context reset due to GPU hang > From the looks of it, it's hanging, tries to recover, but then hangs again instantly, as I tend to get a few repetitions of these lines. > I've attached my best recreation of the file I initially froze on, though I haven't been able to recreate the freeze with it. The only real difference in this one should be the positioning of the corners, as I was adjusting them on the X and Y axes and don't know the exact positions they were in, though this is fairly close. [screwhole_test_freeze.blend](https://archive.blender.org/developer/F10210628/screwhole_test_freeze.blend) I just replicated the issue with the test file of this post, right after it happened with the model I was working on. My error messages look a little bit different, but pretty similar: ``` Oct 3 21:52:44 localhost vmunix: [35774.167860] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out Oct 3 21:52:44 localhost vmunix: [35774.167877] i915 0000:00:02.0: [drm] blender[12755] context reset due to GPU hang Oct 3 21:52:44 localhost vmunix: [35774.197793] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85df9ebf, in blender [12755] Oct 3 21:52:45 localhost vmunix: [35774.871808] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out Oct 3 21:52:45 localhost vmunix: [35774.871827] i915 0000:00:02.0: [drm] blender[12755] context reset due to GPU hang Oct 3 21:52:45 localhost vmunix: [35774.879501] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dfbfff, in blender [12755] Oct 3 21:52:54 localhost vmunix: [35784.215617] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out Oct 3 21:52:54 localhost vmunix: [35784.215643] i915 0000:00:02.0: [drm] blender[12755] context reset due to GPU hang Oct 3 21:52:54 localhost vmunix: [35784.224865] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dfbfff, in blender [12755] ```

Alexandr commented

2021-10-13 16:00:54 +02:00

Added subscriber: @scaled

Alexandr commented

2021-10-13 16:00:54 +02:00

This command fix gpu hang (run from root), but i don't know, where is drawback of changing this varriable. My GPU is HD Graphics 520.

echo 10000 > /sys/class/drm/card0/engine/rcs0/preempt_timeout_ms

This command fix gpu hang (run from root), but i don't know, where is drawback of changing this varriable. My GPU is HD Graphics 520. ``` echo 10000 > /sys/class/drm/card0/engine/rcs0/preempt_timeout_ms ```

Matthew Woehlke commented

2022-09-09 02:21:42 +02:00

Added subscriber: @mwoehlke

Matthew Woehlke commented

2022-09-09 02:21:42 +02:00

FYI, I think I'm experiencing the same bug with blender-3.2.1-2.fc36.x86_64. Happens frequently with Blender, can't say I've ever seen it happen with anything else (although Blender is probably by far the hardest my poor Intel Corporation UHD Graphics 620 gets hit, followed by FreeCAD).

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Reliable GPU hang on common Intel cards (Linux) #80458