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
