On Wed, 4 Dec 2024 at 19:24, Naresh Kamboju wrote:
>
> On Tue, 3 Dec 2024 at 20:04, Greg Kroah-Hartman
> wrote:
> >
> > --
> > Note, this is the LAST 4.19.y kernel to be released. After this one, it
> > is end-of-life. It's been 6 years
On Tue, 3 Dec 2024 at 20:04, Greg Kroah-Hartman
wrote:
>
> --
> Note, this is the LAST 4.19.y kernel to be released. After this one, it
> is end-of-life. It's been 6 years, everyone should have moved off of it
> by now.
> --
>
> This is the start of the stable rev
Following build warnings / errors noticed on Linux next-20240429 tag on the
arm64, arm and riscv with gcc-8 and gcc-13 builds pass.
Reported-by: Linux Kernel Functional Testing
Commit id:
b58a0bc904ff nouveau: add command-line GSP-RM registry support
Buids:
--
gcc-8-arm64-defconfig - Fail
On Thu, 11 Apr 2024 at 15:30, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.312 release.
> There are 175 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.
>
> R
On Tue, 12 Mar 2024 at 22:33, Guenter Roeck wrote:
> This series is based on the RFC patch and subsequent discussion at
> https://patchwork.kernel.org/project/linux-kselftest/patch/02546e59-1afe-4b08-ba81-d94f3b691c9a@moroto.mountain/
> and offers a more comprehensive solution of the problem di
Hi Jani and Benjamin,
On Mon, 4 Mar 2024 at 15:31, Jani Nikula wrote:
>
> On Mon, 04 Mar 2024, Jani Nikula wrote:
> > Removal of the backlight include from fb.h uncovered an implicit
> > dependency in powerpc asm/backlight.h. Add the explicit include.
> >
> &g
The powerpc ppc6xx_defconfig builds failed on today's Linux next tag
next-20240304.
Reported-by: Linux Kernel Functional Testing
Build log:
-
drivers/video/fbdev/chipsfb.c: In function 'chipsfb_pci_init':
drivers/video/fbdev/chipsfb.c:401:31: error: invalid use of undefined
type 'struct
The arm defconfig builds failed on today's Linux next tag next-20240304.
Build log:
-
ERROR: modpost: "__aeabi_uldivmod"
[drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined!
Steps to reproduce:
# tuxmake --runtime podman --target-arch arm --toolchain clang-17
--kconfig defconfig LLVM=1
The Kunit drm_plane_helper failed on all devices running Linux next-20231204
## Test Regressions (compared to next-20231201)
* qemu-armv7, kunit and
* x86, kunit
- drm_test_check_invalid_plane_state_downscaling_invalid
- drm_test_check_invalid_plane_state_drm_plane_helper
- drm_test_check_in
On Mon, 30 Oct 2023 at 14:33, Dan Carpenter wrote:
>
> We have started printing more and more intentional stack traces. Whether
> it's testing KASAN is able to detect use after frees or it's part of a
> kunit test.
>
> These stack traces can be problematic. They suddenly show up as a new
> failu
Following kasan bug was noticed on arm64 bcm2711-rpi-4-b device running
Linux next 6.6.0-rc5-next-20231011 with given config.
This was first noticed on 6.6.0-rc2-next-20230918.
This is an intermittent issue.
Links to build and test logs provided.
Reported-by: Linux Kernel Functional Testing
Boo
On Wed, 20 Sept 2023 at 14:25, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.257 release.
> There are 367 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.
>
> R
On Sun, 23 Jul 2023 at 03:36, Nathan Chancellor wrote:
>
> Hi Christian,
>
> On Tue, Jul 11, 2023 at 03:31:17PM +0200, Christian König wrote:
> > This adds the infrastructure for an execution context for GEM buffers
> > which is similar to the existing TTMs execbuf util and intended to replace
> >
Linux next-20230523 and next-20230524 the x86_64 and i386 builds failed
with clang.
Reported-by: Linux Kernel Functional Testing
make --silent --keep-going \
--jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=x86_64 \
SRCARCH=x86 CROSS_COMPILE=x86_64-linux-gnu- \
'HOSTCC=sccache
Hi Nathan,
On Mon, 23 Jan 2023 at 21:41, Nathan Chancellor wrote:
>
> Hi Naresh,
>
> On Mon, Jan 23, 2023 at 07:28:10PM +0530, Naresh Kamboju wrote:
> > FYI,
> > [ please provide comments, feedback and improvements on build/ ltp smoke
> > tests ]
> >
> &
rivers/s390/net/qeth_l3_main.o
`.exit.text' referenced in section `__bug_table' of
drivers/s390/net/qeth_l3_main.o: defined in discarded section
`.exit.text' of drivers/s390/net/qeth_l3_main.o
s390x-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion
fail ../../bfd/elf64-s390.c:3349
make[2
Following build regression noticed on Linux next-20230118.
Regressions found on arm:
- build/gcc-8-imx_v6_v7_defconfig
- build/gcc-12-imx_v6_v7_defconfig
- build/clang-15-imx_v6_v7_defconfig
- build/clang-nightly-imx_v6_v7_defconfig
Reported-by: Linux Kernel Functional Testing
W
[ please ignore this email if this regression already reported ]
Today's Linux next tag next-20230110 boot passes with defconfig but
boot fails with
defconfig + kselftest merge config on arm64 devices and qemu-arm64.
Reported-by: Linux Kernel Functional Testing
We are bisecting this problem and
Following arm64 kunit enabled build failed with gcc-12.
ERROR: modpost: "kunit_running" [drivers/gpu/drm/vc4/vc4.ko] undefined!
Reported-by: Linux Kernel Functional Testing
Build error:
-
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build
CROSS_COMPIL
Following kunit tests started failing on Linux mainline.
- drm_format_helper_test — FAIL
- drm_test_fb_xrgb_to_xrgb2101010 — FAIL
- single_pixel_source_buffer — FAIL
Good: v6.0-3015-g2bca25eaeba6
Bad: v6.0-5118-g833477fce7a1
Reported-by: Linux Kernel Functional Testing
[ 50.320990]
Following kernel BUG reported while running kunit drm_framebuffer tests
on Linux mainline 6.1.0-rc1.
Started happening from Linux next 6.0.0-rc1-next-20220818.
Stared happening on Linux mainline from
git_sha: 833477fce7a14d43ae4c07f8ddc32fa5119471a2
Reported-by: Linux Kernel Functional Testing
While running igt testing on arm64 Qcomm db410c the following kernel warning
and crash reported with Linux mainline kernel.
Reported-by: Linux Kernel Functional Testing
metadata:
git_ref: master
git_repo: https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline
git_sha: 88084a3df1672
The following kernel warning found on Rpi4 while booting linux next-20220630.
Boot log details [1] & [2].
Reported-by: Linux Kernel Functional Testing
[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.19.0-rc4-next-20220630
(tuxmake@tuxmake) (a
Hi Rob and Linus,
On Mon, 7 Mar 2022 at 14:07, Naresh Kamboju wrote:
>
> Hi Rob,
>
> On Sun, 20 Feb 2022 at 00:02, Rob Clark wrote:
> >
> > From: Rob Clark
> >
> > Avoid going down devfreq paths on devices where devfreq is not
> > initialized.
&g
On Mon, 7 Mar 2022 at 15:07, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.15.27 release.
> There are 262 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
Hi Rob,
On Sun, 20 Feb 2022 at 00:02, Rob Clark wrote:
>
> From: Rob Clark
>
> Avoid going down devfreq paths on devices where devfreq is not
> initialized.
>
> Reported-by: Linux Kernel Functional Testing
> Reported-by: Anders Roxell
> Signed-off-by: Rob Clark
I have tested this patch and t
[Please ignore this email if it is already reported]
Linux next-20220302 running on Qcom db410c the following kernel crash
reported [1].
metadata:
git_ref: master
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: adaedcf826dccf01b69d9a1f1997c9446c6b2c54
git_describ
[Please ignore this email if it is already reported]
Linux next-20220223 arch riscv build warnings noticed.
Build configs:
- riscv-gcc-9-defconfig
- riscv-gcc-9-defconfig
- riscv-gcc-10-defconfig
- riscv-gcc-11-defconfig
metadata:
git_ref: master
git_repo: https://gitlab.com/Linaro/lk
d the option CONFIG_DRM_KMS_HELPER. [2]
>
> v2:
> * fix and expand commit description (Arnd)
>
> Signed-off-by: Thomas Zimmermann
> Fixes: adb9d5a2cc77 ("drm/dp: Move DisplayPort helpers into separate helper
> module")
> Fixes: 5f04e7ce392d ("drm/panel-
Following builds failed on Linux next 20220202 arm architecture.
- arm-gcc-10-omap2plus_defconfig
- arm-clang-nightly-shmobile_defconfig
- arm-gcc-8-lpc32xx_defconfig
- arm-clang-13-shmobile_defconfig
- arm-gcc-10-shmobile_defconfig
- arm-clang-11-shmobile_defconfig
- arm-clang-11-oma
Regression found on arm64 gcc-10 and gcc-11 built with defconfig
Following build warnings / errors reported on linux next 20211027.
metadata:
git_describe: next-20211027
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: ae5179317e79 (\"Add linux-next speci
AHpwAMiyUcpsL/
> Best regards
> Thomas
>
> [1] https://patchwork.freedesktop.org/patch/461426/
Tested-by: Naresh Kamboju
- Naresh
On Mon, 25 Oct 2021 at 17:43, Naresh Kamboju wrote:
>
> Regression found on arm gcc-11 built with multi_v5_defconfig
> Following build warnings / errors reported on linux next 20211025.
>
> metadata:
> git_describe: next-20211025
> git_repo: https://gitlab.com/Lin
Regression found on arm gcc-11 built with multi_v5_defconfig
Following build warnings / errors reported on linux next 20211025.
metadata:
git_describe: next-20211025
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: 9ae1fbdeabd3 (\"Add linux-next specific
Following kernel crash noticed on linux next 20211020 tag.
while booting on arm64 architecture dragonboard 410c device.
I see the following config is enabled in 20211020 tag builds.
CONFIG_STACKDEPOT=y
Crash log,
[ 18.583097] Unable to handle kernel paging request at virtual
address 007
a, #action)
^~~
include/drm/drm_managed.h:27:18: note: expected 'struct drm_device *'
but argument is of type 'struct drm_device **'
int __must_check __drmm_add_action(struct drm_device *dev,
^~~~~
cc1: some warnings being
On Mon, 1 Mar 2021 at 23:11, Naresh Kamboju wrote:
>
> On stable rc 5.11 the x86_64 build failed due to below errors/warnings.
These build failures were also noticed on stable rc 5.10 for arm64,
arm, x86_64, and i386 architectures.
>
> drivers/gpu/drm/rcar-du/rcar_du_kms.c:
On Tue, 15 Sep 2020 at 19:50, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.66 release.
> There are 132 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 Sun, 12 Apr 2020 at 15:08, Naresh Kamboju wrote:
>
> While booting stable-rc 4.14 branch kernel this warning was noticed on
> Qualcomm APQ 8016 SBC (DT) Dragonboard 410c device.
>
> [8.459580] clk: failed to reparent byte0_clk_src to dsi0pllbyte: -22
> [8.4597
We still notice kernel warnings while booting stable rc 4.14.177-rc1 kernel
on qualcomm dragonboard 410c development board.
[7.760140] msm_dsi_host_set_src_pll: can't set parent to
byte_clk_src. ret=-22
[7.763963] msm_dsi_manager_register: failed to register mipi dsi
host for DSI 0
[7.
On Tue, 3 Mar 2020 at 17:19, Lucas Stach wrote:
>
> On Fr, 2020-02-28 at 11:37 +0100, Christian Gmeiner wrote:
> > Report the correct perfmon domains and signals depending
> > on the supported feature flags.
> >
> > Reported-by: Dan Carpenter
> > Fixes: 9e2c2e273012 ("drm/etnaviv: add infrastruct
While booting stable-rc 4.14 branch kernel this warning was noticed on
Qualcomm APQ 8016 SBC (DT) Dragonboard 410c device.
[8.459580] clk: failed to reparent byte0_clk_src to dsi0pllbyte: -22
[8.459724] clk: failed to reparent pclk0_clk_src to dsi0pll: -22
[8.466474] msm 1a0.mdss:
The arm64 device running LTP hugetlb test suite caused test hang on
stable-rc 5.5.5-rc1 due to [drm:ade_irq_handler [kirin_drm]] *ERROR*
LDI underflow!.
Same problem noticed while running libhugetlbfs test suite.
Problematic patch not identified yet.
hugemmap05.c:223: INFO: original nr_hugepages
On 7 September 2018 at 15:11, Jon Hunter wrote:
>
> On 11/07/18 15:43, Arnd Bergmann wrote:
>> Having DRM_SUN4I built-in but DRM_SUN8I_MIXER as a loadable module results in
>> a link error, as we try to access a symbol from the sun8i_tcon_top.ko module:
>>
>> ERROR: "sun8i_tcon_top_of_table" [driv
t; does not leave behind any corrupted list entries. This should
>> get the system back to boot but needs testing. From my understanding,
>> there is at least one more bug that needs to be resolved to actually
>> get everything to work again.
>>
>> Reported-by: Naresh Kamboj
45 matches
Mail list logo
