Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: Marcin <martii@interia.pl>,
	linux-pci@vger.kernel.org, dri-devel@lists.freedesktop.org,
	regressions@lists.linux.dev
Subject: Re: [Bug 216950] New: DisplayPort USB-C hub issue
Date: Wed, 18 Jan 2023 15:14:24 -0600	[thread overview]
Message-ID: <20230118211424.GA259217@bhelgaas> (raw)
In-Reply-To: <bug-216950-41252@https.bugzilla.kernel.org/>

On Wed, Jan 18, 2023 at 07:49:38PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216950
>            Summary: DisplayPort USB-C hub issue
>     Kernel Version: 6.2.0-rc3
> ...
> Created attachment 303624
>   --> https://bugzilla.kernel.org/attachment.cgi?id=303624&action=edit
> dmidecode + kern.log
> 
> I have HP 845 EliteBook G7 (Ryzen) and before 6.2.0-rc3 installation
> there was no issue with my laptop and HP docking station via USB-C.
> 
> This kernel display behaves weirdly. LCD monitor (connected to
> docking station via DisplayPort) wakes up only once after reboot.
> Second docking connection ends up with blank external screen and
> only restart helps.
> 
> Display manager detects extra screen and even newly launched apps
> land there.
> 
> I didn't have such issues with original distro kernel
> 5.16.15-76051615-generic

This report (which looks like a regression between
5.16.15-76051615-generic and 6.2.0-rc3) was raised against PCI, but I
don't see PCI issues in the logs.  Any DRM ideas?

Bjorn

           reply	other threads:[~2023-01-18 21:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-216950-41252@https.bugzilla.kernel.org/>]

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=20230118211424.GA259217@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=martii@interia.pl \
    --cc=regressions@lists.linux.dev \
    /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