From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Heiko Carstens <hca@linux.ibm.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: Thu, 19 Aug 2021 21:07:26 +0300 [thread overview]
Message-ID: <YR6d3nU1R14Eqpic@intel.com> (raw)
In-Reply-To: <YRztFhtGS9RkP2Bf@osiris>
On Wed, Aug 18, 2021 at 01:20:54PM +0200, Heiko Carstens wrote:
> On Sat, Aug 14, 2021 at 02:46:27PM +0200, Heiko Carstens wrote:
> > Hello,
> >
> > I have Fedora 33 running, and with the Fedore kernel update from 5.11
> > series to 5.12 my external monitor was not detected anymore. Same is
> > true with the Fedora supplied 5.13 kernel version.
> >
> > So I tried with vanilla kernel 5.11 and latest git head from Linus'
> > tree. 5.11 works while latest git head does not. Bisecting the problem
> > points to commit 32c3d9b0f51e ("Merge tag 'drm-intel-next-2021-01-27'
> > of git://anongit.freedesktop.org/drm/drm-intel into drm-next").
> >
> > Unfortunately it is a merge commit, so it looks like conflicting
> > changes have been made in the parent branches.
> >
> > Hardware in use:
> >
> > - ThinkPad X1 Yoga 4th / Carbon 7th
> > - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
> >
> > The Thinkpad is connected to a ThinkPad Thunderbolt 3 Dock with a
> > Thunderbolt cable and a monitor (Eizo EV3285) is connected via
> > Displayport to the docking station.
> >
> > The monitor is detected and works without any problems (4k@60HZ)
> > before the above mentioned merge commit. With the commit and
> > afterwards it is not detected anymore and only the Thinkpad builtin
> > display can be used.
> >
> > Any idea what went wrong? I can provide more information, or test
> > debug patches if wanted. Just let me know.
>
> So looks like I made a mistake when bisecting (it literally took me
> two days due to the low power machine, even with a minimized kernel
> config). Anyway, looking into it again the first bad commit is
>
> 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.
--
Ville Syrjälä
Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Heiko Carstens <hca@linux.ibm.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: Thu, 19 Aug 2021 21:07:26 +0300 [thread overview]
Message-ID: <YR6d3nU1R14Eqpic@intel.com> (raw)
In-Reply-To: <YRztFhtGS9RkP2Bf@osiris>
On Wed, Aug 18, 2021 at 01:20:54PM +0200, Heiko Carstens wrote:
> On Sat, Aug 14, 2021 at 02:46:27PM +0200, Heiko Carstens wrote:
> > Hello,
> >
> > I have Fedora 33 running, and with the Fedore kernel update from 5.11
> > series to 5.12 my external monitor was not detected anymore. Same is
> > true with the Fedora supplied 5.13 kernel version.
> >
> > So I tried with vanilla kernel 5.11 and latest git head from Linus'
> > tree. 5.11 works while latest git head does not. Bisecting the problem
> > points to commit 32c3d9b0f51e ("Merge tag 'drm-intel-next-2021-01-27'
> > of git://anongit.freedesktop.org/drm/drm-intel into drm-next").
> >
> > Unfortunately it is a merge commit, so it looks like conflicting
> > changes have been made in the parent branches.
> >
> > Hardware in use:
> >
> > - ThinkPad X1 Yoga 4th / Carbon 7th
> > - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
> >
> > The Thinkpad is connected to a ThinkPad Thunderbolt 3 Dock with a
> > Thunderbolt cable and a monitor (Eizo EV3285) is connected via
> > Displayport to the docking station.
> >
> > The monitor is detected and works without any problems (4k@60HZ)
> > before the above mentioned merge commit. With the commit and
> > afterwards it is not detected anymore and only the Thinkpad builtin
> > display can be used.
> >
> > Any idea what went wrong? I can provide more information, or test
> > debug patches if wanted. Just let me know.
>
> So looks like I made a mistake when bisecting (it literally took me
> two days due to the low power machine, even with a minimized kernel
> config). Anyway, looking into it again the first bad commit is
>
> 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.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2021-08-19 18:07 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ä [this message]
2021-08-19 18:07 ` Ville Syrjälä
2021-08-20 16:05 ` Heiko Carstens
2021-08-20 16:05 ` [Intel-gfx] " 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=YR6d3nU1R14Eqpic@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hca@linux.ibm.com \
--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 \
/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.