From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, stable@vger.kernel.org
Subject: Re: [PATCH 5.11 00/12] 5.11.1-rc1 review
Date: Wed, 24 Feb 2021 08:49:37 +0100 [thread overview]
Message-ID: <YDYFEYOs0RYIjOnc@kroah.com> (raw)
In-Reply-To: <6359a822-c0b2-75f7-40e3-c0c7bf002e3f@linuxfoundation.org>
On Tue, Feb 23, 2021 at 05:12:56PM -0700, Shuah Khan wrote:
> On 2/23/21 2:05 PM, Shuah Khan wrote:
> > On 2/22/21 5:12 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.11.1 release.
> > > There are 12 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Wed, 24 Feb 2021 12:07:46 +0000.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.11.1-rc1.gz
> > >
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > linux-5.11.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
> >
> > Compiled and booted on my test system. No dmesg regressions.
> >
> > I made some progress on the drm/amdgpu display and kepboard
> > problem.
> >
> > My system has
> > amdgpu: ATOM BIOS: 113-RENOIR-026
> >
> > I narrowed it down to the following as a possible lead to
> > start looking:
> > amdgpu 0000:0b:00.0: [drm] Cannot find any crtc or sizes
> >
>
> It is resolved now. A hot-unplugged/plugged the HDMI cable which
> triggered reset sequence. There might be link to AMD_DC_HDCP
> support, amdgpu_dm_atomic_commit changes that went into 5.10 and
> this behavior.
>
> I am basing this on not seeing the problem on Linux 5.4 and until
> Linux 5.10. In any case, I wish I know more, but life is back to
> normal now.
Great, thanks for testing and tracking this down.
greg k-h
next prev parent reply other threads:[~2021-02-24 7:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 12:12 [PATCH 5.11 00/12] 5.11.1-rc1 review Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 01/12] Xen/x86: dont bail early from clear_foreign_p2m_mapping() Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 02/12] Xen/x86: also check kernel mapping in set_foreign_p2m_mapping() Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 03/12] Xen/gntdev: correct dev_bus_addr handling in gntdev_map_grant_pages() Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 04/12] Xen/gntdev: correct error checking " Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 05/12] xen/arm: dont ignore return errors from set_phys_to_machine Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 06/12] xen-blkback: dont "handle" error by BUG() Greg Kroah-Hartman
2021-02-22 12:12 ` [PATCH 5.11 07/12] xen-netback: " Greg Kroah-Hartman
2021-02-22 12:13 ` [PATCH 5.11 08/12] xen-scsiback: " Greg Kroah-Hartman
2021-02-22 12:13 ` [PATCH 5.11 09/12] xen-blkback: fix error handling in xen_blkbk_map() Greg Kroah-Hartman
2021-02-22 12:13 ` [PATCH 5.11 10/12] tty: protect tty_write from odd low-level tty disciplines Greg Kroah-Hartman
2021-02-22 12:13 ` [PATCH 5.11 11/12] Bluetooth: btusb: Always fallback to alt 1 for WBS Greg Kroah-Hartman
2021-02-22 12:13 ` [PATCH 5.11 12/12] media: pwc: Use correct device for DMA Greg Kroah-Hartman
2021-02-22 19:40 ` [PATCH 5.11 00/12] 5.11.1-rc1 review Naresh Kamboju
2021-02-23 12:57 ` Greg Kroah-Hartman
2021-02-22 21:29 ` Guenter Roeck
2021-02-23 12:57 ` Greg Kroah-Hartman
2021-02-23 21:05 ` Shuah Khan
2021-02-24 0:12 ` Shuah Khan
2021-02-24 7:49 ` Greg Kroah-Hartman [this message]
2021-02-24 12:15 ` Jon Hunter
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=YDYFEYOs0RYIjOnc@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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.