nouveau: r535.c:1266:3: error: label at end of compound statement default: with gcc-8
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
gcc-8-arm-defconfig - Fail
gcc-8-riscv-defconfig - Fail
Build log:
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c: In function 'build_registry':
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:1266:3: error: label at
end of compound statement
default:
^~~
make[7]: *** [scripts/Makefile.build:244:
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.o] Error 1
metadata:
git_describe: next-20240429
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: b0a2c79c6f35 ("Add linux-next specific files for 20240429")
arch: arm64, arm, riscv
toolchain: gcc-8
Steps to reproduce:
# tuxmake --runtime podman --target-arch arm64 --toolchain gcc-8
--kconfig defconfig
Links:
-
https://storage.tuxsuite.com/public/linaro/lkft/builds/2flcoOuqVJfhTvX4AOYsWMd5hqe/
-
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240429/testrun/23704376/suite/build/test/gcc-8-defconfig/history/
-
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240429/testrun/23705756/suite/build/test/gcc-8-defconfig/details/
--
Linaro LKFT
https://lkft.linaro.org
Re: [PATCH 4.19 000/175] 4.19.312-rc1 review
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. > > Responses should be made by Sat, 13 Apr 2024 09:53:55 +. > 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.312-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-4.19.y > and the diffstat can be found below. > > thanks, > > greg k-h The arm imx_v6_v7_defconfig build failed with gcc-12 and clang on Linux stable-rc linux-4.19.y. Regressions: - arm * gcc-12-imx_v6_v7_defconfig - failed Reported-by: Linux Kernel Functional Testing Build log: drivers/gpu/drm/imx/parallel-display.c: In function 'imx_pd_bridge_atomic_check': drivers/gpu/drm/imx/parallel-display.c:222:23: error: implicit declaration of function 'drm_bridge_get_next_bridge' [-Werror=implicit-function-declaration] 222 | next_bridge = drm_bridge_get_next_bridge(bridge); | ^~ Links: - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.311-176-gf0cf5f6110a7/testrun/23411280/suite/build/test/gcc-12-imx_v6_v7_defconfig/details/ - https://storage.tuxsuite.com/public/linaro/lkft/builds/2ex1v6eevudbi33g4ozA7hJ4fvs/ -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 00/14] Add support for suppressing warning backtraces
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 discussed there. Thanks for the patchset. This patch series applied on top of Linux next and tested. Tested-by: Linux Kernel Functional Testing -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH] powerpc: include linux/backlight.h from asm/backlight.h
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.
> >
> > Reported-by: Naresh Kamboju
> > Closes:
> > https://lore.kernel.org/r/ca+g9fysak5tbqqxfc2w4ohlga0cbthmxbeq8qayfxtu75yi...@mail.gmail.com
> > Fixes: 11b4eedfc87d ("fbdev: Do not include in header")
> > Cc: Thomas Zimmermann
> > Cc: Helge Deller
> > Cc: linux-fb...@vger.kernel.org
> > Signed-off-by: Jani Nikula
> >
> > ---
> >
> > Not even compile tested!
>
> Naresh, please try this patch!
Thanks for the proposed fix patch.
Steps to reproduce:
# tuxmake --runtime podman --target-arch powerpc --toolchain gcc-13
--kconfig ppc6xx_defconfig --kconfig-add CONFIG_PMAC_BACKLIGHT=y
config debugkernel dtbs kernel modules xipkernel
# Applying patch set
Applying: fbdev/chipsfb: Include
The reported build regression is fixed but build failed with below errors.
My two cents,
I should have copied the full build error log in the morning.
Few more build errors on powerpc builds,
--
drivers/macintosh/via-pmu-backlight.c: In function
'__pmu_backlight_update_status':
drivers/macintosh/via-pmu-backlight.c:74:21: error: implicit
declaration of function 'backlight_get_brightness'; did you mean
'pmu_backlight_get_level_brightness'?
[-Werror=implicit-function-declaration]
74 | int level = backlight_get_brightness(bd);
| ^~~~
| pmu_backlight_get_level_brightness
drivers/macintosh/via-pmu-backlight.c: At top level:
drivers/macintosh/via-pmu-backlight.c:108:21: error: variable
'pmu_backlight_data' has initializer but incomplete type
108 | static const struct backlight_ops pmu_backlight_data = {
| ^
drivers/macintosh/via-pmu-backlight.c:109:10: error: 'const struct
backlight_ops' has no member named 'update_status'
109 | .update_status = pmu_backlight_update_status,
| ^
drivers/macintosh/via-pmu-backlight.c:109:27: warning: excess elements
in struct initializer
109 | .update_status = pmu_backlight_update_status,
| ^~~
drivers/macintosh/via-pmu-backlight.c:109:27: note: (near
initialization for 'pmu_backlight_data')
drivers/macintosh/via-pmu-backlight.c: In function 'pmu_backlight_init':
drivers/macintosh/via-pmu-backlight.c:136:37: error: storage size of
'props' isn't known
136 | struct backlight_properties props;
| ^
drivers/macintosh/via-pmu-backlight.c:154:34: error: invalid
application of 'sizeof' to incomplete type 'struct
backlight_properties'
154 | memset(, 0, sizeof(struct backlight_properties));
| ^~
drivers/macintosh/via-pmu-backlight.c:155:22: error:
'BACKLIGHT_PLATFORM' undeclared (first use in this function)
155 | props.type = BACKLIGHT_PLATFORM;
| ^~
drivers/macintosh/via-pmu-backlight.c:155:22: note: each undeclared
identifier is reported only once for each function it appears in
drivers/macintosh/via-pmu-backlight.c:157:14: error: implicit
declaration of function 'backlight_device_register'; did you mean
'root_device_register'? [-Werror=implicit-function-declaration]
157 | bd = backlight_device_register(name, NULL, NULL,
_backlight_data,
| ^
| root_device_register
drivers/macintosh/via-pmu-backlight.c:166:19: error: invalid use of
undefined type 'struct backlight_device'
166 | level = bd->props.max_brightness;
| ^~
drivers/macintosh/via-pmu-backlight.c:176:35: error: invalid use of
undefined type 'struct backlight_device'
176 | bd->props.max_brightness / 15);
| ^~
drivers/macintosh/via-pmu-backlight.c:179:11: error: invalid use of
undefined type 'struct backlight_device'
179 | bd->props.brightness = level;
| ^~
drivers/macintosh/via-pmu-backlight.c:180:11: error: invalid use of
undefined type 'struct backlight_device'
180 | bd->props.power = FB_BLANK_UNBLANK;
| ^~
drivers/macintosh/via-pmu-backlight.c:181:9: error: implicit
declaration of function 'backlight_update_status'; did you mean
'pmu_backlight_update_status'? [-Werror=implicit-function-declaration]
181 | backlight_update_status(bd);
| ^~~
| pmu_backlight_update_status
drivers/macintosh/via-pmu-backlight.c:136:37: warning: unused variable
'props' [-Wunused-variable]
136 |
fbdev/chipsfb.c:401:31: error: invalid use of undefined type 'struct backlight_device'
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 backlight_device' 401 | pmac_backlight->props.power = FB_BLANK_UNBLANK; | ^~ Steps to reproduce: # tuxmake --runtime podman --target-arch powerpc --toolchain gcc-13 --kconfig ppc6xx_defconfig - https://storage.tuxsuite.com/public/linaro/lkft/builds/2dDE297yLFrAr3gigIDy8tIleDh/tuxmake_reproducer.sh Links: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919857/suite/build/test/gcc-13-ppc6xx_defconfig/details/ - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919857/suite/build/test/gcc-13-ppc6xx_defconfig/log - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919857/suite/build/test/gcc-13-ppc6xx_defconfig/history/ -- Linaro LKFT https://lkft.linaro.org
arm: ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined!
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 LLVM_IAS=1 Links: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919744/suite/build/test/clang-17-defconfig/history/ - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919744/suite/build/test/clang-17-defconfig/log - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919744/suite/build/test/clang-17-defconfig/details/ -- Linaro LKFT https://lkft.linaro.org
Kunit drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123
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_invalid_plane_state_drm_test_check_invalid_plane_state - drm_test_check_invalid_plane_state_positioning_invalid - drm_test_check_invalid_plane_state_upscaling_invalid - drm_test_check_plane_state_clipping_rotate_reflect - drm_test_check_plane_state_clipping_simple - drm_test_check_plane_state_downscaling - drm_test_check_plane_state_drm_test_check_plane_state - drm_test_check_plane_state_positioning_simple - drm_test_check_plane_state_rounding1 - drm_test_check_plane_state_rounding2 - drm_test_check_plane_state_rounding3 - drm_test_check_plane_state_rounding4 - drm_test_check_plane_state_upscaling Reported-by: Linux Kernel Functional Testing Test log: --- [ 91.955019] # Subtest: drm_plane_helper [ 91.959248] # module: drm_plane_helper_test [ 91.959271] 1..2 [ 91.966042] KTAP version 1 [ 91.969494] # Subtest: drm_test_check_plane_state [ 91.969707] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 91.969707] Expected plane_state->visible to be true, but is false [ 91.992346] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:96 [ 91.992346] Expected drm_rect_equals(_state->src, ) to be true, but is false [ 91.992346] [ 91.992346] dst: 2048.00x2048.00+0.00+0.00, expected: 1024.00x768.00+0.00+0.00 [ 91.992392] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:107 [ 91.992392] Expected drm_rect_equals(_state->dst, ) to be true, but is false [ 91.992392] [ 91.992392] dst: 2048x2048+0+0, expected: 1024x768+0+0 [ 92.023394] not ok 1 clipping_simple [ 92.049526] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 92.049526] Expected plane_state->visible to be true, but is false [ 92.071041] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:96 [ 92.071041] Expected drm_rect_equals(_state->src, ) to be true, but is false [ 92.071041] [ 92.071041] dst: 2048.00x2048.00+0.00+0.00, expected: 768.00x1024.00+0.00+0.00 [ 92.071084] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:107 [ 92.071084] Expected drm_rect_equals(_state->dst, ) to be true, but is false [ 92.071084] [ 92.071084] dst: 2048x2048+0+0, expected: 1024x768+0+0 [ 92.102010] not ok 2 clipping_rotate_reflect [ 92.128099] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 92.128099] Expected plane_state->visible to be true, but is false [ 92.150558] not ok 3 positioning_simple [ 92.150768] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 92.150768] Expected plane_state->visible to be true, but is false [ 92.173083] not ok 4 upscaling [ 92.173209] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 92.173209] Expected plane_state->visible to be true, but is false [ 92.194443] not ok 5 downscaling [ 92.194656] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 92.194656] Expected plane_state->visible to be true, but is false [ 92.215819] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:96 [ 92.215819] Expected drm_rect_equals(_state->src, ) to be true, but is false [ 92.215819] [ 92.215819] dst: 4.15x4.15+0.00+0.00, expected: 2.00x2.00+0.00+0.00 [ 92.215863] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:107 [ 92.215863] Expected drm_rect_equals(_state->dst, ) to be true, but is false [ 92.215863] [ 92.215863] dst: 4x4+1022+766, expected: 2x2+1022+766 [ 92.245779] not ok 6 rounding1 [ 92.271735] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:123 [ 92.271735] Expected plane_state->visible to be true, but is false [ 92.292739] # drm_test_check_plane_state: EXPECTATION FAILED at drivers/gpu/drm/tests/drm_plane_helper_test.c:96 [ 92.292739] Expected drm_rect_equals(_state->src, ) to be true, but is false [ 92.292739] [ 92.292739] dst:
Re: [RFC] drm/tests: annotate intentional stack trace in drm_test_rect_calc_hscale()
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 > failure. Now the test team has to contact the developers. A bunch of > people have to investigate the bug. We finally decide that it's > intentional so now the test team has to update their filter scripts to > mark it as intentional. These filters are ad-hoc because there is no > standard format for warnings. > > A better way would be to mark it as intentional from the start. > > Here, I have marked the beginning and the end of the trace. It's more > tricky for things like lkdtm_FORTIFY_MEM_MEMBER() where the flow doesn't > reach the end of the function. I guess I would print a different > warning for stack traces that can't have a > "Intentional warning finished\n" message at the end. > > I haven't actually tested this patch... Daniel, do you have a > list of intentional stack traces we could annotate? [My two cents] I have been noticing following kernel warnings / BUGs These are starting happening from next-20231009. I am not sure which are "Intentional warnings" or real regressions. [ 37.378220] BUG: KASAN: slab-out-of-bounds in kmalloc_oob_right+0xc4/0x300 [ 37.645506] BUG: KASAN: slab-out-of-bounds in kmalloc_oob_right+0xec/0x300 .. [ 632.407425] BUG: KASAN: null-ptr-deref in kobject_namespace+0x3c/0xb0 Logs: [Sorry for sharing long logs ] == [ cut here ] [ 629.699281] WARNING: CPU: 0 PID: 2834 at drivers/gpu/drm/drm_rect.c:138 drm_rect_calc_hscale+0xbc/0xe8 [drm_kms_helper] [ 629.710944] Modules linked in: drm_rect_test(+) drm_probe_helper_test drm_plane_helper_test drm_modes_test drm_mm_test drm_managed_test drm_framebuffer_test drm_format_test drm_format_helper_test drm_exec_test drm_exec drm_kunit_helpers drm_dp_mst_helper_test drm_display_helper drm_damage_helper_test drm_connector_test drm_cmdline_parser_test drm_buddy_test prime_numbers drm_buddy tda998x onboard_usb_hub hdlcd cec crct10dif_ce drm_dma_helper drm_kms_helper drm fuse backlight dm_mod ip_tables x_tables [ 629.756007] CPU: 0 PID: 2834 Comm: kunit_try_catch Tainted: GB N 6.6.0-next-20231031 #1 [ 629.765381] Hardware name: ARM Juno development board (r2) (DT) [ 629.771343] pstate: 2005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 629.778362] pc : drm_rect_calc_hscale+0xbc/0xe8 [drm_kms_helper] [ 629.785160] lr : drm_rect_calc_hscale+0x60/0xe8 [drm_kms_helper] [ 629.791955] sp : 800088907d20 [ 629.795301] x29: 800088907d20 x28: x27: [ 629.802533] x26: 0008270a39c0 x25: 8000885673e8 x24: 8000809ccf28 [ 629.809770] x23: x22: 7fff x21: [ 629.817003] x20: 80007faf0018 x19: 0001 x18: 7be82992 [ 629.824236] x17: 00040044 x16: 00500072b5503510 x15: [ 629.831469] x14: 800085d51d00 x13: 8008b22e5000 x12: 600105778569 [ 629.838704] x11: 1fffe00105778568 x10: 600105778568 x9 : 80007fae56e4 [ 629.845940] x8 : 800088907d08 x7 : x6 : 41b58ab3 [ 629.853171] x5 : dfff8000 x4 : 700011120fb2 x3 : dfff8000 [ 629.860406] x2 : 0003 x1 : x0 : 0001 [ 629.867637] Call trace: [ 629.870108] drm_rect_calc_hscale+0xbc/0xe8 [drm_kms_helper] [ 629.876561] drm_test_rect_calc_hscale+0xac/0x150 [drm_rect_test] [ 629.882811] kunit_try_run_case+0x84/0x110 [ 629.886984] kunit_generic_run_threadfn_adapter+0x38/0x60 [ 629.892445] kthread+0x18c/0x1a8 [ 629.895723] ret_from_fork+0x10/0x20 [ 629.899355] ---[ end trace ]--- [ cut here ] [ 629.914458] WARNING: CPU: 5 PID: 2836 at drivers/gpu/drm/drm_rect.c:138 drm_rect_calc_hscale+0xbc/0xe8 [drm_kms_helper] [ 629.926098] Modules linked in: drm_rect_test(+) drm_probe_helper_test drm_plane_helper_test drm_modes_test drm_mm_test drm_managed_test drm_framebuffer_test drm_format_test drm_format_helper_test drm_exec_test drm_exec drm_kunit_helpers drm_dp_mst_helper_test drm_display_helper drm_damage_helper_test drm_connector_test drm_cmdline_parser_test drm_buddy_test prime_numbers drm_buddy tda998x onboard_usb_hub hdlcd cec crct10dif_ce drm_dma_helper drm_kms_helper drm fuse backlight dm_mod ip_tables x_tables [ 629.971166] CPU: 5 PID: 2836 Comm: kunit_try_catch Tainted: GB WN 6.6.0-next-20231031 #1 [ 629.980553] Hardware name: ARM Juno development board (r2) (DT) [ 629.986519] pstate: 2005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 629.993545] pc : drm_rect_calc_hscale+0xbc/0xe8 [drm_kms_helper] [ 630.000401] lr : drm_rect_calc_hscale+0x60/0xe8 [drm_kms_helper] [ 630.007201] sp : 800088957d20 [ 630.010548] x29:
BUG: KASAN: slab-use-after-free in drm_connector_cleanup
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 Boot log: - [ 209.991842] Bluetooth: Core ver 2.22 [ 209.996014] NET: Registered PF_BLUETOOTH protocol family [ 210.002564] Bluetooth: HCI device and connection manager initialized [ 210.009204] Bluetooth: HCI socket layer initialized [ 210.014443] Bluetooth: L2CAP socket layer initialized [ 210.019906] Bluetooth: SCO socket layer initialized [ 210.175889] KTAP version 1 [ 210.178771] 1..3 [ 210.184030] KTAP version 1 [ 210.187234] # Subtest: vc4-pv-muxing-combinations [ 210.192491] # module: vc4 [ 210.192572] 1..2 [ 210.197937] KTAP version 1 [ 210.201544] # Subtest: drm_vc4_test_pv_muxing [ 210.218416] Bluetooth: HCI UART driver ver 2.3 [ 210.236869] [drm] Initialized vc4 0.0.0 20140616 for drm-kunit-mock-device on minor 1 [ 210.241063] Bluetooth: HCI UART protocol H4 registered [ 210.320009] Bluetooth: HCI UART protocol LL registered [ 210.464457] Bluetooth: HCI UART protocol Broadcom registered [ 210.470871] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator [ 210.472120] Bluetooth: HCI UART protocol QCA registered [ 210.480123] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator [ 210.490971] Bluetooth: HCI UART protocol Marvell registered Debian GNU/Linux 12 runner-vwmj3eza-project-40964107-concurrent-0 ttyS0 runner-vwmj3eza-project-40964107-concurrent-0 login: [ 2root 10.623188] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 210.658616] == [ 210.666006] BUG: KASAN: slab-use-after-free in drm_connector_cleanup+0x30/0x488 drm [ 210.675144] Read of size 8 at addr 000113a8e0a8 by task kunit_try_catch/1750 [ 210.682685] [ 210.684219] CPU: 1 PID: 1750 Comm: kunit_try_catch Tainted: GB N 6.6.0-rc5-next-20231011 #1 [ 210.694056] Hardware name: Raspberry Pi 4 Model B (DT) [ 210.699323] Call trace: r[ 210.701824] dump_backtrace (arch/arm64/kernel/stacktrace.c:235) [ 210.705757] show_stack (arch/arm64/kernel/stacktrace.c:242) [ 210.709160] dump_stack_lvl (lib/dump_stack.c:107) [ 210.712917] print_report (mm/kasan/report.c:365 mm/kasan/report.c:475) [ 210.716560] kasan_report (mm/kasan/report.c:590) o[ 210.720201] __asan_load8 (mm/kasan/generic.c:260) o[ 210.723827] drm_connector_cleanup+0x30/0x488 drm [ 210.729265] drm_connector_cleanup_action+0x1c/0x30 drm t[ 210.735228] drm_managed_release+0x128/0x228 drm [ 210.740570] drm_dev_put.part.0+0xb4/0xf8 drm [ 210.742616] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 210.745649] devm_drm_dev_init_release+0x1c/0x38 drm [ 210.756667] devm_action_release (drivers/base/devres.c:722) [ 210.760840] release_nodes (drivers/base/devres.c:506) [ 210.764569] devres_release_all (drivers/base/devres.c:535) [ 210.765145] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 210.768737] device_unbind_cleanup (drivers/base/dd.c:551) [ 210.768759] device_release_driver_internal (drivers/base/dd.c:1280 drivers/base/dd.c:1295) [ 210.768775] device_release_driver (drivers/base/dd.c:1319) [ 210.768788] bus_remove_device (include/linux/kobject.h:193 drivers/base/base.h:73 drivers/base/bus.c:581) [ 210.768801] device_del (drivers/base/core.c:3815) [ 210.768812] platform_device_del.part.0 (drivers/base/platform.c:753) [ 210.768824] platform_device_del (drivers/base/platform.c:764) [ 210.768834] kunit_action_platform_device_del+0x18/0x30 drm_kunit_helpers [ 210.810264] cfg80211: failed to load regulatory.db [ 210.815438] __kunit_action_free (lib/kunit/resource.c:92) [ 210.815460] kunit_remove_resource (include/kunit/resource.h:120 include/linux/kref.h:65 include/kunit/resource.h:138 lib/kunit/resource.c:59 lib/kunit/resource.c:48) [ 210.815474] kunit_cleanup (lib/kunit/test.c:815 (discriminator 1)) [ 210.815486] kunit_try_run_case_cleanup (lib/kunit/test.c:412) [ 210.815499] kunit_generic_run_threadfn_adapter (lib/kunit/try-catch.c:30) [ 210.815514] kthread (kernel/kthread.c:388) [ 210.815526] ret_from_fork (arch/arm64/kernel/entry.S:858) [ 210.815540] [ 210.815544] Allocated by task 1745: [ 210.815552] kasan_save_stack (mm/kasan/common.c:46) [ 210.815567] kasan_set_track (mm/kasan/common.c:52 (discriminator 1)) [ 210.815579] kasan_save_alloc_info (mm/kasan/generic.c:512) [ 210.815592] __kasan_kmalloc (mm/kasan/common.c:374 mm/kasan/common.c:383) [ 210.815603] __kmalloc (include/linux/kasan.h:198 mm/slab_common.c:1004 mm/slab_common.c:1017) [ 210.815613] kunit_kmalloc_array (include/linux/slab.h:637 lib/kunit/test.c:779) [ 210.815625] vc4_dummy_output+0xac/0x228 vc4 [ 210.882798] __mock_device+0x24c/0x4b0 vc4 [
Re: [PATCH 5.4 000/367] 5.4.257-rc1 review
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. > > Responses should be made by Fri, 22 Sep 2023 11:28:09 +. > 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.4.257-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.4.y > and the diffstat can be found below. > > thanks, > > greg k-h Following build warnings noticed while building arm64 with allmodconfig on stable-rc 5.4 with gcc-8 and gcc-12 toolchains. Reported-by: Linux Kernel Functional Testing drivers/gpu/drm/mediatek/mtk_drm_gem.c: In function 'mtk_drm_gem_prime_vmap': drivers/gpu/drm/mediatek/mtk_drm_gem.c:273:10: warning: returning 'int' from a function with return type 'void *' makes pointer from integer without a cast [-Wint-conversion] return -ENOMEM; ^ Links: - https://storage.tuxsuite.com/public/linaro/lkft/builds/2VfG47LmPH9MUEuIcMVftu6NsFy/ Following commit is causing this build warning. drm/mediatek: Fix potential memory leak if vmap() fail [ Upstream commit 379091e0f6d179d1a084c65de90fa44583b14a70 ] -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 1/6] drm: execution context for GEM buffers v7
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
> > it in the long term.
> >
> > The basic functionality is that we abstracts the necessary loop to lock
> > many different GEM buffers with automated deadlock and duplicate handling.
> >
> > v2: drop xarray and use dynamic resized array instead, the locking
> > overhead is unnecessary and measurable.
> > v3: drop duplicate tracking, radeon is really the only one needing that.
> > v4: fixes issues pointed out by Danilo, some typos in comments and a
> > helper for lock arrays of GEM objects.
> > v5: some suggestions by Boris Brezillon, especially just use one retry
> > macro, drop loop in prepare_array, use flags instead of bool
> > v6: minor changes suggested by Thomas, Boris and Danilo
> > v7: minor typos pointed out by checkpatch.pl fixed
> >
> > Signed-off-by: Christian König
> > Reviewed-by: Boris Brezillon
> > Reviewed-by: Danilo Krummrich
> > Tested-by: Danilo Krummrich
>
>
>
> > diff --git a/include/drm/drm_exec.h b/include/drm/drm_exec.h
> > new file mode 100644
> > index ..73205afec162
> > --- /dev/null
> > +++ b/include/drm/drm_exec.h
>
>
>
> > + * Since labels can't be defined local to the loops body we use a jump
> > pointer
> > + * to make sure that the retry is only used from within the loops body.
> > + */
> > +#define drm_exec_until_all_locked(exec) \
> > + for (void *__drm_exec_retry_ptr; ({ \
> > + __label__ __drm_exec_retry; \
> > +__drm_exec_retry:\
> > + __drm_exec_retry_ptr = &&__drm_exec_retry; \
> > + (void)__drm_exec_retry_ptr; \
> > + drm_exec_cleanup(exec); \
> > + });)
> > +
> > +/**
> > + * drm_exec_retry_on_contention - restart the loop to grap all locks
> > + * @exec: drm_exec object
> > + *
> > + * Control flow helper to continue when a contention was detected and we
> > need to
> > + * clean up and re-start the loop to prepare all GEM objects.
> > + */
> > +#define drm_exec_retry_on_contention(exec) \
> > + do {\
> > + if (unlikely(drm_exec_is_contended(exec))) \
> > + goto *__drm_exec_retry_ptr; \
> > + } while (0)
>
> This construct of using a label as a value and goto to jump into a GNU
> C statement expression is explicitly documented in GCC's manual [1] as
> undefined behavior:
>
> "Jumping into a statement expression with a computed goto (see Labels as
> Values [2]) has undefined behavior. "
>
> A recent change in clang [3] to prohibit this altogether points this out, so
> builds using clang-17 and newer will break with this change applied:
>
> drivers/gpu/drm/tests/drm_exec_test.c:41:3: error: cannot jump from this
> indirect goto statement to one of its possible targets
> 41 | drm_exec_retry_on_contention();
> | ^
LKFT also noticed these build failures on arm and arm64 with clang nightly.
> include/drm/drm_exec.h:96:4: note: expanded from macro
> 'drm_exec_retry_on_contention'
> 96 | goto *__drm_exec_retry_ptr; \
> | ^
> drivers/gpu/drm/tests/drm_exec_test.c:39:2: note: possible target of
> indirect goto statement
> 39 | drm_exec_until_all_locked() {
> | ^
> include/drm/drm_exec.h:79:33: note: expanded from macro
> 'drm_exec_until_all_locked'
> 79 | __label__ __drm_exec_retry; \
> | ^
> drivers/gpu/drm/tests/drm_exec_test.c:39:2: note: jump enters a statement
> expression
>
> It seems like if this construct works, it is by chance, although I am
> not sure if there is another solution.
Thanks for looking into this problem.
>
> [1]: https://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html
> [2]: https://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html
> [3]:
> https://github.com/llvm/llvm-project/commit/20219106060208f0c2f5d096eb3aed7b712f5067
>
> Cheers,
> Nathan
- Naresh
next: clang: x86_64: /intel_display.c:6012:3: error: unannotated fall-through between switch labels [-Werror,-Wimplicit-fallthrough]
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 clang' 'CC=sccache clang' \ LLVM=1 LLVM_IAS=1 drivers/gpu/drm/i915/display/intel_display.c:6012:3: error: unannotated fall-through between switch labels [-Werror,-Wimplicit-fallthrough] case I915_FORMAT_MOD_X_TILED: ^ drivers/gpu/drm/i915/display/intel_display.c:6012:3: note: insert 'break;' to avoid fall-through case I915_FORMAT_MOD_X_TILED: ^ break; 1 error generated. log: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230524/testrun/17171777/suite/build/test/clang-lkftconfig/log - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230524/testrun/17171777/suite/build/test/clang-lkftconfig/history/ -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
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 ]
> >
> > LKFT test farm have fetched your patch series [1]
> > [PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
> > [1]
> > https://lore.kernel.org/llvm/20221228-drop-qunused-arguments-v2-0-9adbddd20...@kernel.org/
>
> Thank you a lot for testing this series, it is much appreciated!
>
> It looks like this was applied on top of 6.2-rc3 if I am reading your
> logs right but your mainline testing is recent, 6.2-rc5. I think the
> errors you are seeing here are just existing mainline regressions that
> were later fixed.
>
> > Following build warnings and errors reported.
> >
> > sh:
> > gcc-11-defconfig — FAIL
> > gcc-11-shx3_defconfig — FAIL
> > https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221835/suite/build/tests/
> >
> > mainline getting passed.
> > https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-defconfig/history/
> > https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-shx3_defconfig/history/
> >
> > Build error:
> > In function 'follow_pmd_mask',
> > inlined from 'follow_pud_mask' at /builds/linux/mm/gup.c:735:9,
> > inlined from 'follow_p4d_mask' at /builds/linux/mm/gup.c:752:9,
> > inlined from 'follow_page_mask' at /builds/linux/mm/gup.c:809:9:
> > /builds/linux/include/linux/compiler_types.h:358:45: error: call to
> > '__compiletime_assert_263' declared with attribute error: Unsupported
> > access size for {READ,WRITE}_ONCE().
> > 358 | _compiletime_assert(condition, msg,
> > __compiletime_assert_, __COUNTER__)
>
> I think this was fixed with mainline commit 526970be53d5 ("sh/mm: Fix
> pmd_t for real"), released in 6.2-rc4. You can see a previous build
> failing in the same manner:
>
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc3-9-g5a41237ad1d4/testrun/14056384/suite/build/tests/
>
> > s390:
> > clang-15-defconfig — FAIL
> > https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221913/suite/build/tests/
> >
> > mainline getting passed.
> > https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14300495/suite/build/test/clang-15-defconfig/history/
> >
> > Build error:
> > make --silent --keep-going --jobs=8
> > O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM_IAS=0 ARCH=s390
> > CROSS_COMPILE=s390x-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache
> > clang'
> > `.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
> > defined in discarded section `.exit.text' of fs/fuse/inode.o
> > `.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
> > defined in discarded section `.exit.text' of fs/fuse/inode.o
> > `.exit.text' referenced in section `__bug_table' of crypto/algboss.o:
> > defined in discarded section `.exit.text' of crypto/algboss.o
> > `.exit.text' referenced in section `__bug_table' of drivers/scsi/sd.o:
> > defined in discarded section `.exit.text' of drivers/scsi/sd.o
> > `.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
> > defined in discarded section `.exit.text' of drivers/md/md.o
> > `.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
> > defined in discarded section `.exit.text' of drivers/md/md.o
> > `.exit.text' referenced in section `.altinstructions' of
> > drivers/md/md.o: defined in discarded section `.exit.text' of
> > drivers/md/md.o
> > `.exit.text' referenced in section `.altinstructions' of
> > drivers/md/md.o: defined in discarded section `.exit.text' of
> > drivers/md/md.o
> > `.exit.text' referenced in section `.altinstructions' of
> > net/iucv/iucv.o: defined in discarded section `.exit.text' of
> > net/iucv/iucv.o
> > `.exit.text' referenced in section `__bug_table' of
> > drivers/s390/cio/qdio_thinint.o: defined in discarded section
> > `.exit.text' of drivers/s390/cio/qdio_thinint.o
> > `.exit.text' referenced in section `__bug_table' of
> > drivers/s390/net/qeth_l3_main.o: defined in discarded section
> > `.exit
Re: [PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
+---
> arch/mips/loongson2ef/Platform | 2 +-
> arch/powerpc/Makefile | 2 +-
> arch/powerpc/kernel/vdso/Makefile | 25 +++--
> arch/s390/kernel/vdso64/Makefile| 4 +--
> arch/s390/purgatory/Makefile| 2 +-
> arch/x86/boot/compressed/Makefile | 2 +-
> drivers/gpu/drm/amd/display/dc/dml/Makefile | 3 ++-
> scripts/Kconfig.include | 2 +-
> scripts/Makefile.clang | 2 ++
> scripts/Makefile.compiler | 8 +++---
> scripts/as-version.sh | 2 +-
> 21 files changed, 74 insertions(+), 98 deletions(-)
FYI,
[ please provide comments, feedback and improvements on build/ ltp smoke tests ]
LKFT test farm have fetched your patch series [1]
[PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
[1]
https://lore.kernel.org/llvm/20221228-drop-qunused-arguments-v2-0-9adbddd20...@kernel.org/
Following build warnings and errors reported.
sh:
gcc-11-defconfig — FAIL
gcc-11-shx3_defconfig — FAIL
https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221835/suite/build/tests/
mainline getting passed.
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-defconfig/history/
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-shx3_defconfig/history/
Build error:
In function 'follow_pmd_mask',
inlined from 'follow_pud_mask' at /builds/linux/mm/gup.c:735:9,
inlined from 'follow_p4d_mask' at /builds/linux/mm/gup.c:752:9,
inlined from 'follow_page_mask' at /builds/linux/mm/gup.c:809:9:
/builds/linux/include/linux/compiler_types.h:358:45: error: call to
'__compiletime_assert_263' declared with attribute error: Unsupported
access size for {READ,WRITE}_ONCE().
358 | _compiletime_assert(condition, msg,
__compiletime_assert_, __COUNTER__)
s390:
clang-15-defconfig — FAIL
https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221913/suite/build/tests/
mainline getting passed.
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14300495/suite/build/test/clang-15-defconfig/history/
Build error:
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM_IAS=0 ARCH=s390
CROSS_COMPILE=s390x-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache
clang'
`.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
defined in discarded section `.exit.text' of fs/fuse/inode.o
`.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
defined in discarded section `.exit.text' of fs/fuse/inode.o
`.exit.text' referenced in section `__bug_table' of crypto/algboss.o:
defined in discarded section `.exit.text' of crypto/algboss.o
`.exit.text' referenced in section `__bug_table' of drivers/scsi/sd.o:
defined in discarded section `.exit.text' of drivers/scsi/sd.o
`.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
defined in discarded section `.exit.text' of drivers/md/md.o
`.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
defined in discarded section `.exit.text' of drivers/md/md.o
`.exit.text' referenced in section `.altinstructions' of
drivers/md/md.o: defined in discarded section `.exit.text' of
drivers/md/md.o
`.exit.text' referenced in section `.altinstructions' of
drivers/md/md.o: defined in discarded section `.exit.text' of
drivers/md/md.o
`.exit.text' referenced in section `.altinstructions' of
net/iucv/iucv.o: defined in discarded section `.exit.text' of
net/iucv/iucv.o
`.exit.text' referenced in section `__bug_table' of
drivers/s390/cio/qdio_thinint.o: defined in discarded section
`.exit.text' of drivers/s390/cio/qdio_thinint.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
`.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]: *** [/builds/linux/scripts/Makefile.vmlinux:34: vmlinux] Error 1
But,
Build and boot pass on arm64, arm, x86_64 and i386.
Build test performed for mips, parisc, riscv, s390, sh, sparc and
powerpc (known build errors for maple_defconfig and cell_defconfig),
Please refer following link for detailed build, boot, LTP smoketest.
https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/?failures_only=false_layout=table#!#test-results
Best regards
Naresh Kamboju
--
Linaro LKFT
https://lkft.linaro.org
> ---
> base-commit: 88603b6dc419445847923fcb7fe5080067a30f98
> change-id: 20221228-drop-qunused-arguments-0c5c7dae54fb
>
> Best regards,
> --
> Nathan Chancellor
>
>
Re: [PATCH v2 1/3] drm/msm/gpu: Add devfreq tuning debugfs
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 WARNING: unmet direct dependencies detected for DEVFREQ_GOV_SIMPLE_ONDEMAND Depends on [n]: PM_DEVFREQ [=n] Selected by [y]: - DRM_MSM [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARCH_QCOM [=n] || SOC_IMX5 [=y] || COMPILE_TEST [=n]) && COMMON_CLK [=y] && IOMMU_SUPPORT [=y] && (QCOM_OCMEM [=n] || QCOM_OCMEM [=n]=n) && (QCOM_LLCC [=n] || QCOM_LLCC [=n]=n) && (QCOM_COMMAND_DB [=n] || QCOM_COMMAND_DB [=n]=n) WARNING: unmet direct dependencies detected for DEVFREQ_GOV_SIMPLE_ONDEMAND Depends on [n]: PM_DEVFREQ [=n] Selected by [y]: - DRM_MSM [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARCH_QCOM [=n] || SOC_IMX5 [=y] || COMPILE_TEST [=n]) && COMMON_CLK [=y] && IOMMU_SUPPORT [=y] && (QCOM_OCMEM [=n] || QCOM_OCMEM [=n]=n) && (QCOM_LLCC [=n] || QCOM_LLCC [=n]=n) && (QCOM_COMMAND_DB [=n] || QCOM_COMMAND_DB [=n]=n) make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc' In file included from drivers/gpu/drm/msm/msm_gpu.h:18, from drivers/gpu/drm/msm/adreno/adreno_gpu.h:15, from drivers/gpu/drm/msm/adreno/adreno_device.c:9: drivers/gpu/drm/msm/msm_drv.h:237:45: error: field 'gpu_devfreq_config' has incomplete type 237 | struct devfreq_simple_ondemand_data gpu_devfreq_config; | ^~ Build log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230118/testrun/14250189/suite/build/test/gcc-12-imx_v6_v7_defconfig/log This was already reported a while back on lore, https://lore.kernel.org/all/202301130108.fslqjvj8-...@intel.com/ -- Linaro LKFT https://lkft.linaro.org
next-20230110: arm64: defconfig+kselftest config boot failed - Unable to handle kernel paging request at virtual address fffffffffffffff8
[ 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 get back to you shortly. GOOD: next-20230109 (defconfig + kselftests configs) BAD: next-20230110 (defconfig + kselftests configs) kernel crash log [1]: [ 15.302140] Unable to handle kernel paging request at virtual address fff8 [ 15.309906] Mem abort info: [ 15.312659] ESR = 0x9604 [ 15.316365] EC = 0x25: DABT (current EL), IL = 32 bits [ 15.321626] SET = 0, FnV = 0 [ 15.324644] EA = 0, S1PTW = 0 [ 15.327744] FSC = 0x04: level 0 translation fault [ 15.332619] Data abort info: [ 15.335422] ISV = 0, ISS = 0x0004 [ 15.339226] CM = 0, WnR = 0 [ 15.342154] swapper pgtable: 4k pages, 48-bit VAs, pgdp=1496c000 [ 15.348795] [fff8] pgd=, p4d= [ 15.355524] Internal error: Oops: 9604 [#1] PREEMPT SMP [ 15.361729] Modules linked in: meson_gxl dwmac_generic snd_soc_meson_gx_sound_card snd_soc_meson_card_utils lima gpu_sched drm_shmem_helper meson_drm drm_dma_helper crct10dif_ce meson_ir rc_core meson_dw_hdmi dw_hdmi meson_canvas dwmac_meson8b stmmac_platform meson_rng stmmac rng_core cec meson_gxbb_wdt drm_display_helper snd_soc_meson_aiu snd_soc_meson_codec_glue pcs_xpcs snd_soc_meson_t9015 amlogic_gxl_crypto crypto_engine display_connector snd_soc_simple_amplifier drm_kms_helper drm nvmem_meson_efuse [ 15.405976] CPU: 1 PID: 9 Comm: kworker/u8:0 Not tainted 6.2.0-rc3-next-20230110 #1 [ 15.413563] Hardware name: Libre Computer AML-S905X-CC (DT) [ 15.419086] Workqueue: events_unbound deferred_probe_work_func [ 15.424863] pstate: 0005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 15.431762] pc : of_drm_find_bridge+0x38/0x70 [drm] [ 15.436594] lr : of_drm_find_bridge+0x20/0x70 [drm] [ 15.441423] sp : 8a04b9b0 [ 15.444700] x29: 8a04b9b0 x28: 08de5810 x27: 08de5808 [ 15.451772] x26: 08de5800 x25: 084cb8b0 x24: 01223c00 [ 15.458844] x23: x22: 0001 x21: 7fa61a28 [ 15.465917] x20: 084ca080 x19: 7fa61a28 x18: 019bd700 [ 15.472989] x17: 6d64685f77645f6e x16: x15: 0004 [ 15.480062] x14: 89bab410 x13: x12: 0003 [ 15.487135] x11: x10: x9 : [ 15.494207] x8 : 810a70a0 x7 : 64410079616b6f01 x6 : 80416403 [ 15.501279] x5 : 03644100 x4 : 0080 x3 : 00416400 [ 15.508352] x2 : 01128000 x1 : x0 : [ 15.515426] Call trace: [ 15.517863] Insufficient stack space to handle exception! [ 15.517867] ESR: 0x9647 -- DABT (current EL) [ 15.517871] FAR: 0x8a047ff0 [ 15.517873] Task stack: [0x8a048000..0x8a04c000] [ 15.517877] IRQ stack: [0x88008000..0x8800c000] [ 15.517880] Overflow stack: [0x7d9c1320..0x7d9c2320] [ 15.517884] CPU: 1 PID: 9 Comm: kworker/u8:0 Not tainted 6.2.0-rc3-next-20230110 #1 [ 15.517890] Hardware name: Libre Computer AML-S905X-CC (DT) [ 15.517895] Workqueue: events_unbound deferred_probe_work_func [ 15.517915] pstate: 83c5 (Nzcv DAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 15.517923] pc : el1_abort+0x4/0x5c [ 15.517932] lr : el1h_64_sync_handler+0x60/0xac [ 15.517939] sp : 8a048020 [ 15.517941] x29: 8a048020 x28: 01128000 x27: 08de5808 [ 15.517950] x26: 08de5800 x25: 8a04b608 x24: 01128000 [ 15.517957] x23: a0c5 x22: 880321dc x21: 8a048180 [ 15.517965] x20: 898e1000 x19: 8a048290 x18: 019bd700 [ 15.517972] x17: 0011 x16: x15: 0004 [ 15.517979] x14: 89bab410 x13: x12: [ 15.517986] x11: 0030 x10: 89013a1c x9 : 890401a0 [ 15.517994] x8 : 0025 x7 : 205d363234353135 x6 : 352e35312020205b [ 15.518001] x5 : 89f766b7 x4 : 88fe695c x3 : 000c [ 15.518008] x2 : 9604 x1 : 9604 x0 : 8a048030 [ 15.518017] Kernel panic - not syncing: kernel stack overflow [ 15.518020] SMP: stopping secondary CPUs [ 15.518027] Kernel Offset: disabled [ 15.518029] CPU features: 0x0,01000100,421b [ 15.518034] Memory Limit: none [ 15.679388] ---[ end Kernel panic - not syncing: kernel stack overflow ]--- [1] https://storage.kernelci.org/next/master/next-20230110/arm64/defconfig/clang-16/lab-broonie/kselftest-arm64-meson-gxl-s905x-libretech-cc.html
next: arm64: ERROR: modpost: "kunit_running" [drivers/gpu/drm/vc4/vc4.ko] undefined!
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_COMPILE_COMPAT=arm-linux-gnueabihf- ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc' 'HOSTCC=sccache gcc' olddefconfig .config:10084:warning: override: TRANSPARENT_HUGEPAGE_MADVISE changes choice state make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc' 'HOSTCC=sccache gcc' In file included from /builds/linux/include/asm-generic/rwonce.h:26, from /builds/linux/arch/arm64/include/asm/rwonce.h:71, from /builds/linux/include/linux/compiler.h:247, from /builds/linux/include/linux/export.h:33, from /builds/linux/include/linux/linkage.h:7, from /builds/linux/include/linux/kernel.h:17, from /builds/linux/fs/btrfs/ioctl.c:6: /builds/linux/include/linux/kasan-checks.h: In function 'btrfs_ioctl_wait_sync': /builds/linux/include/linux/kasan-checks.h:38:27: warning: 'transid' may be used uninitialized [-Wmaybe-uninitialized] 38 | #define kasan_check_write __kasan_check_write | ^~~ /builds/linux/include/linux/kasan-checks.h:20:6: note: by argument 1 of type 'const volatile void *' to '__kasan_check_write' declared here 20 | bool __kasan_check_write(const volatile void *p, unsigned int size); | ^~~ /builds/linux/fs/btrfs/ioctl.c:3134:13: note: 'transid' declared here 3134 | u64 transid; | ^~~ /builds/linux/include/linux/kasan-checks.h: In function 'btrfs_ioctl': /builds/linux/include/linux/kasan-checks.h:38:27: warning: 'space_args' may be used uninitialized [-Wmaybe-uninitialized] 38 | #define kasan_check_write __kasan_check_write | ^~~ /builds/linux/include/linux/kasan-checks.h:20:6: note: by argument 1 of type 'const volatile void *' to '__kasan_check_write' declared here 20 | bool __kasan_check_write(const volatile void *p, unsigned int size); | ^~~ /builds/linux/fs/btrfs/ioctl.c:2973:39: note: 'space_args' declared here 2973 | struct btrfs_ioctl_space_args space_args; | ^~ /builds/linux/include/linux/kasan-checks.h:38:27: warning: 'args32' may be used uninitialized [-Wmaybe-uninitialized] 38 | #define kasan_check_write __kasan_check_write | ^~~ /builds/linux/include/linux/kasan-checks.h:20:6: note: by argument 1 of type 'const volatile void *' to '__kasan_check_write' declared here 20 | bool __kasan_check_write(const volatile void *p, unsigned int size); | ^~~ /builds/linux/fs/btrfs/ioctl.c:4320:49: note: 'args32' declared here 4320 | struct btrfs_ioctl_send_args_32 args32; | ^~ ERROR: modpost: "kunit_running" [drivers/gpu/drm/vc4/vc4.ko] undefined! make[2]: *** [/builds/linux/scripts/Makefile.modpost:137: Module.symvers] Error 1 make[2]: Target '__modpost' not remade because of errors. make[1]: *** [/builds/linux/Makefile:1967: modpost] Error 2 build log: --- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230105/testrun/13988421/suite/build/test/gcc-12-lkftconfig-kunit/log Easy steps to reproduce with tuxmake: - # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake # # See https://docs.tuxmake.org/ for complete documentation. # Original tuxmake command with fragments listed below. # tuxmake --runtime podman --target-arch arm64 --toolchain gcc-12 --kconfig defconfig --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/lkft.config --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/lkft-crypto.config --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/distro-overrides.config --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/systemd.config --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/virtio.config --kconfig-add CONFIG_ARM64_MODULE_PLTS=y --kconfig-add CONFIG_SYN_COOKIES=y --kconfig-add CONFIG_SCHEDSTATS=y --kconfig-add CONFIG_KASAN=y --kconfig-add CONFIG_KUNIT=y --kconfig-add CONFIG_KUNIT_ALL_TESTS=y CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- tuxmake --runtime podman --target-arch arm64
not ok 1 - single_pixel_source_buffer: The buggy address belongs to the physical page
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] # Subtest: drm_test_fb_xrgb_to_xrgb2101010 [ 50.322059] == [ 50.326436] BUG: KASAN: slab-out-of-bounds in drm_test_fb_xrgb_to_xrgb2101010+0x2dd/0x520 [ 50.329249] Read of size 4 at addr 888104d7a5cc by task kunit_try_catch/619 [ 50.331596] [ 50.332135] CPU: 1 PID: 619 Comm: kunit_try_catch Tainted: GB N 6.0.0 #1 [ 50.333876] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [ 50.335138] Call Trace: [ 50.335531] [ 50.335879] dump_stack_lvl+0x49/0x62 [ 50.336462] print_report.cold+0x5e/0x5d9 [ 50.337069] ? _raw_spin_unlock_irqrestore+0x33/0x60 [ 50.337820] ? update_kunit_status+0xee/0x160 [ 50.338494] ? drm_test_fb_xrgb_to_xrgb2101010+0x2dd/0x520 [ 50.339354] kasan_report+0xaa/0x130 [ 50.339905] ? drm_fb_xrgb_to_xrgb2101010+0xa0/0xd0 [ 50.340680] ? drm_test_fb_xrgb_to_xrgb2101010+0x2dd/0x520 [ 50.341576] __asan_load4+0x80/0xa0 [ 50.342112] drm_test_fb_xrgb_to_xrgb2101010+0x2dd/0x520 [ 50.342958] ? drm_test_fb_xrgb_to_gray8+0x470/0x470 [ 50.343778] ? update_load_avg+0x80/0xb80 [ 50.344407] ? update_cfs_group+0x22/0x160 [ 50.345036] ? load_balance+0x14d0/0x14d0 [ 50.345652] ? dequeue_entity+0x1f2/0x6a0 [ 50.346263] ? rcu_qs+0x1c/0x120 [ 50.346773] ? finish_task_switch.isra.0+0xe0/0x410 [ 50.347532] ? __kasan_check_write+0x14/0x20 [ 50.348192] ? _raw_spin_lock_irqsave+0x9e/0x100 [ 50.348891] ? _raw_spin_unlock_irqrestore+0x28/0x60 [ 50.349625] ? trace_preempt_on+0x2a/0xf0 [ 50.350242] ? __kthread_parkme+0x4f/0xd0 [ 50.350857] kunit_try_run_case+0x91/0xd0 [ 50.351479] ? kunit_catch_run_case+0x80/0x80 [ 50.352151] ? kunit_try_catch_throw+0x40/0x40 [ 50.352897] kunit_generic_run_threadfn_adapter+0x2f/0x50 [ 50.353890] kthread+0x179/0x1b0 [ 50.354410] ? kthread_complete_and_exit+0x30/0x30 [ 50.355126] ret_from_fork+0x22/0x30 [ 50.355708] [ 50.356047] [ 50.356284] Allocated by task 619: [ 50.356817] kasan_save_stack+0x26/0x50 [ 50.357410] __kasan_kmalloc+0xae/0xe0 [ 50.357980] __kmalloc+0x1cf/0x390 [ 50.358501] kunit_kmalloc_array_init+0x4b/0x80 [ 50.359189] __kunit_add_resource+0x67/0x100 [ 50.359859] kunit_kmalloc_array+0xf8/0x170 [ 50.360490] drm_test_fb_xrgb_to_xrgb2101010+0x19f/0x520 [ 50.361341] kunit_try_run_case+0x91/0xd0 [ 50.361948] kunit_generic_run_threadfn_adapter+0x2f/0x50 [ 50.362747] kthread+0x179/0x1b0 [ 50.363230] ret_from_fork+0x22/0x30 [ 50.363779] [ 50.364015] The buggy address belongs to the object at 888104d7a5c8 [ 50.364015] which belongs to the cache kmalloc-8 of size 8 [ 50.365824] The buggy address is located 4 bytes inside of [ 50.365824] 8-byte region [888104d7a5c8, 888104d7a5d0) [ 50.367485] [ 50.367736] The buggy address belongs to the physical page: [ 50.368579] page:3c09c153 refcount:1 mapcount:0 mapping: index:0x0 pfn:0x104d7a [ 50.369991] flags: 0x2000200(slab|node=0|zone=2) [ 50.370804] raw: 02000200 dead0122 888100042280 [ 50.371933] raw: 80660066 0001 [ 50.373021] page dumped because: kasan: bad access detected [ 50.373958] [ 50.374202] Memory state around the buggy address: [ 50.374935] 888104d7a480: fc fb fc fc fc fc fb fc fc fc fc fb fc fc fc fc [ 50.376019] 888104d7a500: fb fc fc fc fc fb fc fc fc fc fb fc fc fc fc fb [ 50.377098] >888104d7a580: fc fc fc fc fa fc fc fc fc 04 fc fc fc fc fa fc [ 50.378174] ^ [ 50.379025] 888104d7a600: fc fc fc fa fc fc fc fc fa fc fc fc fc fa fc fc [ 50.380123] 888104d7a680: fc fc 00 fc fc fc fc fa fc fc fc fc fa fc fc fc [ 50.381191] == [ 50.382461] not ok 1 - single_pixel_source_buffer [ 50.382909] ok 2 - single_pixel_clip_rectangle [ 50.384319] ok 3 - well_known_colors [ 50.385393] ok 4 - destination_pitch [ 50.386029] # drm_test_fb_xrgb_to_xrgb2101010: pass:3 fail:1 skip:0 total:4 [ 50.386657] not ok 5 - drm_test_fb_xrgb_to_xrgb2101010 [ 50.387762] # drm_format_helper_test: pass:4 fail:1 skip:0 total:5 [ 50.388598] # Totals: pass:19 fail:1 skip:0 total:20 [ 50.389467] not ok 33 - drm_format_helper_test Test log link, https://lkft.validation.linaro.org/scheduler/job/5633513#L7056
kunit: drm_framebuffer: kernel BUG at drivers/gpu/drm/drm_buddy.c
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 Crash log: [ 38.366527] ok 39 - drm_framebuffer [ 38.367919] # Subtest: drm_buddy [ 38.367921] 1..6 [ 38.368686] [ cut here ] [ 38.370089] kernel BUG at drivers/gpu/drm/drm_buddy.c:140! [ 38.37] invalid opcode: [#1] PREEMPT SMP [ 38.372003] CPU: 1 PID: 654 Comm: kunit_try_catch Tainted: GB N 6.1.0-rc1 #1 [ 38.373486] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [ 38.374972] EIP: drm_buddy_init+0x2c0/0x340 [ 38.375767] Code: 21 29 c1 83 f9 33 0f 86 27 ff ff ff 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 <0f> 0b 8d b6 00 00 00 00 0f bd 45 0c 0f 44 c1 83 c0 21 e9 e0 fd ff [ 38.379066] EAX: c1379898 EBX: c1aaf0a0 ECX: c1aaf090 EDX: c1aaf0b8 [ 38.380196] ESI: 0034 EDI: c2bcff20 EBP: c2bcfebc ESP: c2bcfe8c [ 38.381308] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS: 00010297 [ 38.382507] CR0: 80050033 CR2: f4f5e000 CR3: 0f947000 CR4: 003506d0 [ 38.383659] DR0: cf9aada4 DR1: cf9aada9 DR2: cf9aadaa DR3: cf9aadab [ 38.384760] DR6: 0ff0 DR7: 0600 [ 38.385441] Call Trace: [ 38.385909] drm_test_buddy_alloc_limit+0x47/0x3c0 [ 38.386772] ? __switch_to_asm+0x8f/0xf0 [ 38.387488] ? __switch_to_asm+0x89/0xf0 [ 38.388192] ? __switch_to_asm+0x83/0xf0 [ 38.388903] ? finish_task_switch+0x80/0x2b0 [ 38.389670] ? __schedule+0x2dc/0xac0 [ 38.390325] ? trace_hardirqs_on+0x36/0xf0 [ 38.391066] ? finish_task_switch+0x80/0x2b0 [ 38.391848] ? __switch_to+0x18/0x1e0 [ 38.392505] ? drm_buddy_init_test+0x25/0x40 [ 38.393287] ? get_random_u32+0x8f/0xf0 [ 38.393991] ? drm_buddy_init_test+0x25/0x40 [ 38.394775] kunit_try_run_case+0x52/0x80 [ 38.395524] ? trace_hardirqs_on+0x36/0xf0 [ 38.396259] kunit_generic_run_threadfn_adapter+0x16/0x20 [ 38.397231] kthread+0xe0/0x110 [ 38.397820] ? kunit_try_catch_throw+0x20/0x20 [ 38.398620] ? kthread_complete_and_exit+0x20/0x20 [ 38.399503] ret_from_fork+0x1c/0x28 [ 38.400174] Modules linked in: [ 38.400781] ---[ end trace ]--- [ 38.401623] EIP: drm_buddy_init+0x2c0/0x340 [ 38.402374] Code: 21 29 c1 83 f9 33 0f 86 27 ff ff ff 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 <0f> 0b 8d b6 00 00 00 00 0f bd 45 0c 0f 44 c1 83 c0 21 e9 e0 fd ff [ 38.405711] EAX: c1379898 EBX: c1aaf0a0 ECX: c1aaf090 EDX: c1aaf0b8 [ 38.406830] ESI: 0034 EDI: c2bcff20 EBP: c2bcfebc ESP: c2bcfe8c [ 38.407976] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS: 00010297 [ 38.409186] CR0: 80050033 CR2: f4f5e000 CR3: 0f947000 CR4: 003506d0 login-action: exception [login-action] Waiting for messages, (timeout 00:09:56) [ 38.410313] DR0: cf9aada4 DR1: cf9aada9 DR2: cf9aadaa DR3: cf9aadab [ 38.411481] DR6: 0ff0 DR7: 0600 [ 365.847635] # drm_test_buddy_alloc_limit: try timed out [ 365.848890] [ cut here ] [ 365.849823] refcount_t: addition on 0; use-after-free. [ 365.850822] WARNING: CPU: 3 PID: 1 at lib/refcount.c:25 refcount_warn_saturate+0x84/0x120 [ 365.852421] Modules linked in: [ 365.853055] CPU: 3 PID: 1 Comm: swapper/0 Tainted: GB D N 6.1.0-rc1 #1 [ 365.854612] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [ 365.856032] EIP: refcount_warn_saturate+0x84/0x120 [ 365.856931] Code: cf e8 bb 9a a1 00 0f 0b eb cf 8d 74 26 00 80 3d 54 c7 7d cf 00 75 c2 c7 04 24 90 41 43 cf b0 01 a2 54 c7 7d cf e8 97 9a a1 00 <0f> 0b eb ab 8d b4 26 00 00 00 00 90 80 3d 56 c7 7d cf 00 75 9a c7 [ 365.860283] EAX: 002a EBX: c23a ECX: ce17a1d2 EDX: [ 365.861373] ESI: c23a0018 EDI: c23a EBP: c11cdc90 ESP: c11cdc8c [ 365.862567] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS: 00010296 [ 365.863917] CR0: 80050033 CR2: CR3: 0f947000 CR4: 003506d0 [ 365.865113] DR0: cf9aadac DR1: cf9aadad DR2: cf9aadae DR3: cf9aadaf [ 365.866330] DR6: 0ff0 DR7: 0600 [ 365.867157] Call Trace: [ 365.867736] kthread_stop+0x184/0x190 [ 365.868480] kunit_try_catch_run.cold+0x7b/0xc1 [ 365.869373] kunit_run_case_catch_errors+0x6e/0xa8 [ 365.870394] kunit_run_tests.cold+0x1c4/0x5fe [ 365.871218] ? kunit_catch_run_case+0x50/0x50 [ 365.872153] ? kunit_module_notify+0x90/0x90 [ 365.872945] ? up_write+0x37/0x70 [ 365.873565] ? preempt_count_sub+0xc1/0x110 [ 365.874356] ? preempt_count_add+0x6c/0xd0 [ 365.875120] ? up_write+0x37/0x70 [ 365.875723] ? __debugfs_create_file+0xdb/0x1a0 [ 365.876625] ? up_write+0x37/0x70 [ 365.877264] ? debugfs_create_file+0x3c/0x50 [ 365.878134] ? kunit_debugfs_create_suite+0x90/0xa0 [
v5.19-rc5: igt-test: Unable to handle kernel write to read-only memory at virtual address - drm_dev_unregister
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: 88084a3df1672e131ddc1b4e39eeacfd39864acf git_describe: v5.19-rc5 kernel_version: 5.19.0-rc5 kernel-config: https://builds.tuxbuild.com/2BSEyt8Sb19HSj6SnBFiMo6kiQh/config build-url: https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline/-/pipelines/579007773 artifact-location: https://builds.tuxbuild.com/2BSEyt8Sb19HSj6SnBFiMo6kiQh vmlinux.xz: https://builds.tuxbuild.com/2BSEyt8Sb19HSj6SnBFiMo6kiQh/vmlinux.xz System.map: https://builds.tuxbuild.com/2BSEyt8Sb19HSj6SnBFiMo6kiQh/System.map toolchain: gcc-11 igt-gpu-tools__url: https://gitlab.freedesktop.org/drm/igt-gpu-tools + ./igt-test.sh -d /usr/share/igt-gpu-tools -t CHAMELIUM -c 10.66.16.71 -h HDMI-A-1 Going to run igt Chamelium test Generate ~/.igtrc Generate Chamelium test list igt@kms_chamelium@hdmi-hpd igt@kms_chamelium@hdmi-hpd-fast Subtest hdmi-hpd-storm-disable: SKIP (0.000s) [181.885373] [08/88] kms_chamelium (hdmi-crc-single) [ 181.932031] Console: switching to colour dummy device 80x25 [ 181.932276] [IGT] kms_chamelium: executing [ 182.178035] [IGT] kms_chamelium: starting subtest hdmi-crc-single [ 183.696310] [drm:mdp5_irq_error_handler [msm]] *ERROR* errors: 0400 [ 186.819771] msm_mdp 1a01000.mdp: vblank time out, crtc=0 [ 197.407969] [IGT] kms_chamelium: exiting, ret=98 [ 198.123226] Console: switching to colour frame buffer device 240x67 [ 208.352251] msm_mdp 1a01000.mdp: [drm] *ERROR* flip_done timed out [ 208.352889] msm_mdp 1a01000.mdp: [drm] *ERROR* [CRTC:57:crtc-0] commit wait timed out [ 218.592308] msm_mdp 1a01000.mdp: [drm] *ERROR* flip_done timed out [ 218.592951] msm_mdp 1a01000.mdp: [drm] *ERROR* [PLANE:33:plane-0] commit wait timed out [ 218.598698] [ cut here ] [ 218.605711] WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c:807 mdp5_crtc_atomic_flush+0x1b8/0x1d0 [msm] [ 218.611025] Modules linked in: rfkill snd_soc_hdmi_codec venus_enc venus_dec videobuf2_dma_contig adv7511 pm8916_wdt smsc75xx cec qcom_wcnss_pil msm qrtr qcom_camss venus_core qcom_q6v5_mss videobuf2_dma_sg gpu_sched qcom_pil_info v4l2_fwnode qcom_q6v5 snd_soc_lpass_apq8016 drm_dp_aux_bus qcom_sysmon v4l2_async snd_soc_lpass_cpu v4l2_mem2mem drm_display_helper display_connector qcom_common videobuf2_memops qcom_glink_smem snd_soc_msm8916_analog snd_soc_msm8916_digital snd_soc_apq8016_sbc snd_soc_lpass_platform videobuf2_v4l2 qmi_helpers snd_soc_qcom_common drm_kms_helper qcom_spmi_vadc mdt_loader qcom_spmi_temp_alarm videobuf2_common rtc_pm8xxx drm qcom_vadc_common i2c_qcom_cci qnoc_msm8916 qcom_stats socinfo qcom_pon crct10dif_ce qcom_rng icc_smd_rpm rmtfs_mem fuse [ 218.671585] CPU: 0 PID: 6 Comm: kworker/0:0 Not tainted 5.19.0-rc5 #1 [ 218.689678] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [ 218.696036] Workqueue: events drm_mode_rmfb_work_fn [drm] [ 218.702723] pstate: 6005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 218.708118] pc : mdp5_crtc_atomic_flush+0x1b8/0x1d0 [msm] [ 218.714784] lr : mdp5_crtc_atomic_flush+0x44/0x1d0 [msm] [ 218.720337] sp : 88053b10 [ 218.725571] x29: 88053b10 x28: 0001 x27: 0ca3c2c8 [ 218.729045] x26: x25: x24: 0020 [ 218.736165] x23: 0070 x22: 0038 x21: 0f374200 [ 218.743281] x20: 0ca3e000 x19: 0ca3c000 x18: 0001 [ 218.750398] x17: 0004 x16: x15: [ 218.757516] x14: 0020 x13: x12: 0020 [ 218.764635] x11: x10: 04f1e678 x9 : 81566000 [ 218.771753] x8 : 03295140 x7 : x6 : [ 218.778871] x5 : 0ca3e000 x4 : x3 : [ 218.785987] x2 : x1 : x0 : 023d0980 [ 218.793108] Call trace: [ 218.799906] mdp5_crtc_atomic_flush+0x1b8/0x1d0 [msm] [ 218.802347] drm_atomic_helper_commit_planes+0x160/0x210 [drm_kms_helper] [ 218.807678] msm_atomic_commit_tail+0x1b0/0x8d0 [msm] [ 218.814327] commit_tail+0xac/0x184 [drm_kms_helper] [ 218.819355] drm_atomic_helper_commit+0x150/0x37c [drm_kms_helper] [ 218.824471] drm_atomic_commit+0xb0/0xf0 [drm] [ 218.830345] drm_framebuffer_remove+0x444/0x4e4 [drm] [ 218.834813] drm_mode_rmfb_work_fn+0x84/0xac [drm] [ 218.839919] process_one_work+0x1dc/0x450 [ 218.844544] worker_thread+0x2d0/0x450 [ 218.848605] kthread+0x100/0x110 [ 218.852216] ret_from_fork+0x10/0x20 [ 218.855630] ---[ end trace ]--- [ 218.920029] msm_mdp 1a01000.mdp: vblank time out, crtc=0 [ 229.088439] msm_mdp
[next] Rpi4 : WARNING: at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:487 vc5_hdmi_reset+0x1f0/0x240 [vc4]
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) (aarch64-linux-gnu-gcc (Debian 11.3.0-3) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT @1656576657 [0.00] Machine model: Raspberry Pi 4 Model B [ 21.702341] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22 [ 21.711580] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops [vc4]) [ 21.719271] [ cut here ] [ 21.723971] WARNING: CPU: 0 PID: 246 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:487 vc5_hdmi_reset+0x1f0/0x240 [vc4] [ 21.734403] Modules linked in: cfg80211(+) raspberrypi_hwmon clk_raspberrypi bluetooth reset_raspberrypi crct10dif_ce vc4(+) cec drm_display_helper rfkill iproc_rng200 drm_cma_helper drm_kms_helper pwm_bcm2835 i2c_bcm2835 rng_core v3d bcm2711_thermal drm_shmem_helper gpu_sched pcie_brcmstb drm fuse [ 21.761318] CPU: 0 PID: 246 Comm: systemd-udevd Not tainted 5.19.0-rc4-next-20220630 #1 [ 21.769445] Hardware name: Raspberry Pi 4 Model B (DT) [ 21.774656] pstate: 60c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 21.781725] pc : vc5_hdmi_reset+0x1f0/0x240 [vc4] [ 21.786587] lr : vc5_hdmi_reset+0x38/0x240 [vc4] [ 21.791356] sp : 8b533630 [ 21.794715] x29: 8b533630 x28: x27: 411d4080 [ 21.801967] x26: x25: 89cdd980 x24: 8ae15410 [ 21.809218] x23: 40fce000 x22: fb83a978 x21: [ 21.816467] x20: 411d4cf0 x19: 411d4080 x18: [ 21.823716] x17: x16: x15: [ 21.830963] x14: x13: 0030 x12: 0101010101010101 [ 21.838211] x11: 7f7f7f7f7f7f7f7f x10: 84000386a50f x9 : 893b1660 [ 21.845460] x8 : 0101010101010101 x7 : x6 : 0001 [ 21.852709] x5 : 8a9bf2e0 x4 : 8a9bf000 x3 : [ 21.859958] x2 : 0001 x1 : 0002 x0 : 81587ae8 [ 21.867207] Call trace: [ 21.869684] vc5_hdmi_reset+0x1f0/0x240 [vc4] [ 21.874188] vc4_hdmi_runtime_resume+0x74/0xb0 [vc4] [ 21.879308] vc4_hdmi_bind+0x22c/0x880 [vc4] [ 21.880064] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 21.883719] component_bind_all+0x130/0x290 [ 21.883747] vc4_drm_bind+0x19c/0x2a4 [vc4] [ 21.900105] try_to_bring_up_aggregate_device+0x1f8/0x300 [ 21.905597] component_master_add_with_match+0xbc/0x104 [ 21.910910] vc4_platform_drm_probe+0xcc/0x10c [vc4] [ 21.916028] platform_probe+0x74/0xf0 [ 21.919750] really_probe+0xc8/0x3e0 [ 21.923385] __driver_probe_device+0x84/0x190 [ 21.927811] driver_probe_device+0x44/0x100 [ 21.932062] __driver_attach+0xd8/0x210 [ 21.935959] bus_for_each_dev+0x7c/0xe0 [ 21.939857] driver_attach+0x30/0x3c [ 21.943489] bus_add_driver+0x188/0x244 [ 21.947384] driver_register+0x84/0x140 [ 21.951282] __platform_driver_register+0x34/0x40 [ 21.956055] vc4_drm_register+0x5c/0x1000 [vc4] [ 21.960730] do_one_initcall+0x50/0x2b0 [ 21.964628] do_init_module+0x50/0x200 [ 21.968440] load_module+0x1a8c/0x1f40 [ 21.972243] __do_sys_finit_module+0xac/0x12c [ 21.976663] __arm64_sys_finit_module+0x2c/0x40 [ 21.981259] invoke_syscall+0x50/0x120 [ 21.985069] el0_svc_common.constprop.0+0x104/0x124 [ 21.990024] do_el0_svc+0x3c/0xd0 [ 21.993392] el0_svc+0x38/0xc0 [ 21.996494] el0t_64_sync_handler+0xbc/0x140 [ 22.000828] el0t_64_sync+0x18c/0x190 [ 22.004544] ---[ end trace ]--- [ 22.009327] [ cut here ] [ 22.014009] WARNING: CPU: 0 PID: 246 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:457 vc4_hdmi_read+0xec/0x134 [vc4] [ 22.024243] Modules linked in: cfg80211(+) raspberrypi_hwmon clk_raspberrypi bluetooth reset_raspberrypi crct10dif_ce vc4(+) cec drm_display_helper rfkill iproc_rng200 drm_cma_helper drm_kms_helper pwm_bcm2835 i2c_bcm2835 rng_core v3d bcm2711_thermal drm_shmem_helper gpu_sched pcie_brcmstb drm fuse [ 22.051149] CPU: 0 PID: 246 Comm: systemd-udevd Tainted: GW 5.19.0-rc4-next-20220630 #1 [ 22.060684] Hardware name: Raspberry Pi 4 Model B (DT) [ 22.065894] pstate: 60c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 22.072959] pc : vc4_hdmi_read+0xec/0x134 [vc4] [ 22.077631] lr : vc5_hdmi_reset+0xac/0x240 [vc4] metadata: git_ref: master git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next git_sha: 6cc11d2a1759275b856e464265823d94aabd5eaf git_describe: next-20220630 kernel_version: 5.19.0-rc4 kernel-config: https://builds.tuxbuild.com/2BHwwIpQQ4jA4OQSp6ecOQNPxTg/config build-url:
Re: [PATCH] drm/msm/gpu: Fix crash on devices without devfreq support
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.
> >
> > Reported-by: Linux Kernel Functional Testing
> > Reported-by: Anders Roxell
> > Signed-off-by: Rob Clark
>
> I have tested this patch and the reported kernel crash is fixed [1].
>
> Tested-by: Linux Kernel Functional Testing
>
> > ---
> > drivers/gpu/drm/msm/msm_gpu_devfreq.c | 31 +--
> > 1 file changed, 25 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> > b/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> > index 9bf319be11f6..26a3669a97b3 100644
> > --- a/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> > +++ b/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> > @@ -83,12 +83,17 @@ static struct devfreq_dev_profile msm_devfreq_profile =
> > {
> > static void msm_devfreq_boost_work(struct kthread_work *work);
> > static void msm_devfreq_idle_work(struct kthread_work *work);
> >
> > +static bool has_devfreq(struct msm_gpu *gpu)
> > +{
> > + return !!gpu->funcs->gpu_busy;
> > +}
> > +
> > void msm_devfreq_init(struct msm_gpu *gpu)
> > {
> > struct msm_gpu_devfreq *df = >devfreq;
> >
> > /* We need target support to do devfreq */
> > - if (!gpu->funcs->gpu_busy)
> > + if (!has_devfreq(gpu))
> > return;
> >
> > dev_pm_qos_add_request(>pdev->dev, >idle_freq,
> > @@ -149,6 +154,9 @@ void msm_devfreq_cleanup(struct msm_gpu *gpu)
> > {
> > struct msm_gpu_devfreq *df = >devfreq;
> >
> > + if (!has_devfreq(gpu))
> > + return;
> > +
> > devfreq_cooling_unregister(gpu->cooling);
> > dev_pm_qos_remove_request(>boost_freq);
> > dev_pm_qos_remove_request(>idle_freq);
> > @@ -156,16 +164,24 @@ void msm_devfreq_cleanup(struct msm_gpu *gpu)
> >
> > void msm_devfreq_resume(struct msm_gpu *gpu)
> > {
> > - gpu->devfreq.busy_cycles = 0;
> > - gpu->devfreq.time = ktime_get();
> > + struct msm_gpu_devfreq *df = >devfreq;
> >
> > - devfreq_resume_device(gpu->devfreq.devfreq);
> > + if (!has_devfreq(gpu))
> > + return;
> > +
> > + df->busy_cycles = 0;
> > + df->time = ktime_get();
> > +
> > + devfreq_resume_device(df->devfreq);
> > }
> >
> > void msm_devfreq_suspend(struct msm_gpu *gpu)
> > {
> > struct msm_gpu_devfreq *df = >devfreq;
> >
> > + if (!has_devfreq(gpu))
> > + return;
> > +
> > devfreq_suspend_device(df->devfreq);
> >
> > cancel_idle_work(df);
> > @@ -185,6 +201,9 @@ void msm_devfreq_boost(struct msm_gpu *gpu, unsigned
> > factor)
> > struct msm_gpu_devfreq *df = >devfreq;
> > uint64_t freq;
> >
> > + if (!has_devfreq(gpu))
> > + return;
> > +
> > freq = get_freq(gpu);
> > freq *= factor;
> >
> > @@ -207,7 +226,7 @@ void msm_devfreq_active(struct msm_gpu *gpu)
> > struct devfreq_dev_status status;
> > unsigned int idle_time;
> >
> > - if (!df->devfreq)
> > + if (!has_devfreq(gpu))
> > return;
> >
> > /*
> > @@ -253,7 +272,7 @@ void msm_devfreq_idle(struct msm_gpu *gpu)
> > {
> > struct msm_gpu_devfreq *df = >devfreq;
> >
> > - if (!df->devfreq)
> > + if (!has_devfreq(gpu))
> > return;
> >
> > msm_hrtimer_queue_work(>idle_work, ms_to_ktime(1),
FYI,
This patch is missing on Linux 5.17-rc8 [1].
kernel crash log on arm64 db410c device [2] and details [3].
metadata:
git_describe: v5.17-rc8
git_ref: master
git_repo: https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline
git_sha: 09688c0166e76ce2fb85e86b9d99be8b0084cdf9
kernel-config: https://builds.tuxbuild.com/26LbbVLHqxjh5w5ZtjBMjGmh92P/config
build: https://builds.tuxbuild.com/26LbbVLHqxjh5w5ZtjBMjGmh92P
- Naresh
[1]
https://lore.kernel.org/dri-devel/20220219183310.557435-1-robdcl...@gmail.com/
[2] https://lkft.validation.linaro.org/scheduler/job/4714905#L2795
[3]
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v5.17-rc8/testrun/8446224/suite/linux-log-parser/test/check-kernel-oops-4714905/details/
>
> --
> Linaro LKFT
> https://lkft.linaro.org
>
> [1] https://lkft.validation.linaro.org/scheduler/job/4664600#L1894
Re: [PATCH 5.15 000/262] 5.15.27-rc1 review
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. > > Responses should be made by Wed, 09 Mar 2022 09:16:25 +. > 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.15.27-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.15.y > and the diffstat can be found below. > > thanks, > > greg k-h Following build errors/warnings noticed on arm64. arch/arm64/net/bpf_jit_comp.c: In function 'build_insn': arch/arm64/net/bpf_jit_comp.c:791:21: error: implicit declaration of function 'bpf_pseudo_func' [-Werror=implicit-function-declaration] 791 | if (bpf_pseudo_func(insn)) | ^~~ cc1: some warnings being treated as errors drivers/gpu/drm/mediatek/mtk_dsi.c: In function 'mtk_dsi_host_attach': drivers/gpu/drm/mediatek/mtk_dsi.c:858:28: error: implicit declaration of function 'devm_drm_of_get_bridge'; did you mean 'devm_drm_panel_bridge_add'? [-Werror=implicit-function-declaration] 858 | dsi->next_bridge = devm_drm_of_get_bridge(dev, dev->of_node, 0, 0); |^~ |devm_drm_panel_bridge_add drivers/gpu/drm/mediatek/mtk_dsi.c:858:26: warning: assignment to 'struct drm_bridge *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 858 | dsi->next_bridge = devm_drm_of_get_bridge(dev, dev->of_node, 0, 0); | ^ cc1: some warnings being treated as errors Reported-by: Linux Kernel Functional Testing Build log [1]. -- Linaro LKFT https://lkft.linaro.org [1] https://builds.tuxbuild.com/263ZKyWWLLcPGRbiZwIEZw3wvXX/
Re: [PATCH] drm/msm/gpu: Fix crash on devices without devfreq support
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 the reported kernel crash is fixed [1].
Tested-by: Linux Kernel Functional Testing
> ---
> drivers/gpu/drm/msm/msm_gpu_devfreq.c | 31 +--
> 1 file changed, 25 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> b/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> index 9bf319be11f6..26a3669a97b3 100644
> --- a/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> +++ b/drivers/gpu/drm/msm/msm_gpu_devfreq.c
> @@ -83,12 +83,17 @@ static struct devfreq_dev_profile msm_devfreq_profile = {
> static void msm_devfreq_boost_work(struct kthread_work *work);
> static void msm_devfreq_idle_work(struct kthread_work *work);
>
> +static bool has_devfreq(struct msm_gpu *gpu)
> +{
> + return !!gpu->funcs->gpu_busy;
> +}
> +
> void msm_devfreq_init(struct msm_gpu *gpu)
> {
> struct msm_gpu_devfreq *df = >devfreq;
>
> /* We need target support to do devfreq */
> - if (!gpu->funcs->gpu_busy)
> + if (!has_devfreq(gpu))
> return;
>
> dev_pm_qos_add_request(>pdev->dev, >idle_freq,
> @@ -149,6 +154,9 @@ void msm_devfreq_cleanup(struct msm_gpu *gpu)
> {
> struct msm_gpu_devfreq *df = >devfreq;
>
> + if (!has_devfreq(gpu))
> + return;
> +
> devfreq_cooling_unregister(gpu->cooling);
> dev_pm_qos_remove_request(>boost_freq);
> dev_pm_qos_remove_request(>idle_freq);
> @@ -156,16 +164,24 @@ void msm_devfreq_cleanup(struct msm_gpu *gpu)
>
> void msm_devfreq_resume(struct msm_gpu *gpu)
> {
> - gpu->devfreq.busy_cycles = 0;
> - gpu->devfreq.time = ktime_get();
> + struct msm_gpu_devfreq *df = >devfreq;
>
> - devfreq_resume_device(gpu->devfreq.devfreq);
> + if (!has_devfreq(gpu))
> + return;
> +
> + df->busy_cycles = 0;
> + df->time = ktime_get();
> +
> + devfreq_resume_device(df->devfreq);
> }
>
> void msm_devfreq_suspend(struct msm_gpu *gpu)
> {
> struct msm_gpu_devfreq *df = >devfreq;
>
> + if (!has_devfreq(gpu))
> + return;
> +
> devfreq_suspend_device(df->devfreq);
>
> cancel_idle_work(df);
> @@ -185,6 +201,9 @@ void msm_devfreq_boost(struct msm_gpu *gpu, unsigned
> factor)
> struct msm_gpu_devfreq *df = >devfreq;
> uint64_t freq;
>
> + if (!has_devfreq(gpu))
> + return;
> +
> freq = get_freq(gpu);
> freq *= factor;
>
> @@ -207,7 +226,7 @@ void msm_devfreq_active(struct msm_gpu *gpu)
> struct devfreq_dev_status status;
> unsigned int idle_time;
>
> - if (!df->devfreq)
> + if (!has_devfreq(gpu))
> return;
>
> /*
> @@ -253,7 +272,7 @@ void msm_devfreq_idle(struct msm_gpu *gpu)
> {
> struct msm_gpu_devfreq *df = >devfreq;
>
> - if (!df->devfreq)
> + if (!has_devfreq(gpu))
> return;
>
> msm_hrtimer_queue_work(>idle_work, ms_to_ktime(1),
> --
> 2.34.1
--
Linaro LKFT
https://lkft.linaro.org
[1] https://lkft.validation.linaro.org/scheduler/job/4664600#L1894
[next] arm64: db410c: Internal error: Oops: 96000004 - msm_gpu_pm_suspend
[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_describe: next-20220302 kernel-config: https://builds.tuxbuild.com/25pJv2XjzFav5peWxwfhaU3LFEN/config Kernel crash: Failed to start Entropy Daemon based on the HAVEGE algorithm [ 12.104662] Unable to handle kernel NULL pointer dereference at virtual address 0010 [ 12.121151] ESR = 0x9604 [ 12.121211] EC = 0x25: DABT (current EL), IL = 32 bits [ 12.123137] SET = 0, FnV = 0 [ 12.128687] EA = 0, S1PTW = 0 [ 12.131464] FSC = 0x04: level 0 translation fault [ 12.134572] Data abort info: [ 12.139457] ISV = 0, ISS = 0x0004 [ 12.142566] CM = 0, WnR = 0 [ 12.146165] user pgtable: 4k pages, 48-bit VAs, pgdp=8235d000 [ 12.149360] [0010] pgd=, p4d= [ 12.156339] Internal error: Oops: 9604 [#1] PREEMPT SMP [ 12.162370] Modules linked in: videobuf2_dma_contig adv7511(+) crct10dif_ce qcom_wcnss_pil cec qrtr qcom_q6v5_mss qcom_camss snd_soc_lpass_apq8016 qcom_pil_info snd_soc_lpass_cpu rtc_pm8xxx videobuf2_dma_sg qcom_spmi_vadc snd_soc_msm8916_analog qcom_q6v5 snd_soc_msm8916_digital snd_soc_apq8016_sbc snd_soc_lpass_platform qcom_pon v4l2_fwnode snd_soc_qcom_common qcom_spmi_temp_alarm qcom_sysmon qcom_vadc_common venus_core msm qcom_common v4l2_async qcom_glink_smem qmi_helpers v4l2_mem2mem videobuf2_memops mdt_loader qnoc_msm8916 gpu_sched icc_smd_rpm display_connector drm_dp_helper videobuf2_v4l2 drm_kms_helper qcom_stats videobuf2_common qcom_rng i2c_qcom_cci rpmsg_char drm socinfo rmtfs_mem fuse [ 12.207393] CPU: 0 PID: 66 Comm: kworker/0:4 Not tainted 5.17.0-rc6-next-20220302 #1 [ 12.207407] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [ 12.207415] Workqueue: pm pm_runtime_work [ 12.243952] pstate: 6005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 12.247862] pc : hrtimer_active+0x14/0x80 [ 12.254628] lr : hrtimer_cancel+0x28/0x70 [ 12.258795] sp : 8b423b70 [ 12.262786] x29: 8b423b70 x28: x27: [ 12.266092] x26: 8ad5d2e0 x25: 0002d138d917 x24: 0d8dbb80 [ 12.273210] x23: 0326c010 x22: 0f6b2020 x21: 0f6b2000 [ 12.280328] x20: 0f6b20f8 x19: 0f6b2318 x18: [ 12.287447] x17: 800035bf3000 x16: 88004000 x15: 4000 [ 12.294564] x14: x13: x12: 8a8b7000 [ 12.301682] x11: 087facb61180 x10: 0bc0 x9 : 881d3a78 [ 12.308800] x8 : 03c68000 x7 : 0018 x6 : 1483ced5 [ 12.315918] x5 : 00ff x4 : x3 : [ 12.323036] x2 : x1 : x0 : 0f6b2318 [ 12.330156] Call trace: [ 12.337263] hrtimer_active+0x14/0x80 [ 12.339524] msm_devfreq_suspend+0x30/0x60 [msm] [ 12.343348] msm_gpu_pm_suspend+0x44/0x144 [msm] [ 12.348035] adreno_suspend+0x6c/0x174 [msm] [ 12.352634] pm_generic_runtime_suspend+0x38/0x50 [ 12.356885] genpd_runtime_suspend+0xb4/0x314 [ 12.361487] __rpm_callback+0x50/0x180 [ 12.365824] rpm_callback+0x74/0x80 [ 12.369470] rpm_suspend+0x110/0x634 [ 12.372856] pm_runtime_work+0xd0/0xd4 [ 12.376676] process_one_work+0x1dc/0x450 [ 12.380235] worker_thread+0x154/0x450 [ 12.384314] kthread+0x100/0x110 [ 12.387959] ret_from_fork+0x10/0x20 [ 12.391351] Code: aa1e03e9 d503201f d503233f f9401802 (b9401041) [ 12.394913] ---[ end trace ]--- Reported-by: Linux Kernel Functional Testing -- Linaro LKFT https://lkft.linaro.org [1] https://lkft.validation.linaro.org/scheduler/job/4643232#L2396
gpu/drm/dp/drm_dp.c:59:27: warning: array subscript 10 is outside array bounds of 'const u8[6]'
[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/lkft/mirrors/next/linux-next
git_sha: d4a0ae62a277377de396850ed4b709b6bd9b7326
git_describe: next-20220223
arch: riscv
toolchain: gcc-11
Build warnings:
---
drivers/gpu/drm/dp/drm_dp.c: In function
'drm_dp_get_adjust_request_post_cursor':
drivers/gpu/drm/dp/drm_dp.c:59:27: warning: array subscript 10 is
outside array bounds of 'const u8[6]' {aka 'const unsigned char[6]'}
[-Warray-bounds]
59 | return link_status[r - DP_LANE0_1_STATUS];
|~~~^~~
drivers/gpu/drm/dp/drm_dp.c:210:51: note: while referencing 'link_status'
210 | u8 drm_dp_get_adjust_request_post_cursor(const u8
link_status[DP_LINK_STATUS_SIZE],
|
~^~~~
make[1]: Target '__all' not remade because of errors.
Reported-by: Linux Kernel Functional Testing
Steps to reproduce:
--
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
tuxmake --runtime podman --target-arch riscv --toolchain gcc-11
--kconfig defconfig
--
Linaro LKFT
https://lkft.linaro.org
[1] https://builds.tuxbuild.com/25XO99nwfQgKrWKz4yfBPYw0wyU/
Re: [PATCH v2] drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP
Hi Thomas,
On Thu, 3 Feb 2022 at 15:09, Thomas Zimmermann wrote:
>
> As reported in [1], DRM_PANEL_EDP depends on DRM_DP_HELPER. Select
> the option to fix the build failure. The error message is shown
> below.
>
> arm-linux-gnueabihf-ld: drivers/gpu/drm/panel/panel-edp.o: in function
> `panel_edp_probe': panel-edp.c:(.text+0xb74): undefined reference to
> `drm_panel_dp_aux_backlight'
> make[1]: *** [/builds/linux/Makefile:1222: vmlinux] Error 1
>
> The issue has been reported before, when DisplayPort helpers were
> hidden behind 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-edp: Split eDP panels out of panel-simple")
> Reported-by: Naresh Kamboju
> Reported-by: Linux Kernel Functional Testing
> Link:
> https://lore.kernel.org/dri-devel/CA+G9fYvN0NyaVkRQmA1O6rX7H8PPaZrUAD7=rdy33qy9ruu...@mail.gmail.com/
> # [1]
> Link:
> https://lore.kernel.org/all/2027062704.14671-1-rdun...@infradead.org/ #
> [2]
> Cc: Thomas Zimmermann
> Cc: Lyude Paul
> Cc: Daniel Vetter
> Cc: Maarten Lankhorst
> Cc: Maxime Ripard
> Cc: dri-devel@lists.freedesktop.org
Tested-by: Naresh Kamboju
Tested-by: Linux Kernel Functional Testing
This patch fixes the repored build problem.
> ---
> drivers/gpu/drm/panel/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/panel/Kconfig b/drivers/gpu/drm/panel/Kconfig
> index 434c2861bb40..0aec5a10b064 100644
> --- a/drivers/gpu/drm/panel/Kconfig
> +++ b/drivers/gpu/drm/panel/Kconfig
> @@ -106,6 +106,7 @@ config DRM_PANEL_EDP
> depends on PM
> select VIDEOMODE_HELPERS
> select DRM_DP_AUX_BUS
> + select DRM_DP_HELPER
> help
> DRM panel driver for dumb eDP panels that need at most a regulator
> and
> a GPIO to be powered up. Optionally a backlight can be attached so
> --
> 2.34.1
>
--
Linaro LKFT
https://lkft.linaro.org
[next] arm: panel-edp.c:(.text+0xb74): undefined reference to `drm_panel_dp_aux_backlight'
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-omap2plus_defconfig - arm-clang-13-omap2plus_defconfig - arm-clang-11-lpc32xx_defconfig - arm-gcc-8-omap2plus_defconfig - arm-gcc-9-vexpress_defconfig - arm-clang-nightly-lpc32xx_defconfig - arm-gcc-9-shmobile_defconfig - arm-clang-13-lpc32xx_defconfig - arm-gcc-10-sama5_defconfig - arm-clang-11-vexpress_defconfig - arm-clang-11-sama5_defconfig - arm-gcc-9-omap2plus_defconfig - arm-clang-nightly-sama5_defconfig - arm-clang-13-vexpress_defconfig - arm-clang-nightly-vexpress_defconfig - arm-gcc-9-lpc32xx_defconfig - arm-clang-12-vexpress_defconfig - arm-gcc-10-vexpress_defconfig - arm-clang-12-shmobile_defconfig - arm-gcc-11-omap2plus_defconfig - arm-gcc-9-sama5_defconfig - arm-gcc-8-shmobile_defconfig - arm-gcc-10-lpc32xx_defconfig - arm-clang-12-omap2plus_defconfig - arm-gcc-8-vexpress_defconfig - arm-clang-12-sama5_defconfig - arm-clang-nightly-omap2plus_defconfig - arm-gcc-11-lpc32xx_defconfig - arm-gcc-11-sama5_defconfig - arm-gcc-11-shmobile_defconfig - arm-gcc-11-vexpress_defconfig - arm-gcc-8-sama5_defconfig - arm-clang-13-sama5_defconfig - arm-clang-12-lpc32xx_defconfig make --silent --keep-going --jobs=8 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc' vexpress_defconfig make --silent --keep-going --jobs=8 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc' arm-linux-gnueabihf-ld: drivers/gpu/drm/panel/panel-edp.o: in function `panel_edp_probe': panel-edp.c:(.text+0xb74): undefined reference to `drm_panel_dp_aux_backlight' make[1]: *** [/builds/linux/Makefile:1222: vmlinux] Error 1 Reported-by: Linux Kernel Functional Testing meta data: --- git describe: next-20220202 git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git target_arch: arm kconfig: vexpress_defconfig toolchain: gcc-11 Build log: - https://builds.tuxbuild.com/24XRim72vFXix6l6MdAJNENy6je/ Steps to reproduce: # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake # # See https://docs.tuxmake.org/ for complete documentation. # Original tuxmake command with fragments listed below. tuxmake --runtime podman --target-arch arm --toolchain gcc-11 --kconfig vexpress_defconfig tuxmake --runtime podman --target-arch arm --toolchain gcc-11 --kconfig https://builds.tuxbuild.com/24XRim72vFXix6l6MdAJNENy6je/config -- Linaro LKFT https://lkft.linaro.org
ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vunmap from namespace DMA_BUF, but does not import it.
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 specific files for 20211027\") target_arch: arm64 toolchain: gcc-11 build error : -- ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vunmap from namespace DMA_BUF, but does not import it. ERROR: modpost: module drm_cma_helper uses symbol dma_buf_vmap from namespace DMA_BUF, but does not import it. make[2]: *** [/builds/linux/scripts/Makefile.modpost:134: modules-only.symvers] Error 1 make[2]: *** Deleting file 'modules-only.symvers' make[2]: Target '__modpost' not remade because of errors. Reported-by: Linux Kernel Functional Testing build link: --- https://builds.tuxbuild.com/205SAU159J0g6lSlRRS11o5hHyY/build.log build config: - https://builds.tuxbuild.com/205SAU159J0g6lSlRRS11o5hHyY/config # To install tuxmake on your system globally # sudo pip3 install -U tuxmake tuxmake --runtime podman --target-arch arm64 --toolchain gcc-11 --kconfig defconfig -- Linaro LKFT https://lkft.linaro.org
Re: gpu: drm_fb_cma_helper.c:46: undefined reference to `drm_gem_fb_get_obj'
Hi Thomas,
I have tested the fix patch [1] and it works fine for me.
> Could you please try the patch at [1]? It fixes the problem for me.
Pass: 6d61a7c3bc2a ("arm: multi_v5_defconfig build fix")
arm (multi_v5_defconfig) with gcc-11
@ https://builds.tuxbuild.com/204SnLe1DFWQ4iAHpwAMiyUcpsL/
> Best regards
> Thomas
>
> [1] https://patchwork.freedesktop.org/patch/461426/
Tested-by: Naresh Kamboju
- Naresh
Re: gpu: drm_fb_cma_helper.c:46: undefined reference to `drm_gem_fb_get_obj'
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/Linaro/lkft/mirrors/next/linux-next > git_short_log: 9ae1fbdeabd3 (\"Add linux-next specific files for > 20211025\") > target_arch: arm > toolchain: gcc-11 > config: multi_v5_defconfig > > build error : > -- > arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.o: in > function `drm_fb_cma_get_gem_obj': > drivers/gpu/drm/drm_fb_cma_helper.c:46: undefined reference to > `drm_gem_fb_get_obj' > arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.c:46: > undefined reference to `drm_gem_fb_get_obj' > arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.c:46: > undefined reference to `drm_gem_fb_get_obj' > arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.o: in > function `drm_fb_cma_sync_non_coherent': > drivers/gpu/drm/drm_fb_cma_helper.c:133: undefined reference to > `drm_atomic_helper_damage_iter_init' > arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.c:135: > undefined reference to `drm_atomic_helper_damage_iter_next' > make[1]: *** [Makefile:1252: vmlinux] Error 1 > make[1]: Target '__all' not remade because of errors. > make: *** [Makefile:226: __sub-make] Error 2 > > Reported-by: Linux Kernel Functional Testing The bisection script pointed to the first bad commit, commit 4b2b5e142ff499a2bef2b8db0272bbda1088a3fe drm: Move GEM memory managers into modules > build link: > --- > https://builds.tuxbuild.com/1zzgFZBGjpQ5R0lawQFW9iJ39Hp/build.log > > build config: > - > https://builds.tuxbuild.com/1zzgFZBGjpQ5R0lawQFW9iJ39Hp/config > > # To install tuxmake on your system globally > # sudo pip3 install -U tuxmake > tuxmake --runtime podman --target-arch arm --toolchain gcc-11 > --kconfig multi_v5_defconfig > > -- > Linaro LKFT > https://lkft.linaro.org - Naresh
gpu: drm_fb_cma_helper.c:46: undefined reference to `drm_gem_fb_get_obj'
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 files for 20211025\") target_arch: arm toolchain: gcc-11 config: multi_v5_defconfig build error : -- arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.o: in function `drm_fb_cma_get_gem_obj': drivers/gpu/drm/drm_fb_cma_helper.c:46: undefined reference to `drm_gem_fb_get_obj' arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.c:46: undefined reference to `drm_gem_fb_get_obj' arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.c:46: undefined reference to `drm_gem_fb_get_obj' arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.o: in function `drm_fb_cma_sync_non_coherent': drivers/gpu/drm/drm_fb_cma_helper.c:133: undefined reference to `drm_atomic_helper_damage_iter_init' arm-linux-gnueabihf-ld: drivers/gpu/drm/drm_fb_cma_helper.c:135: undefined reference to `drm_atomic_helper_damage_iter_next' make[1]: *** [Makefile:1252: vmlinux] Error 1 make[1]: Target '__all' not remade because of errors. make: *** [Makefile:226: __sub-make] Error 2 Reported-by: Linux Kernel Functional Testing build link: --- https://builds.tuxbuild.com/1zzgFZBGjpQ5R0lawQFW9iJ39Hp/build.log build config: - https://builds.tuxbuild.com/1zzgFZBGjpQ5R0lawQFW9iJ39Hp/config # To install tuxmake on your system globally # sudo pip3 install -U tuxmake tuxmake --runtime podman --target-arch arm --toolchain gcc-11 --kconfig multi_v5_defconfig -- Linaro LKFT https://lkft.linaro.org
[next] [dragonboard 410c] Unable to handle kernel paging request at virtual address 00000000007c4240
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 007c4240 [ 18.583521] Mem abort info: [ 18.590286] ESR = 0x9604 [ 18.592920] EC = 0x25: DABT (current EL), IL = 32 bits [ 18.596103] SET = 0, FnV = 0 [ 18.601512] EA = 0, S1PTW = 0 [ 18.604384] FSC = 0x04: level 0 translation fault [ 18.607447] Data abort info: [ 18.612296] ISV = 0, ISS = 0x0004 [ 18.615451] CM = 0, WnR = 0 [ 18.618990] user pgtable: 4k pages, 48-bit VAs, pgdp=8b4c7000 [ 18.622054] [007c4240] pgd=, p4d= [ 18.628974] Internal error: Oops: 9604 [#1] SMP [ 18.635073] Modules linked in: adv7511 cec snd_soc_lpass_apq8016 snd_soc_lpass_cpu snd_soc_lpass_platform snd_soc_msm8916_digital qcom_camss qrtr snd_soc_apq8016_sbc videobuf2_dma_sg qcom_pon qcom_spmi_vadc snd_soc_qcom_common qcom_q6v5_mss qcom_vadc_common rtc_pm8xxx qcom_spmi_temp_alarm msm qcom_pil_info v4l2_fwnode qcom_q6v5 snd_soc_msm8916_analog qcom_sysmon qcom_common v4l2_async qnoc_msm8916 qcom_rng gpu_sched qcom_glink_smem venus_core videobuf2_memops icc_smd_rpm qmi_helpers drm_kms_helper v4l2_mem2mem mdt_loader display_connector i2c_qcom_cci videobuf2_v4l2 crct10dif_ce videobuf2_common socinfo drm rmtfs_mem fuse [ 18.672948] CPU: 0 PID: 178 Comm: kworker/u8:3 Not tainted 5.15.0-rc6-next-20211020 #1 [ 18.695000] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [ 18.695012] Workqueue: events_unbound deferred_probe_work_func [ 18.695033] pstate: 6005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 18.715282] pc : __stack_depot_save+0x13c/0x4e0 [ 18.722130] lr : stack_depot_save+0x14/0x20 [ 18.726641] sp : 800014a23500 [ 18.730801] x29: 800014a23500 x28: 000f8848 x27: 800013acdf68 [ 18.734294] x26: x25: 007c4240 x24: 800014a23780 [ 18.741413] x23: 0008 x22: 800014a235b8 x21: 0008 [ 18.748530] x20: c32f8848 x19: 1038cc18 x18: [ 18.755649] x17: 80002d9f8000 x16: 800010004000 x15: c426 [ 18.762767] x14: x13: 800014a23780 x12: [ 18.769885] x11: 1038cc80 x10: 8000136e9ba0 x9 : 800014a235f4 [ 18.777003] x8 : 0001 x7 : b664620b x6 : 11a58b4a [ 18.784121] x5 : 1aa43464 x4 : 9e7d8b67 x3 : 0001 [ 18.791239] x2 : 2800 x1 : 800013acd000 x0 : f2d429d8 [ 18.798358] Call trace: [ 18.805451] __stack_depot_save+0x13c/0x4e0 [ 18.807716] stack_depot_save+0x14/0x20 [ 18.811881] __drm_stack_depot_save+0x44/0x70 [drm] [ 18.815710] modeset_lock.part.0+0xe0/0x1a4 [drm] [ 18.820571] drm_modeset_lock_all_ctx+0x2d4/0x334 [drm] [ 18.825435] drm_client_firmware_config.constprop.0.isra.0+0xc0/0x5d0 [drm] [ 18.830478] drm_client_modeset_probe+0x328/0xbb0 [drm] [ 18.837413] __drm_fb_helper_initial_config_and_unlock+0x54/0x5b4 [drm_kms_helper] [ 18.842633] drm_fb_helper_initial_config+0x5c/0x70 [drm_kms_helper] [ 18.850266] msm_fbdev_init+0x98/0x100 [msm] [ 18.856767] msm_drm_bind+0x650/0x720 [msm] [ 18.861021] try_to_bring_up_master+0x230/0x320 [ 18.864926] __component_add+0xc8/0x1c4 [ 18.869435] component_add+0x20/0x30 [ 18.873253] mdp5_dev_probe+0xe0/0x11c [msm] [ 18.877077] platform_probe+0x74/0xf0 [ 18.881328] really_probe+0xc4/0x470 [ 18.884883] __driver_probe_device+0x11c/0x190 [ 18.888534] driver_probe_device+0x48/0x110 [ 18.892786] __device_attach_driver+0xa4/0x140 [ 18.896869] bus_for_each_drv+0x84/0xe0 [ 18.901380] __device_attach+0xe4/0x1c0 [ 18.905112] device_initial_probe+0x20/0x30 [ 18.908932] bus_probe_device+0xac/0xb4 [ 18.913098] deferred_probe_work_func+0xc8/0x120 [ 18.916920] process_one_work+0x280/0x6a0 [ 18.921780] worker_thread+0x80/0x454 [ 18.925683] kthread+0x178/0x184 [ 18.929326] ret_from_fork+0x10/0x20 [ 18.932634] Code: d37d4e99 92404e9c f940077a 8b190359 (c8dfff33) [ 18.936203] ---[ end trace 3e289b724840642d ]--- Full log, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20211020/testrun/6177937/suite/linux-log-parser/test/check-kernel-oops-3786583/log https://lkft.validation.linaro.org/scheduler/job/3786583#L2549 Build config: https://builds.tuxbuild.com/1zlLlQrUyHVr1MQ1gcler3dKaE6/config Reported-by: Linux Kernel Functional Testing steps to reproduce: 1) https://builds.tuxbuild.com/1zlLlQrUyHVr1MQ1gcler3dKaE6/tuxmake_reproducer.sh 2) Boot db410c device -- Linaro LKFT https://lkft.linaro.org
rcar_du_kms.c:781:24: error: passing argument 1 of '__drmm_add_action' from incompatible pointer type
On stable rc 5.11 the x86_64 build failed due to below errors/warnings. drivers/gpu/drm/rcar-du/rcar_du_kms.c: In function 'rcar_du_modeset_cleanup': drivers/gpu/drm/rcar-du/rcar_du_kms.c:754:32: error: implicit declaration of function 'to_rcar_du_device'; did you mean 'to_rtc_device'? [-Werror=implicit-function-declaration] struct rcar_du_device *rcdu = to_rcar_du_device(dev); ^ to_rtc_device drivers/gpu/drm/rcar-du/rcar_du_kms.c:754:32: warning: initialization makes pointer from integer without a cast [-Wint-conversion] In file included from drivers/gpu/drm/rcar-du/rcar_du_kms.c:17:0: drivers/gpu/drm/rcar-du/rcar_du_kms.c: In function 'rcar_du_modeset_init': drivers/gpu/drm/rcar-du/rcar_du_kms.c:781:24: error: passing argument 1 of '__drmm_add_action' from incompatible pointer type [-Werror=incompatible-pointer-types] ret = drmm_add_action(>ddev, rcar_du_modeset_cleanup, NULL); ^ include/drm/drm_managed.h:25:20: note: in definition of macro 'drmm_add_action' __drmm_add_action(dev, action, data, #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 treated as errors Reported-by: Naresh Kamboju Build link, https://ci.linaro.org/job/openembedded-lkft-linux-stable-rc-5.11/DISTRO=lkft,MACHINE=ls2088ardb,label=docker-buster-lkft/8/consoleText -- Linaro LKFT https://lkft.linaro.org ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: rcar_du_kms.c:781:24: error: passing argument 1 of '__drmm_add_action' from incompatible pointer type
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: In function 'rcar_du_modeset_cleanup': > drivers/gpu/drm/rcar-du/rcar_du_kms.c:754:32: error: implicit > declaration of function 'to_rcar_du_device'; did you mean > 'to_rtc_device'? [-Werror=implicit-function-declaration] > struct rcar_du_device *rcdu = to_rcar_du_device(dev); > ^ > to_rtc_device > drivers/gpu/drm/rcar-du/rcar_du_kms.c:754:32: warning: initialization > makes pointer from integer without a cast [-Wint-conversion] > In file included from drivers/gpu/drm/rcar-du/rcar_du_kms.c:17:0: > drivers/gpu/drm/rcar-du/rcar_du_kms.c: In function 'rcar_du_modeset_init': > drivers/gpu/drm/rcar-du/rcar_du_kms.c:781:24: error: passing argument > 1 of '__drmm_add_action' from incompatible pointer type > [-Werror=incompatible-pointer-types] > ret = drmm_add_action(>ddev, rcar_du_modeset_cleanup, NULL); > ^ > include/drm/drm_managed.h:25:20: note: in definition of macro > 'drmm_add_action' > __drmm_add_action(dev, action, data, #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 treated as errors > > Reported-by: Naresh Kamboju > > Build link, > https://ci.linaro.org/job/openembedded-lkft-linux-stable-rc-5.11/DISTRO=lkft,MACHINE=ls2088ardb,label=docker-buster-lkft/8/consoleText > > -- > Linaro LKFT > https://lkft.linaro.org ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 5.4 000/132] 5.4.66-rc1 review
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.
>
> Responses should be made by Thu, 17 Sep 2020 14:06:12 +.
> 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.4.66-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.4.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
arm and arm64 build breaks on stable rc 5.4.
make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf- HOSTCC=gcc CC="sccache
arm-linux-gnueabihf-gcc" O=build zImage
#
../kernel/kprobes.c: In function ‘kill_kprobe’:
../kernel/kprobes.c:1081:33: warning: statement with no effect [-Wunused-value]
1081 | #define disarm_kprobe_ftrace(p) (-ENODEV)
| ^
../kernel/kprobes.c:2113:3: note: in expansion of macro ‘disarm_kprobe_ftrace’
2113 | disarm_kprobe_ftrace(p);
| ^~~~
#
# make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf- HOSTCC=gcc CC="sccache
arm-linux-gnueabihf-gcc" O=build modules
#
../drivers/gpu/drm/msm/adreno/a5xx_preempt.c: In function ‘preempt_init_ring’:
../drivers/gpu/drm/msm/adreno/a5xx_preempt.c:235:21: error:
‘MSM_BO_MAP_PRIV’ undeclared (first use in this function)
235 | MSM_BO_UNCACHED | MSM_BO_MAP_PRIV, gpu->aspace, , );
| ^~~
../drivers/gpu/drm/msm/adreno/a5xx_preempt.c:235:21: note: each
undeclared identifier is reported only once for each function it
appears in
make[5]: *** [../scripts/Makefile.build:266:
drivers/gpu/drm/msm/adreno/a5xx_preempt.o] Error 1
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c: In function ‘a6xx_hw_init’:
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:414:6: error: implicit
declaration of function ‘adreno_is_a640’; did you mean
‘adreno_is_a540’? [-Werror=implicit-function-declaration]
414 | if (adreno_is_a640(adreno_gpu) || adreno_is_a650(adreno_gpu)) {
| ^~
| adreno_is_a540
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:414:36: error: implicit
declaration of function ‘adreno_is_a650’; did you mean
‘adreno_is_a540’? [-Werror=implicit-function-declaration]
414 | if (adreno_is_a640(adreno_gpu) || adreno_is_a650(adreno_gpu)) {
|^~
|adreno_is_a540
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:415:18: error:
‘REG_A6XX_GBIF_QSB_SIDE0’ undeclared (first use in this function)
415 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE0, 0x00071620);
| ^~~
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:415:18: note: each undeclared
identifier is reported only once for each function it appears in
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:416:18: error:
‘REG_A6XX_GBIF_QSB_SIDE1’ undeclared (first use in this function)
416 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE1, 0x00071620);
| ^~~
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:417:18: error:
‘REG_A6XX_GBIF_QSB_SIDE2’ undeclared (first use in this function)
417 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE2, 0x00071620);
| ^~~
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:418:18: error:
‘REG_A6XX_GBIF_QSB_SIDE3’ undeclared (first use in this function)
418 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE3, 0x00071620);
| ^~~
cc1: some warnings being treated as errors
make[5]: *** [../scripts/Makefile.build:265:
drivers/gpu/drm/msm/adreno/a6xx_gpu.o] Error 1
In file included from ../drivers/gpu/drm/msm/msm_gpu.c:7:
../drivers/gpu/drm/msm/msm_gpu.c: In function ‘msm_gpu_init’:
../drivers/gpu/drm/msm/msm_gpu.h:330:22: error: ‘MSM_BO_MAP_PRIV’
undeclared (first use in this function)
330 | (((gpu)->hw_apriv ? MSM_BO_MAP_PRIV : 0) | (flags))
| ^~~
../drivers/gpu/drm/msm/msm_gpu.c:935:3: note: in expansion of macro
‘check_apriv’
935 | check_apriv(gpu, MSM_BO_UNCACHED), gpu->aspace, >memptrs_bo,
| ^~~
../drivers/gpu/drm/msm/msm_gpu.h:330:22: note: each undeclared
identifier is reported only once for each function it appears in
330 | (((gpu)->hw_apriv ? MSM_BO_MAP_PRIV : 0) | (flags))
| ^~~
../drivers/gpu/drm/msm/msm_gpu.c:935:3: note: in expansion of macro
‘check_apriv’
935 | check_apriv(gpu, MSM_BO_UNCACHED), gpu->aspace, >memptrs_bo,
| ^~~
make[5]: *** [../scripts/Makefile.build:266:
drivers/gpu/drm/msm/msm_gpu.o] Error 1
In file
Re: WARNING: drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h:178 mdp5_bind
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.459724] clk: failed to reparent pclk0_clk_src to dsi0pll: -22 > [8.466474] msm 1a0.mdss: Using legacy clk name binding. Use > \"iface\" instead of \"iface_clk\" > [8.476753] msm 1a0.mdss: Using legacy clk name binding. Use > \"bus\" instead of \"bus_clk\" > [8.480055] msm 1a0.mdss: Using legacy clk name binding. Use > \"vsync\" instead of \"vsync_clk\" > [8.489023] msm 1a0.mdss: 1a0.mdss supply vdd not found, > using dummy regulator > [8.498450] msm_mdp 1a01000.mdp: Using legacy clk name binding. > Use \"bus\" instead of \"bus_clk\" > [8.505394] msm_mdp 1a01000.mdp: Using legacy clk name binding. > Use \"iface\" instead of \"iface_clk\" > [8.524724] msm_mdp 1a01000.mdp: Using legacy clk name binding. > Use \"core\" instead of \"core_clk\" > [8.524877] msm_mdp 1a01000.mdp: Using legacy clk name binding. > Use \"vsync\" instead of \"vsync_clk\"[8.532846] [ cut > here ] > [8.541651] WARNING: CPU: 1 PID: 32 at > /usr/src/kernel/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h:178 > mdp5_bind+0x418/0x4e0 [msm] > [8.546303] Modules linked in: crc32_ce adv7511 rfkill msm > mdt_loader drm_kms_helper drm msm_rng rng_core fuse > [8.557504] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted 4.14.176-rc1 #1 > [8.567478] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) > [8.574344] Workqueue: events deferred_probe_work_func > [8.581018] task: 80003d764680 task.stack: 0a4c > [8.586178] PC is at mdp5_bind+0x418/0x4e0 [msm] > [8.591989] LR is at mdp5_bind+0x1b4/0x4e0 [msm] > [8.596644] pc : [] lr : [] > pstate: 6145 > [8.601246] sp : 0a4c39d0 > [8.608617] x29: 0a4c39d0 x28: > [8.611832] x27: 800037db4a00 x26: 00eec9e8 > [8.617214] x25: 800037e28000 x24: 800037dc3810 > [8.622509] x23: 800037ca7000 x22: 0a22e4b0 > [8.627805] x21: 800037dc3800 x20: > [8.633100] x19: 80003a8c2880 x18: 0010 > [8.638395] x17: b6f9ba28 x16: 082fd6e0 > [8.643691] x15: x14: > [8.648986] x13: x12: e3d3f2dc > [8.654280] x11: 80003d764eb0 x10: 0a20 > [8.659576] x9 : fffe x8 : > [8.664871] x7 : 087c908c x6 : > [8.670167] x5 : 0040 x4 : 0004 > [8.675461] x3 : feb0 x2 : 09d5f1a0 > [8.680755] x1 : 80003d764680 x0 : > [8.686052] Call trace: > [8.691346] Exception stack(0x0a4c3890 to 0x0a4c39d0) > [8.693521] 3880: > 80003d764680 > [8.700120] 38a0: 09d5f1a0 feb0 > 0004 0040 > [8.707934] 38c0: 087c908c > fffe > [8.715746] 38e0: 0a20 80003d764eb0 > e3d3f2dc > [8.723558] 3900: > 082fd6e0 b6f9ba28 > [8.731372] 3920: 0010 80003a8c2880 > 800037dc3800 > [8.739183] 3940: 0a22e4b0 800037ca7000 > 800037dc3810 800037e28000 > [8.746997] 3960: 00eec9e8 800037db4a00 > 0a4c39d0 > [8.754809] 3980: 00ebd494 0a4c39d0 > 00ebd6f8 6145 > [8.762622] 39a0: 0a4c39d0 00ebd494 > > [8.770431] 39c0: 0a4c39d0 00ebd6f8 > [8.778452] [] mdp5_bind+0x418/0x4e0 [msm] > [8.782937] [] component_bind_all+0x104/0x298 > [8.789040] [] msm_drm_bind+0x140/0x5f0 [msm] > [8.794481] [] try_to_bring_up_master+0x180/0x1e0 > [8.800380] [] component_add+0xa8/0x170 > [8.806845] [] dsi_dev_probe+0x24/0x38 [msm] > [8.812199] [] platform_drv_probe+0x60/0xc0 > [8.817913] [] driver_probe_device+0x218/0x2e0 > [8.823730] [] __device_attach_driver+0xa4/0xf0 > [8.829810] [] bus_for_each_drv+0x5c/0xa8 > [8.835797] [] __device_attach+0xd0/0x148 > [8.841177] [] device_initial_probe+0x24/0x30 > [8.846734] [] bus_probe_device+0xa0/0xa8 >
stable-rc 4.14: Internal error: Oops: 96000004 - pc : __pi_strcmp+0x18/0x154
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.772434] EA = 0, S1PTW = 0 [7.774344] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops [msm]): -22 [7.779241] Data abort info: [7.789056] msm 1a0.mdss: master bind failed: -22 [7.792091] msm_dsi: probe of 1a98000.dsi failed with error -22 [7.794132] ISV = 0, ISS = 0x0004 [7.802783] CM = 0, WnR = 0 [7.809436] user pgtable: 4k pages, 48-bit VAs, pgd = 80003b1d7000 [7.809660] [] *pgd= [7.825466] Internal error: Oops: 9604 [#1] PREEMPT SMP [7.825498] Modules linked in: rfkill crc32_ce adv7511 msm(+) msm_rng mdt_loader drm_kms_helper rng_core drm fuse [7.829847] Process systemd-udevd (pid: 2635, stack limit = 0x0f3c) [7.840261] CPU: 1 PID: 2635 Comm: systemd-udevd Not tainted 4.14.177-rc1 #1 [7.847391] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [7.847397] task: 80003b279780 task.stack: 0f3c [7.847410] pc : __pi_strcmp+0x18/0x154 [7.866993] lr : platform_match+0xc8/0xe8 [7.870809] sp : 0f3c3b10 pstate : 4145 [7.874975] x29: 0f3c3b10 x28: 80003a56a000 [7.879663] x27: 081a0578 x26: 00ef98d0 [7.885219] x25: 0f3c3e50 x24: 0f515000 [7.890514] x23: 095c8000 x22: [7.895809] x21: x20: 00ef8648 [7.901104] x19: 80003d1998d0 x18: 9a0bf0b0 [7.906398] x17: 9a06b6d0 x16: 08160330 [7.911694] x15: 2810bf43 x14: 0043 [7.916990] x13: 3a6c6c7030697364 x12: bcc77e12 [7.922283] x11: 80003b279fb8 x10: 0101010101010101 [7.927581] x9 : 8efefeff06fefeff x8 : [7.932874] x7 : x6 : [7.938172] x5 : 0100 x4 : [7.943466] x3 : x2 : 087be348 [7.948761] x1 : 00eed688 x0 : [7.954056] Call trace: [7.959354] __pi_strcmp+0x18/0x154 [7.970033] bus_for_each_dev+0x5c/0xa8 [7.970056] driver_attach+0x30/0x [7.972665] bus_add_driver+0x1d0/0x240 [7.976484] driver_register+0x6c/0x118 [7.980044] __platform_driver_register+0x54/0x60 [7.984103] msm_drm_register+0x48/0x80 [msm] [7.988728] do_one_initcall+0x44/0x138 [7.993065] do_init_module+0x64/0x1d0 [7.996710] load_module+0x1d48/0x2518 [8.000530] SyS_finit_module+0xb0/0xc8 [8.004263] __sys_trace_return+0x0/0x4 [8.007998] Code: f24008ff 540002e1 f2400807 54000141 (f8408402) [8.011820] ---[ end trace 7d6fc616cc3d45e7 ]--- full test log, https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.176-200-gcebd79de8787/testrun/1389032/log https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.176-200-gcebd79de8787/testrun/1389032/ https://lkft.validation.linaro.org/scheduler/job/1389032#L3519 Kernel config: http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/dragonboard-410c/lkft/linux-stable-rc-4.14/817/config -- Linaro LKFT https://lkft.linaro.org ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v2] drm/etnaviv: rework perfmon query infrastructure
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 infrastructure to query perf
> > counter")
> > Cc: sta...@vger.kernel.org
> > Signed-off-by: Christian Gmeiner
>
> Thanks, applied to etnaviv/next.
>
> Regards,
> Lucas
>
> >
> > ---
> > Changes V1 -> V2:
> > - Handle domain == NULL case better to get rid of BUG_ON(..) usage.
> > ---
> > drivers/gpu/drm/etnaviv/etnaviv_perfmon.c | 59 ---
> > 1 file changed, 52 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/etnaviv/etnaviv_perfmon.c
> > b/drivers/gpu/drm/etnaviv/etnaviv_perfmon.c
> > index 8adbf2861bff..e6795bafcbb9 100644
> > --- a/drivers/gpu/drm/etnaviv/etnaviv_perfmon.c
> > +++ b/drivers/gpu/drm/etnaviv/etnaviv_perfmon.c
> > @@ -32,6 +32,7 @@ struct etnaviv_pm_domain {
> > };
> >
> > struct etnaviv_pm_domain_meta {
> > + unsigned int feature;
> > const struct etnaviv_pm_domain *domains;
> > u32 nr_domains;
> > };
> > @@ -410,36 +411,78 @@ static const struct etnaviv_pm_domain doms_vg[] = {
> >
> > static const struct etnaviv_pm_domain_meta doms_meta[] = {
> > {
> > + .feature = chipFeatures_PIPE_3D,
make modules failed for arm architecture on stable rc 4.19 branch.
drivers/gpu/drm/etnaviv/etnaviv_perfmon.c:392:14: error:
'chipFeatures_PIPE_3D' undeclared here (not in a function)
.feature = chipFeatures_PIPE_3D,
^~~~
drivers/gpu/drm/etnaviv/etnaviv_perfmon.c:397:14: error:
'chipFeatures_PIPE_2D' undeclared here (not in a function); did you
mean 'chipFeatures_PIPE_3D'?
.feature = chipFeatures_PIPE_2D,
^~~~
chipFeatures_PIPE_3D
drivers/gpu/drm/etnaviv/etnaviv_perfmon.c:402:14: error:
'chipFeatures_PIPE_VG' undeclared here (not in a function); did you
mean 'chipFeatures_PIPE_2D'?
.feature = chipFeatures_PIPE_VG,
^~~~
chipFeatures_PIPE_2D
ref:
https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-stable-rc-4.19/DISTRO=lkft,MACHINE=am57xx-evm,label=docker-lkft/511/consoleText
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h:178 mdp5_bind
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: Using legacy clk name binding. Use \"iface\" instead of \"iface_clk\" [8.476753] msm 1a0.mdss: Using legacy clk name binding. Use \"bus\" instead of \"bus_clk\" [8.480055] msm 1a0.mdss: Using legacy clk name binding. Use \"vsync\" instead of \"vsync_clk\" [8.489023] msm 1a0.mdss: 1a0.mdss supply vdd not found, using dummy regulator [8.498450] msm_mdp 1a01000.mdp: Using legacy clk name binding. Use \"bus\" instead of \"bus_clk\" [8.505394] msm_mdp 1a01000.mdp: Using legacy clk name binding. Use \"iface\" instead of \"iface_clk\" [8.524724] msm_mdp 1a01000.mdp: Using legacy clk name binding. Use \"core\" instead of \"core_clk\" [8.524877] msm_mdp 1a01000.mdp: Using legacy clk name binding. Use \"vsync\" instead of \"vsync_clk\"[8.532846] [ cut here ] [8.541651] WARNING: CPU: 1 PID: 32 at /usr/src/kernel/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.h:178 mdp5_bind+0x418/0x4e0 [msm] [8.546303] Modules linked in: crc32_ce adv7511 rfkill msm mdt_loader drm_kms_helper drm msm_rng rng_core fuse [8.557504] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted 4.14.176-rc1 #1 [8.567478] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [8.574344] Workqueue: events deferred_probe_work_func [8.581018] task: 80003d764680 task.stack: 0a4c [8.586178] PC is at mdp5_bind+0x418/0x4e0 [msm] [8.591989] LR is at mdp5_bind+0x1b4/0x4e0 [msm] [8.596644] pc : [] lr : [] pstate: 6145 [8.601246] sp : 0a4c39d0 [8.608617] x29: 0a4c39d0 x28: [8.611832] x27: 800037db4a00 x26: 00eec9e8 [8.617214] x25: 800037e28000 x24: 800037dc3810 [8.622509] x23: 800037ca7000 x22: 0a22e4b0 [8.627805] x21: 800037dc3800 x20: [8.633100] x19: 80003a8c2880 x18: 0010 [8.638395] x17: b6f9ba28 x16: 082fd6e0 [8.643691] x15: x14: [8.648986] x13: x12: e3d3f2dc [8.654280] x11: 80003d764eb0 x10: 0a20 [8.659576] x9 : fffe x8 : [8.664871] x7 : 087c908c x6 : [8.670167] x5 : 0040 x4 : 0004 [8.675461] x3 : feb0 x2 : 09d5f1a0 [8.680755] x1 : 80003d764680 x0 : [8.686052] Call trace: [8.691346] Exception stack(0x0a4c3890 to 0x0a4c39d0) [8.693521] 3880: 80003d764680 [8.700120] 38a0: 09d5f1a0 feb0 0004 0040 [8.707934] 38c0: 087c908c fffe [8.715746] 38e0: 0a20 80003d764eb0 e3d3f2dc [8.723558] 3900: 082fd6e0 b6f9ba28 [8.731372] 3920: 0010 80003a8c2880 800037dc3800 [8.739183] 3940: 0a22e4b0 800037ca7000 800037dc3810 800037e28000 [8.746997] 3960: 00eec9e8 800037db4a00 0a4c39d0 [8.754809] 3980: 00ebd494 0a4c39d0 00ebd6f8 6145 [8.762622] 39a0: 0a4c39d0 00ebd494 [8.770431] 39c0: 0a4c39d0 00ebd6f8 [8.778452] [] mdp5_bind+0x418/0x4e0 [msm] [8.782937] [] component_bind_all+0x104/0x298 [8.789040] [] msm_drm_bind+0x140/0x5f0 [msm] [8.794481] [] try_to_bring_up_master+0x180/0x1e0 [8.800380] [] component_add+0xa8/0x170 [8.806845] [] dsi_dev_probe+0x24/0x38 [msm] [8.812199] [] platform_drv_probe+0x60/0xc0 [8.817913] [] driver_probe_device+0x218/0x2e0 [8.823730] [] __device_attach_driver+0xa4/0xf0 [8.829810] [] bus_for_each_drv+0x5c/0xa8 [8.835797] [] __device_attach+0xd0/0x148 [8.841177] [] device_initial_probe+0x24/0x30 [8.846734] [] bus_probe_device+0xa0/0xa8 [8.852638] [] deferred_probe_work_func+0xac/0x158 [8.858195] [] process_one_work+0x278/0x790 [8.864800] [] worker_thread+0x50/0x480 [8.870441] [] kthread+0x138/0x140 [8.875823] [] ret_from_fork+0x10/0x1c [8.880846] ---[ end trace 73f4fbf7f1caf3f2 ]--- [8.886661] msm 1a0.mdss: bound 1a01000.mdp (ops mdp5_ops [msm]) [8.891128] msm_dsi 1a98000.dsi: 1a98000.dsi supply gdsc not found, using dummy regulator [8.897939] [ cut here ] [8.905384] WARNING: CPU: 1 PID: 2210 at /usr/src/kernel/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c:253 mdp5_disable+0xa0/0xb8 [msm] [
stable-rc 5.5.5-rc1: [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow!
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 is 0 hugemmap05.c:236: INFO: original nr_overcommit_hugepages is 0 hugemmap05.c:104: INFO: check /proc/meminfo before allocation. hugemmap05.c:285: INFO: HugePages_Total is 192. hugemmap05.c:285: INFO: HugePages_Free is 192. hugemmap05.c:285: INFO: HugePages_Surp is 64. hugemmap05.c:285: INFO: HugePages_[ 51.411646] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! Rsvd is 192. [ 51.411735] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.419705] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.427680] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.434455] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.441179] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.447912] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.454639] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.461395] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.468175] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.475014] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.481868] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.488621] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.495367] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.502113] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.508845] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.515582] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.522316] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.529054] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.535836] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.542621] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.549399] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.556144] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.562897] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.569634] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.576378] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.583142] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.589889] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.596610] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! hugemmap05.c:260:[ 51.603356] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! INFO: First hex is 7070707 [ 51.610101] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 51.621956] [drm:ade_ldi_set_mode [kirin_drm]] *ERROR* failed to set pixel clk 0Hz (-22) hugemmap05.c:139: INFO: check /proc/meminfo. hugemmap05.c:285: INFO: HugePages_Total is 192. hugemmap05.c:285: INFO: HugePages_Free is 0. hugemmap05.c:285: INFO: HugePages_Surp is 64. hugemmap05.c:285: INFO: HugePages_Rsvd is 0. hugemmap05.c:163: PASS: hugepages overcommit test pass hugemmap05.c:180: INFO: restore nr_hugepages to 0. hugemmap05.c:189: INFO: restore nr_overcommit_hugepages to 0. Summary: passed 1 failed 0 skipped 0 warnings 0 tst_test.c:1217: INFO: Timeout per run is 0h 15m 00s mem.c:817: INFO: set nr_hugepages to 255 [ 54.139687] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 54.143384] [drm:ade_ldi_set_mode [kirin_drm]] *ERROR* failed to set pixel clk 0Hz (-22) [ 54.278589] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 54.280642] [drm:ade_ldi_set_mode [kirin_drm]] *ERROR* failed to set pixel clk 0Hz (-22) hugemmap06.c:139: PASS: No regression found. [ 54.520165] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 54.522769] [drm:ade_ldi_set_mode [kirin_drm]] *ERROR* failed to set pixel clk 0Hz (-22) [ 54.664774] [drm:ade_irq_handler [kirin_drm]] *ERROR* LDI underflow! [ 54.668013] [drm:ade_ldi_set_mode [kirin_drm]] *ERROR* failed to set pixel clk 0Hz (-22) Ref: https://lkft.validation.linaro.org/scheduler/job/1227316#L4288 metadata: git branch: linux-5.5.y git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git commit: 7d6c8f2632c92635fcef4175921a7742f23947e4 git describe: v5.5.4-46-g7d6c8f2632c9 make_kernelversion: 5.5.5-rc1 kernel-config: http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/hikey/lkft/linux-stable-rc-5.5/24/config build-location: http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/hikey/lkft/linux-stable-rc-5.5/24 -- Linaro LKFT https://lkft.linaro.org ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] [v3] drm/sun4i: fix build failure with CONFIG_DRM_SUN8I_MIXER=m
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" [drivers/gpu/drm/sun4i/sun8i-drm-hdmi.ko]
>> undefined!
>> ERROR: "sun8i_tcon_top_of_table" [drivers/gpu/drm/sun4i/sun4i-drm.ko]
>> undefined!
>>
>> This solves the problem by adding a silent symbol for the tcon_top module,
>> building it as a separate module in exactly the cases that we need it,
>> but in a way that it is reachable by the other modules.
>>
>> Fixes: 57e23de02f48 ("drm/sun4i: DW HDMI: Expand algorithm for possible
>> crtcs")
>> Fixes: ef0cf6441fbb ("drm/sun4i: Add support for traversing graph with TCON
>> TOP")
>> Signed-off-by: Arnd Bergmann
> I am seeing the following on today's -next (20180907) as well the last
> few -next versions for that matter ...
>
> ERROR: "sun8i_tcon_top_de_config" [drivers/gpu/drm/sun4i/sun4i-tcon.ko]
> undefined!
> ERROR: "sun8i_tcon_top_set_hdmi_src" [drivers/gpu/drm/sun4i/sun4i-tcon.ko]
> undefined!
> ERROR: "sun8i_tcon_top_of_table" [drivers/gpu/drm/sun4i/sun4i-tcon.ko]
> undefined!
>
> Seems like this issue has cropped up again as Arnd's fix is present. I
> am seeing this on ARM64 builds.
I do notice these failures on ARM64 builds on linux next 20180906 and 20180907.
11:40:55 | ERROR: "sun8i_tcon_top_de_config"
[drivers/gpu/drm/sun4i/sun4i-tcon.ko] undefined!
11:40:55 | ERROR: "sun8i_tcon_top_set_hdmi_src"
[drivers/gpu/drm/sun4i/sun4i-tcon.ko] undefined!
11:40:55 | ERROR: "sun8i_tcon_top_of_table"
[drivers/gpu/drm/sun4i/sun4i-tcon.ko] undefined!
Build full log can be found on this link.
https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=rpb,MACHINE=dragonboard-410c,label=docker-stretch-amd64/346/console
- Naresh
>
> Cheers
> Jon
>
> --
> nvpublic
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] [RFT] drm: adv7511/33: fix adv7511_cec_init() failure handling
On 15 November 2017 at 18:28, Hans Verkuil <hverk...@xs4all.nl> wrote:
> On 15/11/17 13:37, Arnd Bergmann wrote:
>> An otherwise correct cleanup patch from Dan Carpenter turned a broken
>> failure handling from a feature patch by Hans Verkuil into a kernel
>> Oops, so bisection points to commit 7af35b0addbc ("drm/kirin: Checking
>> for IS_ERR() instead of NULL") rather than 3b1b975003e4 ("drm:
>> adv7511/33: add HDMI CEC support").
>>
>> I've managed to piece together several partial problems, though
>> I'm still struggling with the bigger picture:
>>
>> adv7511_probe() registers a drm_bridge structure that was allocated
>> with devm_kzalloc(). It calls adv7511_cec_init(), which fails for an
>> unknown reason, which in turn triggers the registered structure to be
>> removed.
>>
>> Elsewhere, kirin_drm_platform_probe() gets called, which calls
>> of_graph_get_remote_node(), and that returns NULL. Before Dan's
>> patch we would go on with a NULL pointer here and register that,
>> now kirin_drm_platform_probe() fails with -ENODEV.
>>
>> In a third driver, dsi_parse_dt() calls drm_of_find_panel_or_bridge(),
>> which after not finding a panel goes on to call of_drm_find_bridge(),
>> and that crashes due to the earlier list corruption.
>>
>> This addresses the first issue by making sure that adv7511_probe()
>> 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 Kamboju <naresh.kamb...@linaro.org>
>> Cc: Xinliang Liu <xinliang@linaro.org>
>> Cc: Dan Carpenter <dan.carpen...@oracle.com>
>> Cc: Sean Paul <seanp...@chromium.org>
>> Cc: Hans Verkuil <hans.verk...@cisco.com>
>> Cc: Archit Taneja <arch...@codeaurora.org>
>> Link: https://bugs.linaro.org/show_bug.cgi?id=3345
>> Link: https://lkft.validation.linaro.org/scheduler/job/48017#L3551
>> Fixes: 7af35b0addbc ("drm/kirin: Checking for IS_ERR() instead of NULL")
>> Fixes: 3b1b975003e4 ("drm: adv7511/33: add HDMI CEC support")
>> Signed-off-by: Arnd Bergmann <a...@arndb.de>
>> ---
>> Untested so far, this is what I came up with after reading the
>> WARN_ON log from a modified kernel.
>>
>> Naresh, can you give this one a go?
Tested with this patch.
I did not notice kernel crash/WARNING in dmesg log on HiKey (arm64) board.
Ref test log:
Link: https://pastebin.com/t8iLEFwF
Tested-by: Naresh Kamboju <naresh.kamb...@linaro.org>
>>
>> Hans and others, can you review in the meantime?
>>
>> Signed-off-by: Arnd Bergmann <a...@arndb.de>
>> ---
>> drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 7 ++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
>> b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
>> index 0e14f1572d05..93d1ecafe8fa 100644
>> --- a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
>> +++ b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
>> @@ -1204,7 +1204,7 @@ static int adv7511_probe(struct i2c_client *i2c, const
>> struct i2c_device_id *id)
>> #ifdef CONFIG_DRM_I2C_ADV7511_CEC
>> ret = adv7511_cec_init(dev, adv7511, offset);
>> if (ret)
>> - goto err_unregister_cec;
>> + goto err_unregister_bridge;
>
> Rather than adding the err_unregister_bridge label, I think it is better to
> move
> this code up to just before the call to drm_bridge_add().
>
> I think I just didn't realize that doing it after would require additional
> cleanup.
> But it should be perfectly fine to move it up so we can avoid doing that.
>
> I can't test it until Monday as I don't have access to the hardware at the
> moment.
>
> Regards,
>
> Hans
>
>> #else
>> regmap_write(adv7511->regmap, ADV7511_REG_CEC_CTRL + offset,
>>ADV7511_CEC_CTRL_POWER_DOWN);
>> @@ -1212,6 +1212,11 @@ static int adv7511_probe(struct i2c_client *i2c,
>> const struct i2c_device_id *id)
>>
>> return 0;
>>
>> +#ifdef CONFIG_DRM_I2C_ADV7511_CEC
>> +err_unregister_bridge:
>> + adv7511_audio_exit(adv7511);
>> + drm_bridge_remove(>bridge);
>> +#endif
>> err_unregister_cec:
>> i2c_unregister_device(adv7511->i2c_cec);
>> if (adv7511->cec_clk)
>>
>
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
