unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "help-guix\\@gnu.org" <help-guix@gnu.org>,
	Christopher Lemmer Webber <cwebber@dustycloud.org>
Subject: Re: Blender freezes i3wm
Date: Sun, 03 Oct 2021 19:59:09 +0000	[thread overview]
Message-ID: <rp_OM4d-DqrgGHZhq5JcsfV_lNCPHk9eY2NLQZZWY7UHSEuzL9LnoE54cOxTzUJWYdwOlPlKr3lz82hg3QHSK36Td_GoZ9WoOF4SdZIQ7R4=@elenq.tech> (raw)

> Well I was wrong about the patch applying cleanly too.  Not paying close
> Attention, apparently.  And that patch was merged already in the current
> Version of Blender we ship.
>
> It looks like my GPU, which is (according to lspci):
>
>   00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
> (Whiskey Lake)
>
> Has particular trouble:
>
>   https://developer.blender.org/T80458#1182395
>
> Frustrating.

Hi all,

I found this error again and I don't know what to do.
Honestly this sucks really hard.

I checked the error report at blender.org and I find the
same error even with the same file that is added in the error
report:

```
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]
```

Is there any chance that we can fix this?
Any ideas?


             reply	other threads:[~2021-10-03 19:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 19:59 Ekaitz Zarraga [this message]
2021-10-03 20:40 ` Blender freezes i3wm Leo Famulari
2021-10-03 20:47   ` Ekaitz Zarraga
  -- strict thread matches above, loose matches on Subject: below --
2021-03-18 17:40 Ekaitz Zarraga
2021-03-19  1:24 ` raingloom
2021-03-19 12:49   ` Ekaitz Zarraga
2021-03-19 16:00     ` raingloom
2021-03-27  1:09       ` Ekaitz Zarraga
2021-03-27 12:07         ` Ekaitz Zarraga
2021-03-27 14:45         ` Luis Felipe
2021-03-27 19:33           ` Luis Felipe
2021-03-27 21:31             ` Ekaitz Zarraga
2021-03-29  9:36               ` Ekaitz Zarraga
2021-06-24 16:17                 ` Chris Lemmer-Webber
2021-06-24 18:32                   ` Chris Lemmer-Webber
2021-06-25 17:49                     ` Chris Lemmer-Webber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='rp_OM4d-DqrgGHZhq5JcsfV_lNCPHk9eY2NLQZZWY7UHSEuzL9LnoE54cOxTzUJWYdwOlPlKr3lz82hg3QHSK36Td_GoZ9WoOF4SdZIQ7R4=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=cwebber@dustycloud.org \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).