From: Frederik Schwan <frederik@tty42.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
regressions@lists.linux.dev, Imre Deak <imre.deak@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [REGRESSION] i915: UHBR training fails with TB5 dock after 1fd440de4e02; source FFE update skipped?
Date: Mon, 16 Nov 2026 13:39:43 +0100 [thread overview]
Message-ID: <avr5VTYmuO4E1yax@mail.tty42.de> (raw)
In-Reply-To: <40e2af4139b94eaeecd41fcdccb4ec1ef3dc098a@intel.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Mon, Nov 16, 2026 at 12:35:25PM +0200, Jani Nikula wrote:
> On Fri, 13 Nov 2026, Frederik Schwan <frederik@tty42.de> wrote:
> > Hi everyone,
> > I just upgraded my system to 7.3.x and found a regression with my notebook/dock setup.
> > 3x 4k displays are hooked to the dock, 2 by DP and one through USB-C (I guess that DP-alt mode then).
> >
> > Until 7.2 all displays worked. With 7.3 all displays work until kernel switches from fbdev (?) after
> > which the 2 DP displays have no signal anymore but the USB-C one still works.
>
> Please file i915 bugs as described at [1].
>
> BR,
> Jani.
>
>
> [1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
>
>
> --
> Jani Nikula, Intel
Done, report continues here [1].
Best regards,
Frederik
[1] https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items?sort=created_date&state=opened&first_page_size=20&show=eyJpaWQiOiIxNzg0OCIsImZ1bGxfcGF0aCI6ImRybS9pOTE1L2tlcm5lbCIsImlkIjoxNjA3ODl9
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2026-11-16 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 22:08 [REGRESSION] i915: UHBR training fails with TB5 dock after 1fd440de4e02; source FFE update skipped? Frederik Schwan
2026-11-16 10:35 ` Jani Nikula
2026-11-16 12:39 ` Frederik Schwan [this message]
2026-11-16 14:24 ` Imre Deak
2026-11-16 14:49 ` sashiko-bot
2026-11-16 17:46 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
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=avr5VTYmuO4E1yax@mail.tty42.de \
--to=frederik@tty42.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=regressions@lists.linux.dev \
--cc=rodrigo.vivi@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