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.... 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
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 5.11.1-rc1
Matwey V. Kornilov matwey@sai.msu.ru media: pwc: Use correct device for DMA
Trent Piepho tpiepho@gmail.com Bluetooth: btusb: Always fallback to alt 1 for WBS
Linus Torvalds torvalds@linux-foundation.org tty: protect tty_write from odd low-level tty disciplines
Jan Beulich jbeulich@suse.com xen-blkback: fix error handling in xen_blkbk_map()
Jan Beulich jbeulich@suse.com xen-scsiback: don't "handle" error by BUG()
Jan Beulich jbeulich@suse.com xen-netback: don't "handle" error by BUG()
Jan Beulich jbeulich@suse.com xen-blkback: don't "handle" error by BUG()
Stefano Stabellini stefano.stabellini@xilinx.com xen/arm: don't ignore return errors from set_phys_to_machine
Jan Beulich jbeulich@suse.com Xen/gntdev: correct error checking in gntdev_map_grant_pages()
Jan Beulich jbeulich@suse.com Xen/gntdev: correct dev_bus_addr handling in gntdev_map_grant_pages()
Jan Beulich jbeulich@suse.com Xen/x86: also check kernel mapping in set_foreign_p2m_mapping()
Jan Beulich jbeulich@suse.com Xen/x86: don't bail early from clear_foreign_p2m_mapping()
-------------
Diffstat:
Makefile | 4 ++-- arch/arm/xen/p2m.c | 6 ++++-- arch/x86/xen/p2m.c | 15 +++++++-------- drivers/block/xen-blkback/blkback.c | 32 ++++++++++++++++++-------------- drivers/bluetooth/btusb.c | 20 ++++++-------------- drivers/media/usb/pwc/pwc-if.c | 22 +++++++++++++--------- drivers/net/xen-netback/netback.c | 4 +--- drivers/tty/tty_io.c | 5 ++++- drivers/xen/gntdev.c | 37 ++++++++++++++++++++----------------- drivers/xen/xen-scsiback.c | 4 ++-- include/xen/grant_table.h | 1 + 11 files changed, 78 insertions(+), 72 deletions(-)
On Mon, 22 Feb 2021 at 17:43, Greg Kroah-Hartman gregkh@linuxfoundation.org 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.... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
NOTE: 1) We (LKFT) have upgraded clang-10 to clang-12 builds and following three new configs enabled. CONFIG_CC_HAS_ASM_GOTO_OUTPUT=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_HAVE_KCSAN_COMPILER=y
2) on qemu_x86_64_clang-12 a large number of LTP tests reported failures on stable-rc 5.4, 5.10, 5.11 and Linux mainline. reported link, https://lore.kernel.org/lkml/CA+G9fYuE4ELVDju=LESHnphL4Z2DT5YQjdh9rNgr5D1x5g...
Summary ------------------------------------------------------------------------
kernel: 5.11.1-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.11.y git commit: 6380656c9227c27a989f750aa7a0c81039d28607 git describe: v5.11-13-g6380656c9227 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.11.y/build/v5.11-...
No regressions (compared to build v5.11)
No fixes (compared to build v5.11)
Ran 52054 total tests in the following environments and test suites.
Environments -------------- - arc - arm - arm64 - dragonboard-410c - dragonboard-845c - hi6220-hikey - i386 - juno-64k_page_size - juno-r2 - juno-r2-compat - juno-r2-kasan - mips - nxp-ls2088 - nxp-ls2088-64k_page_size - parisc - powerpc - qemu-arm-clang - qemu-arm64-clang - qemu-arm64-kasan - qemu-x86_64-clang - qemu-x86_64-kasan - qemu-x86_64-kcsan - qemu_arm - qemu_arm64 - qemu_arm64-compat - qemu_i386 - qemu_x86_64 - qemu_x86_64-compat - riscv - s390 - sh - sparc - x15 - x86 - x86-kasan - x86_64
Test Suites ----------- * build * linux-log-parser * install-android-platform-tools-r2600 * kselftest-android * kselftest-bpf * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-lkdtm * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-dio-tests * ltp-fs-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-securebits-tests * ltp-tracing-tests * perf * kvm-unit-tests * libhugetlbfs * ltp-controllers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-ipc-tests * ltp-sched-tests * fwts * kselftest-intel_pstate * kselftest-livepatch * kselftest-net * kselftest-netfilter * kselftest-nsfs * kselftest-ptrace * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-zram * ltp-syscalls-tests * network-basic-tests * v4l2-compliance * kselftest-efivarfs * kselftest-filesystems * kselftest-firmware * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-vm * kselftest-x86 * ltp-open-posix-tests * rcutorture * kunit
On Tue, Feb 23, 2021 at 01:10:19AM +0530, Naresh Kamboju wrote:
On Mon, 22 Feb 2021 at 17:43, Greg Kroah-Hartman gregkh@linuxfoundation.org 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.... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
Thanks for testing them all and letting me know.
greg k-h
On Mon, Feb 22, 2021 at 01:12:52PM +0100, 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.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 435 pass: 435 fail: 0
Tested-by: Guenter Roeck linux@roeck-us.net
Guenter
On Mon, Feb 22, 2021 at 01:29:17PM -0800, Guenter Roeck wrote:
On Mon, Feb 22, 2021 at 01:12:52PM +0100, 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.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 435 pass: 435 fail: 0
Tested-by: Guenter Roeck linux@roeck-us.net
Thanks for testing them all and letting me know.
greg k-h
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.... 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
Tested-by: Shuah Khan skhan@linuxfoundation.org
thanks, -- Shuah
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....
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.
When I hot-unplugged/plugged the cable, saw the following dmesg:
amdgpu 0000:0b:00.0: [drm] fb0: amdgpudrmfb frame buffer device kernel: [ 6704.580326] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out kernel: [ 6773.444316] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out kernel: [ 6783.684306] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:55:plane-3] flip_done timed out
The following
WARN_ON(acrtc_attach->pflip_status != AMDGPU_FLIP_NONE); fires:
kernel: [ 6783.750035] WARNING: CPU: 7 PID: 190 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7754 amdgpu_dm_atomic_commit_tail+0x2542/0x25d0 [amdgpu] Feb 23 16:20:39 shuah-IC5 kernel: [ 6783.750392] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c rfcomm ccm cmac algif_hash algif_skcipher af_alg bnep intel_rapl_msr intel_rapl_common amdgpu edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel kvm_amd snd_intel_dspcfg snd_hda_codec kvm snd_hda_core ath10k_pci snd_hwdep snd_pcm crct10dif_pclmul ath10k_core ghash_clmulni_intel ath iommu_v2 snd_seq_midi gpu_sched aesni_intel snd_seq_midi_event drm_ttm_helper mac80211 ttm snd_rawmidi btusb drm_kms_helper crypto_simd btrtl snd_seq cryptd btbcm rtsx_usb_ms cec glue_helper btintel snd_seq_device snd_timer rapl memstick rc_core bluetooth cfg80211 i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect snd_rn_pci_acp3x ecdh_generic wmi_bmof sysimgblt efi_pstore soundcore ccp joydev ecc k10temp input_leds snd_pci_acp3x libarc4 mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 Feb 23 16:20:39 shuah-IC5 kernel: [ 6783.750506] hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb nvme crc32_pclmul i2c_piix4 r8169 nvme_core ahci xhci_pci realtek libahci xhci_pci_renesas wmi video gpio_amdpt gpio_generic
kernel: [ 6783.750532] CPU: 7 PID: 190 Comm: kworker/7:1 Not tainted 5.11.1 #1 kernel: [ 6783.750537] Hardware name: LENOVO 90Q30008US/3728, BIOS O4ZKT1CA 09/16/2020 kernel: [ 6783.750541] Workqueue: events dm_irq_work_func [amdgpu] kernel: [ 6783.750859] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2542/0x25d0 [amdgpu] kernel: [ 6783.751159] Code: a0 fd ff ff 01 c7 85 9c fd ff ff 37 00 00 00 c7 85 a4 fd ff ff 20 00 00 00 e8 ca ef 12 00 e9 e9 fa ff ff 0f 0b e9 39 f9 ff ff <0f> 0b e9 88 f9 ff ff 0f 0b 0f 0b e9 9e f9 ff ff 49 8b 06 41 0f b6 kernel: [ 6783.751162] RSP: 0018:ffffac390068fa48 EFLAGS: 00010002 kernel: [ 6783.751167] RAX: 0000000000000002 RBX: 0000000000000004 RCX: ffff9604442d7918 kernel: [ 6783.751169] RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff960444a80188 kernel: [ 6783.751172] RBP: ffffac390068fd48 R08: 0000000000000005 R09: 0000000000000000 kernel: [ 6783.751174] R10: ffffac390068f998 R11: ffffac390068f99c R12: 0000000000000297 kernel: [ 6783.751176] R13: ffff96048d131a00 R14: ffff9604442d7800 R15: ffff96048da29c00 kernel: [ 6783.751179] FS: 0000000000000000(0000) GS:ffff96073f1c0000(0000) knlGS:0000000000000000 kernel: [ 6783.751182] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: [ 6783.751185] CR2: 00005612d2a1a000 CR3: 0000000030010000 CR4: 0000000000350ee0 kernel: [ 6783.751188] Call Trace: kernel: [ 6783.751197] ? irq_work_queue+0x2a/0x40 kernel: [ 6783.751205] ? vprintk_emit+0x139/0x240 kernel: [ 6783.751218] commit_tail+0x99/0x130 [drm_kms_helper] kernel: [ 6783.751247] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper] kernel: [ 6783.751273] drm_atomic_commit+0x4a/0x50 [drm] kernel: [ 6783.751323] dm_restore_drm_connector_state+0xf3/0x170 [amdgpu] kernel: [ 6783.751628] handle_hpd_irq+0x11a/0x150 [amdgpu] kernel: [ 6783.751923] dm_irq_work_func+0x4e/0x60 [amdgpu] kernel: [ 6783.752018] process_one_work+0x220/0x3c0 kernel: [ 6783.752018] worker_thread+0x53/0x420 kernel: [ 6783.752018] kthread+0x12f/0x150 kernel: [ 6783.752018] ? process_one_work+0x3c0/0x3c0 kernel: [ 6783.752018] ? __kthread_bind_mask+0x70/0x70 kernel: [ 6783.752018] ret_from_fork+0x22/0x30
thanks, -- Shuah
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....
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
On Mon, 22 Feb 2021 13:12:52 +0100, 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.... 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
All tests passing for Tegra ...
Test results for stable-v5.11: 12 builds: 12 pass, 0 fail 26 boots: 26 pass, 0 fail 65 tests: 65 pass, 0 fail
Linux version: 5.11.1-rc1-g6380656c9227 Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra194-p2972-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Tested-by: Jon Hunter jonathanh@nvidia.com
Jon
-
Greg Kroah-Hartman -
Guenter Roeck -
Jon Hunter -
Naresh Kamboju -
Shuah Khan