From: Stefan Joosten <stefan@atcomputing.nl>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] Revert "drm/i915: Force state->modeset=true when distrust_bios_wm==true"
Date: Thu, 15 Oct 2020 16:37:39 +0200 [thread overview]
Message-ID: <b58d854afe42d45f499b978da96f0cf29c5e574c.camel@atcomputing.nl> (raw)
In-Reply-To: <20201001152346.GR6112@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1537 bytes --]
Dear Ville Syrjälä,
Thank you for responding so quickly.
I was occupied with work and life for the past two weeks, sorry about
the wait, but have now managed to find some time to continue pursuing
this issue again.
On Thu, 2020-10-01 at 18:23 +0300, Ville Syrjälä wrote:
> Argh. If only I had managed to land the full dbuf rework and nuke
> this mess before it came back to bite us...
Yeah... I know the feeling.
> This is definitely going to break something else, so not great.
I did expect that. The automated tests failing was a pretty good
indicator.
You put that code in to take care of something. All I did was just tear
it down because it happens to work better for me... blunt but
functional for my purposes.
Seems to need some finesse or a condition to not cause my problem? Yet
still function for the reason you put it in there for.
I am more than willing to play guinea pig and test patches on my end to
improve it with you.
> Can you file an upstream bug at
> https://gitlab.freedesktop.org/drm/intel/issues/new
> and attach dmesgs from booting both good and bad kernels with
> drm.debug=0x1e passed to the kernel cmdline? Bump log_buf_len=
> if necessary to capture the full log.
I have done so today.
It's at: https://gitlab.freedesktop.org/drm/intel/-/issues/2579
--
Stefan Joosten
AT Computing BV
Sharing and growing together Tel +31 24 352 72 82
Arnhemsestraatweg 33 info@atcomputing.nl
6881 ND Velp www.atcomputing.nl
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 516 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-10-16 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 13:47 [Intel-gfx] [PATCH] Revert "drm/i915: Force state->modeset=true when distrust_bios_wm==true" Stefan Joosten
2020-09-30 15:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-10-01 15:23 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2020-10-15 14:37 ` Stefan Joosten [this message]
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=b58d854afe42d45f499b978da96f0cf29c5e574c.camel@atcomputing.nl \
--to=stefan@atcomputing.nl \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/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