From: Salvatore Bonaccorso <carnil@debian.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matthew Fahner <mdfahner@gmail.com>,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Second Monitor Issue on Kernel 6.1.5
Date: Sat, 14 Jan 2023 15:52:57 +0100 [thread overview]
Message-ID: <Y8LByXvibutD79au@eldamar.lan> (raw)
In-Reply-To: <Y8JSMlMgnggwOYl0@kroah.com>
Hi,
On Sat, Jan 14, 2023 at 07:56:50AM +0100, Greg KH wrote:
> On Fri, Jan 13, 2023 at 11:58:47PM -0500, Matthew Fahner wrote:
> > Hello,
> >
> > I'm running Ubuntu 20.10 and experienced a regression when trying
> > kernel 6.1.5 that was not present in previous kernels such as 6.0.19
> > or 6.0.9
> >
> > I have two monitors attached using DisplayPort MST (daisy chaining the
> > displays).
> >
> > Normally, this works without issue and both monitors are detected and
> > display properly.
> >
> > With kernel 6.1.5, the second monitor (the monitor that's not directly
> > connected to the computer) was detected but would not display. I
> > didn't spend much time troubleshooting the issue and instead reverted
> > to 6.0.19 where it again worked without issue. The first monitor
> > worked without issue.
> >
> > Let me know what steps I can take to help identify the root cause.
>
> Can you use 'git bisect' to track down the offending commit?
Not the reporter, but I suspect this is
https://gitlab.freedesktop.org/drm/amd/-/issues/2171 .
Matthew can you verify this matches? There is as well context on this
issue on this thread:
https://lore.kernel.org/stable/8502e5d8-8444-e256-54f3-0c488b54686a@amd.com/
FWIW, we had a similar bugreport downstream in Debian:
https://bugs.debian.org/1028451
Regards,
Salvatore
next prev parent reply other threads:[~2023-01-14 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 4:58 Second Monitor Issue on Kernel 6.1.5 Matthew Fahner
2023-01-14 6:56 ` Greg KH
2023-01-14 14:52 ` Salvatore Bonaccorso [this message]
2023-01-15 0:55 ` Matthew Fahner
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=Y8LByXvibutD79au@eldamar.lan \
--to=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=mdfahner@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=stable@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 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.