I have no such issues

System Information
Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64
version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 03:43, hash: rBb4d50d3f07bb

Thank you for replying.

I should have mentioned that I have tried also in Gnome Xorg and that
I have tried the Fedora and portable versions of each.
I just tried again to confirm that it still happens.

(I have also tried in live version of Debian)

Maybe this has to do with this being a Kaby Lake and mitigations are
affecting something ?

(I have tried with another laptop with an AMD and seems to work fine,
but slow and it gets hot)

Another thought is this is a small desktop machine/CPU but uses
laptop sodimm RAM but I don't think that would matter.

I will review how to compile blender in the meantime, which I haven't
tried before.

Maybe someone can recommend some compiling options for this
specific processor, i3-7100 ?
If more info is needed for these options I will provide what I can.

Thanks again

Just to update and let you know I am still trying here.

I have also tried flatpak installs in Wayland and X11 but there is not difference.

Currently trying to build blender from master but I am getting errors.
CMakeLists.txt seems to have to be manually remove each time then complains
that it is not there.

I will keep trying

I will research on running a Blender debugger and continue trying to compile
Blender.

The OS is new install of Fedora 32 but I am considering trying another distro.
It may be due to some Intel Gen7 cpu mitigations that have yet to be updated.
I hear that kernel 5.7 will include some updates and am hoping it resolves this.
(Otherwise I may have to adamantly recommend against Asrock products)

I have seen these same problems in previous releases in forums, etc. but it
seems they have resolved for others but for some reason not here.

I am also thinking that Blender may try to allocate memory that may conflict
with the current OS, being that I am running with only 4GB and integrated
graphics. I'm not saying it's a Blender problem but some incompatibility and
the mitigations mentioned above.

I will keep updating any progress here in case it helps someones else and/or
blender in general.

The RAM thing could defiantly be a issue. If Intel GPUs operate like some of the older stuff I've seen with computers, in theory you will have 2GB of "VRAM" for your GPU and 2GB of RAM for your CPU. This isn't that much to run Blender.

However, I may be wrong on this assumption.

I have also been having issues with 2.83 & 2.90 of the system hanging, i get mouse abality and can manage to shutdown safely through memorised key presses or using a kill command set up ready for this, but with varying success. a reboot is the only thing possible once blender hang. workbench also freezes!

I have used Xorg with Gnome and Cinnamon (my default), with Mesa drivers, i've even used the AMD GPU console to see what Blender is doing with GPU, it only works in CPU and doesn't even show my AMD or Intel HD 620, also very unstable in Workbench, EEVEE and cycles, it shows a mouse cursor as corrupted lines. workbench also freezes! i have also tried Fedora from FC 30/31/32. i have the latest Mesa driver for amdgpu and am using a HP laptop with a passthrough GPU Intel HD 620/AMD Radeon R7 M440.

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

i have just tried 2.90 on my other main system using a Nvidia GTX 1060 and it works flawlessly no freeze no errors, GPU and CPU. If AMD are working with blender and Linux why are their Drivers not upto date or working with linux, its ridiculus that AMD cannot support Linux properly and with blender to get these issues sorted.

I have now tried 2.83 portable version using Wayland and Xorg.
The problem continues but seems to take longer before it hangs the system.

Trying to find a reproducible event but I have yet to find one.
It seems that it may be related to change back to solid view after LookDev or Render view.
Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad)

I still have had no luck compiling but this might be Fedora specific problem.
I have installed missing libs that compiler could not find but it still fails to find them.

Sorry if the following is a bit of subject but since user is also experiencing a similar hang...

In T76529#953107, @Gary Parris (GAPsWorld) wrote:

...it only works in CPU and doesn't even show my AMD...

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has
been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes"

Have you had any success compiling in Fedora ?

In T76529#953360, @ArbySmith (BlastedPupil) wrote:

I have now tried 2.83 portable version using Wayland and Xorg.
The problem continues but seems to take longer before it hangs the system.

Trying to find a reproducible event but I have yet to find one.
It seems that it may be related to change back to solid view after LookDev or Render view.
Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad)

I still have had no luck compiling but this might be Fedora specific problem.
I have installed missing libs that compiler could not find but it still fails to find them.

Sorry if the following is a bit of subject but since user is also experiencing a similar hang...

In T76529#953107, @Gary Parris (GAPsWorld) wrote:

...it only works in CPU and doesn't even show my AMD...

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has
been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes"

Have you had any success compiling in Fedora ?

In T76529#953360, @ArbySmith (BlastedPupil) wrote:

I have now tried 2.83 portable version using Wayland and Xorg.
The problem continues but seems to take longer before it hangs the system.

Trying to find a reproducible event but I have yet to find one.
It seems that it may be related to change back to solid view after LookDev or Render view.
Another possibility is toggling back and forth from the ortho/perspective (using 5 on numpad)

I still have had no luck compiling but this might be Fedora specific problem.
I have installed missing libs that compiler could not find but it still fails to find them.

Sorry if the following is a bit of subject but since user is also experiencing a similar hang...

In T76529#953107, @Gary Parris (GAPsWorld) wrote:

...it only works in CPU and doesn't even show my AMD...

i can use 2.82 without crashing but still my GPU doesnt show as available or render in GPU cycles or eevee.

I have also been trying to use on a machine with Intel i5 M 450 and AMD RV710/M92 and although it has
been working it does not show as GPU available in Blender even though inxi shows "direct render: Yes"

Have you had any success compiling in Fedora ?

I've no luck at all with Passthrough nor with compiling its fails to build and halts on some repository that doesnt seem to respond, not sure if it it is linked to the current buildbot problems or not but tried to follow blenders instruction page to build but it doesnt seem to fork with fedora 30/31/32 currently

i also tried 2.79b and it doesnt recognise the AMDGPU either, nor does Luxcore it seems except at least luxcore shows some GPU usage when it passes the final image to the screen. Am tearing my hair out trying to deal with something that should ne a simple click install.

Here are screen grabs from Ubunto which i tried to use 2.90 Alpha on and in different modes maybe it will help, this is using the version downloaded from 16 June 2020

I've just recently started experiencing something similar. I run Fedora 32 on a Huawei matebook x, it's been very stable for about a year, running Fedora 31 and 32, but recently blender had become unusable. After a minute or so of working in blender the screen glitches. I'm left with an unresponsive desktop that seems to be stick between two screen updates, and jumps between them. I can get to a console with ctrl-alt-f3, but I cannot see any errors, and I can progressively kill tasks until I eventually force a logout. This only occurs when running blender, and it appears to do it with several versions, 2.8.1 to current at least. I suspect something has been upgraded in gnome or the kernel. I am not using any gpu resources, just the gen 8 i7 CPU. I have tried under Wayland and xorg.

This looks like an Intel graphics driver issue. It's been reported by a few people over here:

https://gitlab.freedesktop.org/drm/intel/-/issues/2176

In T76529#978781, @Euan de Kock (euan_dk) wrote:

I've just recently started experiencing something similar. I run Fedora 32 on a Huawei matebook x, it's been very stable for about a year, running Fedora 31 and 32, but recently blender had become unusable. After a minute or so of working in blender the screen glitches. I'm left with an unresponsive desktop that seems to be stick between two screen updates, and jumps between them. I can get to a console with ctrl-alt-f3, but I cannot see any errors, and I can progressively kill tasks until I eventually force a logout. This only occurs when running blender, and it appears to do it with several versions, 2.8.1 to current at least. I suspect something has been upgraded in gnome or the kernel. I am not using any gpu resources, just the gen 8 i7 CPU. I have tried under Wayland and xorg.

I am having the exact same issue! and I have no idea how to fix it, but do you think blender 2.9 would work?

i'm only able to use B282a at this stage everything newer is having problems with stability, it will freeze even with the factory defaults loaded, i have tried multiple versions and cant replicate exactly when it will freeze, it can be as simple as changing a value regardless of the mode, or render engine used, it seems to be a vram thing with either AMD GPU or INTEL passthrough to AMD GPU hybrids at this stage.

It turns out it was that the motherboard wasn't compatible (Asrock Deskmini h110m-stx)
I have tried 2.79, 2.80, 2.81, 2.90, 2.91 and alll are working now.

The motherboard is made for Skylake but supposed to be upgradeable to Kaby Lake.
Apparently that is not true and they stopped shipping BIOS updates.