While booting and testing selftest cgroups and filesystem testing on arm64
dragonboard-410c the following kernel warnings / errors noticed and system
halted and did not recover with selftests Kconfig enabled running the kernel
Linux next tag next-20250804.
Regression Analysis:
- New regression? Ye
Regressions noticed while building x86_64 and i386 builds with clang-nightly
and clang-20 toolchains on the Linux next-20250725 tag.
First seen on the Linux next-20250725
Good: next-20250724
Bad: next-20250725
Regression Analysis:
- New regression? Yes
- Reproducibility? Yes
## Build regression
Regressions on boot failure observed in builds with CONFIG_PREEMPT_RT=y
and CONFIG_LAZY_PREEMPT=y enabled on multiple platforms running the
Linux next-20250710.
Kernel stalls and RCU preempt self-detected stalls reported.
Boot log shows CPU stalls and failure as below.
Test environments:
- Ampere
The following build warnings / errors noticed while building the selftest/ublk
with gcc-13 and clang-nightly toolchains on Linux next tree.
Please suggest if I am missing something in my build setup.
Regressions found on arm arm64 x86_64
- selftests ublk
Regression Analysis:
- New regression
On Tue, 17 Jun 2025 at 01:58, David Hildenbrand wrote:
>
> On 16.06.25 21:14, Christian Heusel wrote:
> > On 25/06/16 11:02PM, Naresh Kamboju wrote:
> >> The following test regressions noticed while running selftests/mm
> >> gup_longterm
> >> test case
The following build warnings were noticed while building selftests/mm
with clang nightly toolchain for arm64 and x86_64 architectures.
Regressions found on arm64 and x86_64
- Build/clang-nightly-lkftconfig-kselftest
Regression Analysis:
- New regression? Yes
- Reproducibility? Yes
Build reg
The following test regressions noticed while running selftests/mm gup_longterm
test cases on Dragonboard-845c, Dragonboard-410c, rock-pi-4, qemu-arm64 and
qemu-x86_64 this build have required selftest/mm/configs included and toolchain
is clang nightly.
Regressions found on Dragonboard-845c, Dragon
Regressions found on arm, arm64 and x86_64 building warnings with clang-20
and clang-nightly started from Linux next-20250603
Regressions found on arm, arm64 and x86_64
- selftests/filesystem
Regression Analysis:
- New regression? Yes
- Reproducible? Yes
First seen on the next-20250603
Good:
On Tue, 29 Apr 2025 at 23:31, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 6.1.136 release.
> There are 167 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.
>
> Re
path")
> Signed-off-by: Dan Carpenter
> ---
> Naresh, could you test this patch and see if it fixes the boot
> problems you saw?
Dan, This patch fixes the reported problem.
Tested-by: Naresh Kamboju
Links:
- https://lkft.validation.linaro.org/scheduler/job/8244118#L2441
>
On Thu, 3 Apr 2025 at 20:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 6.13.10 release.
> There are 23 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.
>
> Resp
As part of LKFT’s re-validation of known issues, we have observed that
the selftests: cgroup suite is consistently failing across almost all
LKFT-supported devices due to:
- Test timeouts (45 seconds limit reached)
- OOM-killer invocation
## Key Questions for Discussion:
- Would it be beneficia
On Wed, 12 Feb 2025 at 19:30, Marc Zyngier wrote:
>
> On Wed, 12 Feb 2025 11:41:38 +,
> Dan Carpenter wrote:
> >
> > On Tue, Feb 11, 2025 at 11:36:31AM +, Marc Zyngier wrote:
> > > For the crash at hand, which clearly shows nVHE, can you report
> > > whether the following hack fixes it fo
The kselftest-vDSO/vdso_test_abi test encounters failures when built
and executed using GCC-13 on armv7 architecture.
The issue has been observed on both TI X15 devices and QEMU-armv7.
Interestingly, the same test passes without any issues when built using
Clang-19.This failure is specific to GCC-
On Wed, 12 Feb 2025 at 17:11, Dan Carpenter wrote:
>
> On Tue, Feb 11, 2025 at 11:36:31AM +, Marc Zyngier wrote:
> > For the crash at hand, which clearly shows nVHE, can you report
> > whether the following hack fixes it for you?
> >
> > M.
>
> No luck, I'm afraid. It still crashes the
Regression on rk3399-rock-pi-4b while running kvm-unit-tests with
nvhe, protected and vhe mode with virtualization enabled.
First seen on next-20250120
Good: next-20250117
Bad: next-20250120 till today's next-20250210
This is always reproducible.
Regression on these devices with kernel command l
On Tue, 11 Feb 2025 at 14:53, Naresh Kamboju wrote:
>
> Regressions on arm64 Juno-r2 device while running LTP syscalls tests
> madvise01 warnings on the Linux next-20250210 tag.
>
> First seen on next-20250210
> Good: next-20250207
> Bad: next-20250210
>
> This regr
Regressions on arm64 Juno-r2 device while running LTP syscalls tests
madvise01 warnings on the Linux next-20250210 tag.
First seen on next-20250210
Good: next-20250207
Bad: next-20250210
This regression is reproducible with CONFIG_ARM64_64K_PAGES=y
Test regression: LTP madvise01 WARNING include/
The selftests: arm64: pac getting failed on FVP, Graviton-vm and Qemu-arm64
running Linux next-20250113..next-20250116.
Started noticing from next-20250113.
Bad: next-20250110
Bad: next-20250113
Test failed:
pac
global.pac_instructions_not_nop
global.pac_instructions_not_nop_generic
Reported-
On Sun, 5 Jan 2025 at 19:52, Sasha Levin wrote:
>
> I'm sorry, this is my bad: I haven't realized anyone else will be
> looking at these results...
>
> Naresh, I'm cheating and using this tree to bisect the issue you've
> originally reported in
> https://lore.kernel.org/all/ca+g9fyvcbvbabg+m7brkfp
The following kselftest rust builds failed on sashal/linus-next.git
due to following build warnings / errors.
Good: 829d8581c398a96deea1d6bc78578950347dcbec
Bad: b2d472701a703596889c3fd067fd8929aeffc4be
Build error:
--
warning: the feature `new_uninit` has been stable since 1.82.0 a
The Rust gcc builds failed due to following build warnings / errors on the
x86_64 and arm64 architectures with selftests/rust/config on the Linux
next-20241216...next-20241218.
First seen on the next-20241216 tag.
Good: next-20241213
Bad: next-20241216
Reported-by: Linux Kernel Functional Testing
[Gentle Reminder]
On Mon, 26 Aug 2024 at 18:50, Naresh Kamboju wrote:
>
> The following kernel warning is noticed on all arch and all devices while
> running selftests: core: unshare_test on Linux next-20240823 and
> next-20240826.
>
> First seen on next-20240823.
>
On Thu, 28 Nov 2024 at 08:42, Xuan Zhuo wrote:
>
> On Wed, 27 Nov 2024 13:30:59 +0530, Naresh Kamboju
> wrote:
> > The following build errors were noticed for arm64, arm, x86_64 and riscv.
> >
> > First seen on Sasha Linus-next 441d2975754ad94f3ce2e29f6
The following build errors were noticed for arm64, arm, x86_64 and riscv.
First seen on Sasha Linus-next 441d2975754ad94f3ce2e29f672824bc2dc5120c.
Good: 07e98e730a08081b6d0b5c3a173b0487c36ed27f
Bad: 441d2975754ad94f3ce2e29f672824bc2dc5120c
arm64, arm, riscv and x86_64:
build:
* clang-1
The QEMU-ARM64 boot has failed with the Linux next-20241031 tag.
The boot log shows warnings at clockevents_register_device and followed
by rcu_preempt detected stalls.
However, the system did not proceed far enough to reach the login prompt.
The fvp-aemva, Qemu-arm64, Qemu-armv7 and Qemu-riscv64
The following kselftest arm64 and FVP failed with Linux next-20241025 on
- Qemu-arm64
- FVP
running Linux next-20241025 kernel.
First seen on next-20241025
Good: next-20241024
BAD: next-20241025
kselftest-arm64, FVP
* arm64_check_buffer_fill
* arm64_check_mmap_options
* arm
Most of the tinyconfigs are failing on stable-rc linux-6.6.y.
Build errors:
--
aarch64-linux-gnu-ld: kernel/task_work.o: in function `task_work_add':
task_work.c:(.text+0x190): undefined reference to `irq_work_queue'
task_work.c:(.text+0x190): relocation truncated to fit:
R_AARCH64_CAL
On Thu, 24 Oct 2024 at 20:11, Naresh Kamboju wrote:
>
> Most of the tinyconfigs are failing on stable-rc linux-6.6.y.
>
> Build errors:
> --
> aarch64-linux-gnu-ld: kernel/task_work.o: in function `task_work_add':
> task_work.c:(.text+0x190): undefined re
On Wed, 2 Oct 2024 at 19:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 6.6.54 release.
> There are 538 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.
>
> Resp
On Tue, 17 Sept 2024 at 00:53, Miguel Ojeda
wrote:
>
> Hi Naresh,
>
> On Mon, Sep 16, 2024 at 9:17 PM Naresh Kamboju
> wrote:
> >
> > The x86 rust gcc builds failed on the Linux next-20240917 due to following
> > build
> > warnings / errors with rustgcc f
The x86 rust gcc builds failed on the Linux next-20240917 due to following build
warnings / errors with rustgcc for selftests rust builds.
First seen on next-20240917
Good: next-20240913
BAD: next-20240917
Reported-by: Linux Kernel Functional Testing
build log:
error: unknown unst
The following kernel rcu info generated while running the test case
selftests: memfd: run_fuse_test.sh on qemu-arm64 running Linux
next-20240902. The qemu-arm64 did not recover.
This build was created with kselftest merge configs.
Anders bisected this to,
# first bad commit:
[5fb9c98e9d8ddf
Hi Steven,
On Tue, 21 Nov 2023 at 02:06, Steven Rostedt wrote:
>
> On Thu, 16 Nov 2023 18:00:16 +0530
> Naresh Kamboju wrote:
>
> > Following kernel crash noticed while running selftests: ftrace on arm64
> > Juno-r2
> > device running stable-rc linux-6.6.y ker
Following kernel crash noticed while running selftests: ftrace on arm64 Juno-r2
device running stable-rc linux-6.6.y kernel.
This kernel crash is hard to reproduce.
Reported-by: Linux Kernel Functional Testing
kselftest: Running tests in ftrace
TAP version 13
1..1
# timeout set to 0
# selftests
ocument
> that as well.
>
> Link:
> https://lore.kernel.org/all/CA+G9fYu9GOEbD=rR5eMR-=HJ8H6rMsbzDC2ZY5=y50wpwae...@mail.gmail.com/
>
> Reported-by: Linux Kernel Functional Testing
> Reported-by: Naresh Kamboju
> Signed-off-by: Steven Rostedt (Google)
Tested-by: Linux Ker
On Mon, 30 Oct 2023 at 20:11, Steven Rostedt wrote:
>
> On Mon, 30 Oct 2023 12:37:08 +0530
> Naresh Kamboju wrote:
>
> >
> > I have tested the linux-trace.git trace/core and run selftests ftrace
> > the reported kernel panic [1] & [2] has been fixed but found
&
Hi Steven,
> Are you sure it was applied correctly?
Please ignore the build warnings / errors it was due to apply patch was
not successful.
> Perhaps check out the branch I
> have and let me know if you get the same errors.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
SurMgCepTxunSJf=MTe=6...@mail.gmail.com/
>
> Fixes: 5790b1fb3d672 ("eventfs: Remove eventfs_file and just use
> eventfs_inode")
> Reported-by: Linux Kernel Functional Testing
> Reported-by: Naresh Kamboju
> Reported-by: Beau Belgrave
> Signed-off-by: Steven Rostedt
SurMgCepTxunSJf=MTe=6...@mail.gmail.com/
>
> Fixes: 5790b1fb3d672 ("eventfs: Remove eventfs_file and just use
> eventfs_inode")
> Reported-by: Reported-by: Linux Kernel Functional Testing
In the above line "Reported-by:" is twice.
> Reported-by: Naresh Kamb
On Tue, 20 Apr 2021 at 19:47, Eric Dumazet wrote:
>
> On Tue, Apr 20, 2021 at 3:45 PM Naresh Kamboju
> wrote:
> >
> > Following kernel BUG reported on qemu-arm64 running linux next 20210420
> > the config is enabled with KASAN.
imit: none
[ 23.922914] ---[ end Kernel panic - not syncing: Oops: Fatal
exception in interrupt ]---
Reported-by: Naresh Kamboju
Full test log:
--
https://lkft.validation.linaro.org/scheduler/job/2555059#L646
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-202104
On Mon, 19 Apr 2021 at 18:50, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.114 release.
> There are 73 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.
>
> Res
On Mon, 19 Apr 2021 at 18:49, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.32 release.
> There are 103 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.
>
> Re
On Mon, 19 Apr 2021 at 18:39, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.16 release.
> There are 122 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.
>
> Re
make: *** [Makefile:222: __sub-make] Error 2
make: Target '__all' not remade because of errors.
Reported-by: Naresh Kamboju
steps to reproduce:
# TuxMake is a command line tool and Python library that provides
# portable and repeatable Linux kernel builds
On Thu, 15 Apr 2021 at 20:20, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.267 release.
> There are 38 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.
>
> Res
On Thu, 15 Apr 2021 at 20:23, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.267 release.
> There are 47 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.
>
> Res
On Thu, 15 Apr 2021 at 20:27, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.231 release.
> There are 68 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.
>
> Re
On Thu, 15 Apr 2021 at 20:29, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.188 release.
> There are 13 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.
>
> Re
On Thu, 15 Apr 2021 at 20:31, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.113 release.
> There are 18 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.
>
> Res
On Thu, 15 Apr 2021 at 20:33, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.31 release.
> There are 25 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.
>
> Res
On Thu, 15 Apr 2021 at 20:34, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.15 release.
> There are 23 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.
>
> Res
On Mon, 12 Apr 2021 at 14:13, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.187 release.
> There are 66 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.
>
> Re
On Mon, 12 Apr 2021 at 14:16, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.112 release.
> There are 111 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.
>
> Re
On Mon, 12 Apr 2021 at 14:23, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.30 release.
> There are 188 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.
>
> Re
On Mon, 12 Apr 2021 at 14:32, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.14 release.
> There are 210 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.
>
> Re
On Fri, 9 Apr 2021 at 15:26, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.266 release.
> There are 13 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.
>
> Resp
On Fri, 9 Apr 2021 at 15:25, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.266 release.
> There are 20 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.
>
> Resp
On Sat, 10 Apr 2021 at 01:43, Guenter Roeck wrote:
>
> On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.230 release.
> > There are 14 patches in this series, all will be posted as a response
> > to this one. If anyon
On Fri, 9 Apr 2021 at 15:27, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.230 release.
> There are 14 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.
>
> Res
On Fri, 9 Apr 2021 at 15:27, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.186 release.
> There are 18 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.
>
> Res
On Fri, 9 Apr 2021 at 15:29, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.111 release.
> There are 23 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.
>
> Resp
On Fri, 9 Apr 2021 at 15:30, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.29 release.
> There are 41 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.
>
> Resp
On Fri, 9 Apr 2021 at 15:32, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.13 release.
> There are 45 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.
>
> Resp
On Fri, 9 Apr 2021 at 23:17, Naresh Kamboju wrote:
>
> On Fri, 9 Apr 2021 at 21:49, Shyam Prasad wrote:
> >
> > Hi Naresh,
> >
> > AFAIK, this has been fixed in an updated patch last evening. Can you please
> > check if you're still seeing it?
>
&g
On Fri, 9 Apr 2021 at 21:49, Shyam Prasad wrote:
>
> Hi Naresh,
>
> AFAIK, this has been fixed in an updated patch last evening. Can you please
> check if you're still seeing it?
Please share the fix commit and subject here.
FYI,
This build error is still on today's Linux next tag 20210409.
-
On Fri, 9 Apr 2021 at 12:02, Chaitanya Kulkarni
wrote:
>
> On 4/8/21 23:24, Naresh Kamboju wrote:
> >> bio_offset(req->bio),
> >> GDROM_DMA_STARTADDR_REG);
> >> __raw_writel(block_cnt * GDROM_HARD_SECTOR, GDROM_DMA_LENG
Hi Chaitanya,
On Fri, 9 Apr 2021 at 11:01, Chaitanya Kulkarni
wrote:
>
> On 4/8/21 22:21, Naresh Kamboju wrote:
> > Linux next tag 20210408 architecture sh builds failed due to these errors.
> >
> > # to reproduce this build locally:
> >
> > make --sile
x/drivers/cdrom/gdrom.c:586:61: error: 'rq' undeclared
(first use in this function)
586 | __raw_writel(page_to_phys(bio_page(req->bio)) + bio_offset(rq->bio),
| ^~
Reported-by: Naresh Kamboju
Regressions found on sh:
"dns_query" [fs/cifs/cifs.ko] undefined
Reported-by: Naresh Kamboju
Regressions found on parisc:
- build/gcc-9-defconfig
- build/gcc-8-defconfig
- build/gcc-10-defconfig
Regressions found on sh:
- build/gcc-9-dreamcast_defconfig
- build/gcc-10-dreamcast_defconfig
- b
On Thu, 8 Apr 2021 at 15:17, Andy Shevchenko wrote:
>
> On Thu, Apr 8, 2021 at 11:33 AM Naresh Kamboju
> wrote:
> > On Thu, 8 Apr 2021 at 04:21, Andy Shevchenko
> > wrote:
> > > On Thu, Apr 8, 2021 at 12:38 AM Naresh Kamboju
> > > wrote:
> > >
On Thu, 8 Apr 2021 at 04:21, Andy Shevchenko wrote:
>
> On Thu, Apr 8, 2021 at 12:38 AM Naresh Kamboju
> wrote:
> >
> > While running kselftest recently added gpio gpio-sim.sh test case the
> > following
> > warning was triggered on Linux next tag 20210330
disabled at (5577): []
irq_exit+0x1b4/0x1c0
[ 143.377992] ---[ end trace bc3c86ef609281aa ]---
# 1.2. chip_name returns 'none' if the chip is still pending
Reported-by: Naresh Kamboju
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
On Mon, 5 Apr 2021 at 14:26, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.265 release.
> There are 28 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.
>
> Resp
On Mon, 5 Apr 2021 at 14:27, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.265 release.
> There are 35 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.
>
> Resp
On Mon, 5 Apr 2021 at 14:29, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.229 release.
> There are 52 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.
>
> Res
On Mon, 5 Apr 2021 at 14:31, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.185 release.
> There are 56 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.
>
> Res
On Mon, 5 Apr 2021 at 14:33, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.110 release.
> There are 74 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.
>
> Resp
On Mon, 5 Apr 2021 at 14:37, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.28 release.
> There are 126 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.
>
> Res
On Mon, 5 Apr 2021 at 14:43, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.12 release.
> There are 152 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.
>
> Res
] ---[ end trace bc3c86ef609281aa ]---
# 1.2. chip_name returns 'none' if the chip is still pending
Reported-by: Naresh Kamboju
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git describe: next-20210330
kernel-co
Small correction,
As per available test data the good tag is next-20210326.
GOOD: next-20210326
BAD: next-20210330
On Tue, 30 Mar 2021 at 22:19, Naresh Kamboju wrote:
>
> While running kselftest gpio on x86_64 and i386 the following warnings were
> noticed and the device did not recover
rc/kernel/fs/proc/generic.c:717 remove_proc_entry+0x1a8/0x1c0
Reported-by: Naresh Kamboju
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git describe: next-20210330
kernel-config:
http://snapshots.linaro.org/openembedded/lkft/lkf
On Mon, 29 Mar 2021 at 13:32, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.264 release.
> There are 33 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.
>
> Res
On Mon, 29 Mar 2021 at 13:33, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.264 release.
> There are 53 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.
>
> Res
On Mon, 29 Mar 2021 at 13:37, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.228 release.
> There are 59 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.
>
> Re
On Mon, 29 Mar 2021 at 13:40, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.184 release.
> There are 72 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.
>
> Re
On Mon, 29 Mar 2021 at 13:44, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.109 release.
> There are 111 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.
>
> Re
On Mon, 29 Mar 2021 at 15:44, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.27 release.
> There are 219 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.
>
> Re
On Mon, 29 Mar 2021 at 15:45, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.11 release.
> There are 252 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.
>
> Re
On Mon, 29 Mar 2021 at 14:10, Greg Kroah-Hartman
wrote:
>
> From: Anshuman Khandual
>
> [ Upstream commit 03aaf83fba6e5af08b5dd174c72edee9b7d9ed9b ]
>
> This overrides arch_get_mappable_range() on arm64 platform which will be
> used with recently added generic framework. It drops
> inside_linear
On Mon, 29 Mar 2021 at 13:49, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.27 release.
> There are 221 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.
>
> Re
On Mon, 29 Mar 2021 at 14:00, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.11 release.
> There are 254 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.
>
> Re
On Wed, 24 Mar 2021 at 15:10, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.26 release.
> There are 150 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.
>
> Re
On Tue, 23 Mar 2021 at 14:19, Naresh Kamboju wrote:
>
> On Mon, 22 Mar 2021 at 20:49, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.10.26 release.
> > There are 156 patches in this series, all will be posted as a response
fff8100
(relocation range: 0x8000-0xbfff)
steps to reproduce:
--
- cd /opt/kselftests/mainline/net/mptcp
- ./mptcp_join.sh || true
Reported-by: Naresh Kamboju
crash test link:
https://lkft.validation.linaro.org/scheduler/job/2436164
Re
On Mon, 22 Mar 2021 at 18:24, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.263 release.
> There are 14 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.
>
> Res
On Mon, 22 Mar 2021 at 18:25, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.263 release.
> There are 25 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.
>
> Res
On Mon, 22 Mar 2021 at 18:29, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.227 release.
> There are 43 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.
>
> Re
1 - 100 of 1031 matches
Mail list logo
