This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +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/v4.x/stable-review/patch-4.19.278-rc... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y and the diffstat can be found below.
thanks,
greg k-h
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 4.19.278-rc3
Eric Dumazet edumazet@google.com ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping()
Kang Chen void0red@gmail.com nfc: fdp: add null check of devm_kmalloc_array in fdp_nci_i2c_read_device_properties
Shigeru Yoshida syoshida@redhat.com net: caif: Fix use-after-free in cfusbl_device_notify()
John Harrison John.C.Harrison@Intel.com drm/i915: Don't use BAR mappings for ring buffers with LLC
Tung Nguyen tung.q.nguyen@dektech.com.au tipc: improve function tipc_wait_for_cond()
Paul Elder paul.elder@ideasonboard.com media: ov5640: Fix analogue gain control
Alvaro Karsz alvaro.karsz@solid-run.com PCI: Add SolidRun vendor ID
Nathan Chancellor nathan@kernel.org macintosh: windfarm: Use unsigned type for 1-bit bitfields
Edward Humes aurxenon@lunos.org alpha: fix R_ALPHA_LITERAL reloc for large modules
xurui xurui@kylinos.cn MIPS: Fix a compilation issue
Nobuhiro Iwamatsu nobuhiro1.iwamatsu@toshiba.co.jp Revert "spi: mt7621: Fix an error message in mt7621_spi_probe()"
Bart Van Assche bvanassche@acm.org scsi: core: Remove the /proc/scsi/${proc_name} directory earlier
Masahiro Yamada yamada.masahiro@socionext.com kbuild: generate modules.order only in directories visited by obj-y/m
Masahiro Yamada yamada.masahiro@socionext.com kbuild: fix false-positive need-builtin calculation
Jan Kara jack@suse.cz udf: Detect system inodes linked into directory hierarchy
Jan Kara jack@suse.cz udf: Preserve link count of system files
Jan Kara jack@suse.cz udf: Remove pointless union in udf_inode_info
Steven J. Magnani steve.magnani@digidescorp.com udf: reduce leakage of blocks related to named streams
Jan Kara jack@suse.cz udf: Explain handling of load_nls() failure
Fedor Pchelkin pchelkin@ispras.ru nfc: change order inside nfc_se_io error path
Zhihao Cheng chengzhihao1@huawei.com ext4: zero i_disksize when initializing the bootloader inode
Ye Bin yebin10@huawei.com ext4: fix WARNING in ext4_update_inline_data
Ye Bin yebin10@huawei.com ext4: move where set the MAY_INLINE_DATA flag is set
Darrick J. Wong djwong@kernel.org ext4: fix another off-by-one fsmap error on 1k block filesystems
Eric Whitney enwlinux@gmail.com ext4: fix RENAME_WHITEOUT handling for inline directories
Andrew Cooper andrew.cooper3@citrix.com x86/CPU/AMD: Disable XSAVES on AMD family 0x17
Theodore Ts'o tytso@mit.edu fs: prevent out-of-bounds array speculation when closing a file descriptor
-------------
Diffstat:
Makefile | 4 +- arch/alpha/kernel/module.c | 4 +- arch/mips/include/asm/mach-rc32434/pci.h | 2 +- arch/x86/kernel/cpu/amd.c | 9 ++++ drivers/gpu/drm/i915/intel_ringbuffer.c | 4 +- drivers/macintosh/windfarm_lm75_sensor.c | 4 +- drivers/macintosh/windfarm_smu_sensors.c | 4 +- drivers/media/i2c/ov5640.c | 2 +- drivers/nfc/fdp/i2c.c | 4 ++ drivers/scsi/hosts.c | 2 + drivers/staging/mt7621-spi/spi-mt7621.c | 8 ++-- fs/ext4/fsmap.c | 2 + fs/ext4/inline.c | 1 - fs/ext4/inode.c | 7 ++- fs/ext4/ioctl.c | 1 + fs/ext4/namei.c | 13 +++--- fs/ext4/xattr.c | 3 ++ fs/file.c | 1 + fs/udf/directory.c | 2 +- fs/udf/file.c | 7 ++- fs/udf/ialloc.c | 14 +++--- fs/udf/inode.c | 76 ++++++++++++++++++++++---------- fs/udf/misc.c | 6 +-- fs/udf/namei.c | 7 ++- fs/udf/partition.c | 2 +- fs/udf/super.c | 12 ++++- fs/udf/symlink.c | 2 +- fs/udf/udf_i.h | 12 ++--- include/linux/pci_ids.h | 2 + net/caif/caif_usb.c | 3 ++ net/ipv6/ila/ila_xlat.c | 1 + net/nfc/netlink.c | 2 +- net/tipc/socket.c | 2 +- scripts/Makefile.build | 4 +- 34 files changed, 150 insertions(+), 79 deletions(-)
Hello Greg,
From: Greg Kroah-Hartman gregkh@linuxfoundation.org Sent: 16 March 2023 09:42
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +0000. Anything received after that time might be too late.
CIP configurations built and booted with Linux 4.19.278-rc3 (0233a363477c): https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/80... https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linu...
Tested-by: Chris Paterson (CIP) chris.paterson2@renesas.com
Kind regards, Chris
On Thu, Mar 16, 2023 at 10:42:14AM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 431 pass: 431 fail: 0
Tested-by: Guenter Roeck linux@roeck-us.net
Guenter
On Thu, 16 Mar 2023 at 15:12, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +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/v4.x/stable-review/patch-4.19.278-rc... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.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
## Build * kernel: 4.19.278-rc3 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-4.19.y * git commit: 0233a363477c634e1ba87559073eeab4b8fac88e * git describe: v4.19.276-32-g0233a363477c * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19....
## Test Regressions (compared to v4.19.276)
## Metric Regressions (compared to v4.19.276)
## Test Fixes (compared to v4.19.276)
## Metric Fixes (compared to v4.19.276)
## Test result summary total: 90635, pass: 68730, fail: 3044, skip: 18533, xfail: 328
## Build Summary * arc: 10 total, 10 passed, 0 failed * arm: 201 total, 200 passed, 1 failed * arm64: 42 total, 41 passed, 1 failed * i386: 29 total, 28 passed, 1 failed * mips: 42 total, 42 passed, 0 failed * parisc: 12 total, 12 passed, 0 failed * powerpc: 51 total, 51 passed, 0 failed * s390: 15 total, 15 passed, 0 failed * sh: 24 total, 24 passed, 0 failed * sparc: 12 total, 12 passed, 0 failed * x86_64: 37 total, 36 passed, 1 failed
## Test suites summary * boot * fwts * kselftest-android * kselftest-arm64 * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers-dma-buf * kselftest-efivarfs * kselftest-filesystems * kselftest-filesystems-binderfs * kselftest-firmware * kselftest-fpu * kselftest-ftrace * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-net * kselftest-net-forwarding * kselftest-net-mptcp * kselftest-netfilter * kselftest-nsfs * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-vm * kselftest-x86 * kselftest-zram * kunit * kvm-unit-tests * libhugetlbfs * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-open-posix-tests * ltp-pty * ltp-sched * ltp-securebits * ltp-smoke * ltp-syscalls * ltp-tracing * network-basic-tests * packetdrill * rcutorture * v4l2-compliance * vdso
-- Linaro LKFT https://lkft.linaro.org
Hi Greg,
On Thu, Mar 16, 2023 at 10:42:14AM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +0000. Anything received after that time might be too late.
Build test (gcc version 11.3.1 20230311): mips: 63 configs -> no failure arm: 115 configs -> no failure arm64: 2 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Boot test: x86_64: Booted on qemu. No regression. [1]
Boot Regression on test laptop: Only black screen but ssh worked, so from the dmesg it seems i915 failed.
[ 3.538702] ------------[ cut here ]------------ [ 3.538703] WARN_ON(!list_empty(&b->signals)) [ 3.538765] WARNING: CPU: 3 PID: 137 at drivers/gpu/drm/i915/intel_breadcrumbs.c:888 intel_engine_fini_breadcrumbs+0xc5/0xd0 [i915] [ 3.538766] Modules linked in: crc32c_intel psmouse ahci i2c_i801 libahci i915(+) libata i2c_algo_bit scsi_mod lpc_ich drm_kms_helper ehci_pci sdhci_pci cqhci sdhci ehci_hcd mmc_core usbcore drm e1000e(+) usb_common video [ 3.538777] CPU: 3 PID: 137 Comm: systemd-udevd Not tainted 4.19.278-rc3-0233a363477c+ #1 [ 3.538777] Hardware name: LENOVO 4287CTO/4287CTO, BIOS 8DET68WW (1.38 ) 04/11/2013 [ 3.538815] RIP: 0010:intel_engine_fini_breadcrumbs+0xc5/0xd0 [i915] [ 3.538817] Code: 98 59 6e c0 48 c7 c7 11 51 6d c0 e8 98 21 73 d5 0f 0b e9 6f ff ff ff 48 c7 c6 d8 5a 6e c0 48 c7 c7 11 51 6d c0 e8 7e 21 73 d5 <0f> 0b e9 68 ff ff ff 0f 1f 40 00 66 66 66 66 90 41 57 41 56 41 55 [ 3.538818] RSP: 0018:ffffb1930113bb48 EFLAGS: 00010286 [ 3.538819] RAX: 0000000000000000 RBX: ffff8bc9c6828000 RCX: 0000000000000029 [ 3.538820] RDX: 0000000000000000 RSI: ffffffff979e9320 RDI: 0000000000000246 [ 3.538821] RBP: ffff8bca5e9b8000 R08: 284e4f5f4e524157 R09: 6d655f7473696c21 [ 3.538821] R10: 3e2d622628797470 R11: 29736c616e676973 R12: 00000000fffffffa [ 3.538822] R13: ffff8bc9c681d780 R14: 0000000000000000 R15: ffff8bca5fabe000 [ 3.538823] FS: 00007f097ff6a8c0(0000) GS:ffff8bcad60c0000(0000) knlGS:0000000000000000 [ 3.538824] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.538825] CR2: 00007f09804fe8cc CR3: 000000019df3e001 CR4: 00000000000606e0 [ 3.538826] Call Trace: [ 3.538866] intel_engine_cleanup_common+0x4f/0x160 [i915] [ 3.538904] intel_init_ring_buffer+0xcc/0xf0 [i915] [ 3.538940] intel_engines_init+0x46/0xb0 [i915] [ 3.538976] i915_gem_init+0x1d4/0x520 [i915] [ 3.539009] i915_driver_load+0xb1d/0xdb0 [i915] [ 3.539013] local_pci_probe+0x43/0x90 [ 3.539015] pci_device_probe+0x10a/0x1a0 [ 3.539019] really_probe+0x247/0x3d0 [ 3.539021] driver_probe_device+0xb6/0x100 [ 3.539022] __driver_attach+0x113/0x120 [ 3.539023] ? driver_probe_device+0x100/0x100 [ 3.539026] bus_for_each_dev+0x78/0xc0 [ 3.539028] bus_add_driver+0x16a/0x220 [ 3.539030] driver_register+0x8f/0xe0 [ 3.539031] ? 0xffffffffc07aa000 [ 3.539033] do_one_initcall+0x46/0x1d0 [ 3.539037] ? kernel_read_file+0x16a/0x1a0 [ 3.539040] ? _cond_resched+0x16/0x40 [ 3.539042] ? kmem_cache_alloc_trace+0x171/0x1d0 [ 3.539044] do_init_module+0x4e/0x270 [ 3.539046] __se_sys_finit_module+0xb1/0x110 [ 3.539049] do_syscall_64+0x55/0xf0 [ 3.539050] entry_SYSCALL_64_after_hwframe+0x5c/0xc1 [ 3.539052] RIP: 0033:0x7f09804222e9 [ 3.539053] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 77 8b 0d 00 f7 d8 64 89 01 48 [ 3.539054] RSP: 002b:00007ffca2100948 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 3.539055] RAX: ffffffffffffffda RBX: 0000564e2d018470 RCX: 00007f09804222e9 [ 3.539056] RDX: 0000000000000000 RSI: 00007f09805bfe2d RDI: 000000000000000e [ 3.539057] RBP: 0000000000020000 R08: 0000000000000000 R09: 0000564e2cffe480 [ 3.539057] R10: 000000000000000e R11: 0000000000000246 R12: 00007f09805bfe2d [ 3.539058] R13: 0000000000000000 R14: 0000564e2d017720 R15: 0000564e2d018470 [ 3.539060] ---[ end trace 2dc2b0b9c81e2ead ]--- [ 3.554929] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock [ 3.563955] ------------[ cut here ]------------ [ 3.563990] WARNING: CPU: 2 PID: 137 at drivers/gpu/drm/drm_mode_config.c:444 drm_mode_config_cleanup.cold+0x32/0x6b [drm] [ 3.563991] Modules linked in: crc32c_intel psmouse ahci i2c_i801 libahci i915(+) libata i2c_algo_bit scsi_mod lpc_ich drm_kms_helper ehci_pci sdhci_pci cqhci sdhci ehci_hcd mmc_core usbcore drm e1000e(+) usb_common video [ 3.563998] CPU: 2 PID: 137 Comm: systemd-udevd Tainted: G W 4.19.278-rc3-0233a363477c+ #1 [ 3.563999] Hardware name: LENOVO 4287CTO/4287CTO, BIOS 8DET68WW (1.38 ) 04/11/2013 [ 3.564011] RIP: 0010:drm_mode_config_cleanup.cold+0x32/0x6b [drm] [ 3.564012] Code: 9f 4b a0 d5 0f 0b e9 bc 55 ff ff 48 c7 c7 c8 83 34 c0 e8 8c 4b a0 d5 0f 0b e9 f2 54 ff ff 48 c7 c7 c8 83 34 c0 e8 79 4b a0 d5 <0f> 0b 48 89 e6 48 89 ef e8 91 e4 fe ff 48 89 e7 e8 a9 e6 fe ff 48 [ 3.564013] RSP: 0018:ffffb1930113bb78 EFLAGS: 00010246 [ 3.564014] RAX: 0000000000000024 RBX: ffff8bca5e9b8368 RCX: 0000000000000299 [ 3.564015] RDX: 0000000000000000 RSI: 0000000000000092 RDI: 0000000000000247 [ 3.564016] RBP: ffff8bca5e9b8000 R08: 0000000000000299 R09: 0000000000000004 [ 3.564017] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8bca5e9b8370 [ 3.564017] R13: ffff8bca5e9bc9e8 R14: 00000000fffffffa R15: ffff8bca5fabe000 [ 3.564019] FS: 00007f097ff6a8c0(0000) GS:ffff8bcad6080000(0000) knlGS:0000000000000000 [ 3.564019] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.564020] CR2: 0000564e2d0060b0 CR3: 000000019df3e002 CR4: 00000000000606e0 [ 3.564021] Call Trace: [ 3.564068] intel_modeset_cleanup+0xbc/0x130 [i915] [ 3.564102] i915_driver_load+0xb72/0xdb0 [i915] [ 3.564104] local_pci_probe+0x43/0x90 [ 3.564106] pci_device_probe+0x10a/0x1a0 [ 3.564109] really_probe+0x247/0x3d0 [ 3.564110] driver_probe_device+0xb6/0x100 [ 3.564112] __driver_attach+0x113/0x120 [ 3.564113] ? driver_probe_device+0x100/0x100 [ 3.564115] bus_for_each_dev+0x78/0xc0 [ 3.564117] bus_add_driver+0x16a/0x220 [ 3.564118] driver_register+0x8f/0xe0 [ 3.564119] ? 0xffffffffc07aa000 [ 3.564121] do_one_initcall+0x46/0x1d0 [ 3.564123] ? kernel_read_file+0x16a/0x1a0 [ 3.564125] ? _cond_resched+0x16/0x40 [ 3.564127] ? kmem_cache_alloc_trace+0x171/0x1d0 [ 3.564129] do_init_module+0x4e/0x270 [ 3.564130] __se_sys_finit_module+0xb1/0x110 [ 3.564133] do_syscall_64+0x55/0xf0 [ 3.564134] entry_SYSCALL_64_after_hwframe+0x5c/0xc1 [ 3.564135] RIP: 0033:0x7f09804222e9 [ 3.564137] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 77 8b 0d 00 f7 d8 64 89 01 48 [ 3.564137] RSP: 002b:00007ffca2100948 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 3.564139] RAX: ffffffffffffffda RBX: 0000564e2d018470 RCX: 00007f09804222e9 [ 3.564139] RDX: 0000000000000000 RSI: 00007f09805bfe2d RDI: 000000000000000e [ 3.564140] RBP: 0000000000020000 R08: 0000000000000000 R09: 0000564e2cffe480 [ 3.564141] R10: 000000000000000e R11: 0000000000000246 R12: 00007f09805bfe2d [ 3.564141] R13: 0000000000000000 R14: 0000564e2d017720 R15: 0000564e2d018470 [ 3.564143] ---[ end trace 2dc2b0b9c81e2eae ]--- [ 3.564156] [drm:drm_mode_config_cleanup.cold [drm]] *ERROR* connector LVDS-1 leaked! [ 3.599840] i915 0000:00:02.0: Device initialization failed (-6)
[1]. https://openqa.qa.codethink.co.uk/tests/3130
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
On Fri, Mar 17, 2023 at 10:23:42AM +0000, Sudip Mukherjee wrote:
Hi Greg,
On Thu, Mar 16, 2023 at 10:42:14AM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +0000. Anything received after that time might be too late.
Build test (gcc version 11.3.1 20230311): mips: 63 configs -> no failure arm: 115 configs -> no failure arm64: 2 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Boot test: x86_64: Booted on qemu. No regression. [1]
Boot Regression on test laptop: Only black screen but ssh worked, so from the dmesg it seems i915 failed.
Can you bisect this?
Hi Greg,
On Fri, 17 Mar 2023 at 12:55, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Fri, Mar 17, 2023 at 10:23:42AM +0000, Sudip Mukherjee wrote:
Hi Greg,
On Thu, Mar 16, 2023 at 10:42:14AM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +0000. Anything received after that time might be too late.
Build test (gcc version 11.3.1 20230311): mips: 63 configs -> no failure arm: 115 configs -> no failure arm64: 2 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Boot test: x86_64: Booted on qemu. No regression. [1]
Boot Regression on test laptop: Only black screen but ssh worked, so from the dmesg it seems i915 failed.
Can you bisect this?
There was no need to bisect. Only one i915 related commit was there and reverting that has fixed it for me.
9a0789a26289 ("drm/i915: Don't use BAR mappings for ring buffers with LLC") commit 85636167e3206c3fbd52254fc432991cc4e90194 upstream.
On Fri, Mar 17, 2023 at 01:21:03PM +0000, Sudip Mukherjee wrote:
Hi Greg,
On Fri, 17 Mar 2023 at 12:55, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Fri, Mar 17, 2023 at 10:23:42AM +0000, Sudip Mukherjee wrote:
Hi Greg,
On Thu, Mar 16, 2023 at 10:42:14AM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.278 release. There are 27 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 Sat, 18 Mar 2023 09:41:20 +0000. Anything received after that time might be too late.
Build test (gcc version 11.3.1 20230311): mips: 63 configs -> no failure arm: 115 configs -> no failure arm64: 2 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Boot test: x86_64: Booted on qemu. No regression. [1]
Boot Regression on test laptop: Only black screen but ssh worked, so from the dmesg it seems i915 failed.
Can you bisect this?
There was no need to bisect. Only one i915 related commit was there and reverting that has fixed it for me.
9a0789a26289 ("drm/i915: Don't use BAR mappings for ring buffers with LLC") commit 85636167e3206c3fbd52254fc432991cc4e90194 upstream.
Unfortunately, the bad patch made it into v4.19.278 anyway, breaking that release for all affected users (i915 with LLC support). That has been fixed in v4.19.279, but it is still unfortunate that the patch made it into the release even though it was reported that it is problematic.
I don't know what went wrong here, but it would be great if that kind of problem could be avoided in the future.
Guenter
-
Chris Paterson -
Greg Kroah-Hartman -
Guenter Roeck -
Naresh Kamboju -
Sudip Mukherjee