From: Dirk Neukirchen <dirkneukirchen@web.de>
To: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: [Intel-gfx] Haswell Regression in 5.9-rcX and lower 5.7.x, 5.8.x #2024 - Revert 47f8253d2b89 ("drm/i915/gen7: Clear all EU/L3 residual contexts") ?
Date: Tue, 15 Sep 2020 12:10:26 +0200 [thread overview]
Message-ID: <fc85dfc7-7f82-51f3-4fae-efea02a8339c@web.de> (raw)
Hi David, Chris and lists
I am inquiring about the current status of #2024 [1]
Problem: Kernels 5.7.x , 5.8.x, current 5.9-rcs and drm-tip have a large regression on (some?) Haswell (HSW)
This is verified by _multiple people_ using different methods.
All his is documented in [1] , Kernel 5.6.19 was fine
Result: no output, no usable desktop due to gpu crashes
Hardware : 2x Acer C720 Chromebooks and potentially others
Methods:
- running mpv with vaapi enabled
- glxgears
- automatic desktop environment start (probably with acceleration)
There is atm no fix in drm-tip integrated (5.9.0_rc5bisect_g30b3e38bd6d5 for example still errors)
and no activity from Intel in the bug report beside the "working" suggested patches / hacks there
There should be enough bisection info an there.
Nobody asked there to get more info or different bisects/trees.
So - the ticket is still open.
Because Fedora uses newish Kernels I would like to use it "normally" without
going for 5.4 LTS or waiting an unknown amount of time - as 5.9.x currently seems to have the
same regression.
Affected Hardware at my end:
- C720 with a Intel Celeron 2955U
- UEFI Bios instead of original Bios (mrchromebox.tech) if thats relevant for hardware init related bugs;
But the Kernel should take care of the correct initialization anyway
Feel free to comment which trees, branches, tags or patches we should try to help
and what _more_ to report for "Report-By" , "Tested-By", "Verified-By"
tagging so that [1] can be closed.
Greetings, Dirk
[1]https://gitlab.freedesktop.org/drm/intel/-/issues/2024
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2020-09-15 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc85dfc7-7f82-51f3-4fae-efea02a8339c@web.de \
--to=dirkneukirchen@web.de \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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