From: Heiko Carstens <hca@linux.ibm.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
Dave Airlie <airlied@redhat.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [BUG - BISECTED] display not detected anymore
Date: Fri, 20 Aug 2021 18:05:18 +0200 [thread overview]
Message-ID: <YR/SvvDxQjp52h6A@osiris> (raw)
In-Reply-To: <YR6d3nU1R14Eqpic@intel.com>
On Thu, Aug 19, 2021 at 09:07:26PM +0300, Ville Syrjälä wrote:
> > ef79d62b5ce5 ("drm/i915: Encapsulate dbuf state handling harder")
> >
> > With that commit the display is not detected anymore, one commit
> > before that it still works. So this one seems to be broken.
> >
> > Ville, Stanislav, any idea how to fix this?
> >
> > commit ef79d62b5ce53851901d6c1d21b74cbb9e27219b
> > Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Date: Fri Jan 22 22:56:32 2021 +0200
> >
> > drm/i915: Encapsulate dbuf state handling harder
>
> That has nothing to do with display detection, so very mysterious.
>
> Please file a bug at https://gitlab.freedesktop.org/drm/intel/issues/new
> boot with drm.debug=0xe with both good and bad kernels and attach the
> dmesg from both to the bug.
Everything (hopefully) provided here:
https://gitlab.freedesktop.org/drm/intel/-/issues/4013
Please let me know if you need more, or if I can help otherwise to
resolve this.
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Carstens <hca@linux.ibm.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
Dave Airlie <airlied@redhat.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [BUG - BISECTED] display not detected anymore
Date: Fri, 20 Aug 2021 18:05:18 +0200 [thread overview]
Message-ID: <YR/SvvDxQjp52h6A@osiris> (raw)
In-Reply-To: <YR6d3nU1R14Eqpic@intel.com>
On Thu, Aug 19, 2021 at 09:07:26PM +0300, Ville Syrjälä wrote:
> > ef79d62b5ce5 ("drm/i915: Encapsulate dbuf state handling harder")
> >
> > With that commit the display is not detected anymore, one commit
> > before that it still works. So this one seems to be broken.
> >
> > Ville, Stanislav, any idea how to fix this?
> >
> > commit ef79d62b5ce53851901d6c1d21b74cbb9e27219b
> > Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Date: Fri Jan 22 22:56:32 2021 +0200
> >
> > drm/i915: Encapsulate dbuf state handling harder
>
> That has nothing to do with display detection, so very mysterious.
>
> Please file a bug at https://gitlab.freedesktop.org/drm/intel/issues/new
> boot with drm.debug=0xe with both good and bad kernels and attach the
> dmesg from both to the bug.
Everything (hopefully) provided here:
https://gitlab.freedesktop.org/drm/intel/-/issues/4013
Please let me know if you need more, or if I can help otherwise to
resolve this.
next prev parent reply other threads:[~2021-08-20 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 12:46 [BUG - BISECTED] display not detected anymore Heiko Carstens
2021-08-14 12:46 ` [Intel-gfx] " Heiko Carstens
2021-08-18 11:20 ` Heiko Carstens
2021-08-18 11:20 ` [Intel-gfx] " Heiko Carstens
2021-08-19 18:07 ` Ville Syrjälä
2021-08-19 18:07 ` [Intel-gfx] " Ville Syrjälä
2021-08-20 16:05 ` Heiko Carstens [this message]
2021-08-20 16:05 ` Heiko Carstens
2021-08-26 18:45 ` Heiko Carstens
2021-08-26 18:45 ` [Intel-gfx] " Heiko Carstens
2021-09-09 8:12 ` Heiko Carstens
2021-09-09 8:12 ` [Intel-gfx] " Heiko Carstens
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=YR/SvvDxQjp52h6A@osiris \
--to=hca@linux.ibm.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stanislav.lisovskiy@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.