From: Peter Schneider <pschneider1968@googlemail.com>
To: Muhammad Usama Anjum <Usama.Anjum@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.10 000/482] 6.10.14-rc1 review
Date: Thu, 10 Oct 2024 19:18:55 +0200 [thread overview]
Message-ID: <86472ad5-6fd3-4273-be9b-e4815b54797e@googlemail.com> (raw)
In-Reply-To: <05ef1fc5-6947-45f1-bf9b-879681647107@collabora.com>
Am 10.10.2024 um 10:58 schrieb Muhammad Usama Anjum:
> Please find the KernelCI report below :-
>
>
> OVERVIEW
>
> Builds: 24 passed, 1 failed
>
> Boot tests: 510 passed, 0 failed
>
> CI systems: maestro
>
> REVISION
>
> Commit
> name:
> hash: d44129966591836e3ff248d0af2358f1b8f7bc28
> Checked out from
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> linux-6.10.y
>
>
> BUILDS
> - i386 (defconfig+kcidebug+x86-board)
> Build error:
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_state.c:219:1: error:
> the frame size of 1192 bytes is larger than 1024 bytes
> [-Werror=frame-larger-than=]
> config:
> https://kciapistagingstorage1.file.core.windows.net/early-access/kbuild-gcc-12-x86-kcidebug-6705246a7ef7358befb78db3/.config?sv=2022-11-02&ss=f&srt=sco&sp=r&se=2024-10-17T19:19:12Z&st=2023-10-17T11:19:12Z&spr=https&sig=sLmFlvZHXRrZsSGubsDUIvTiv%2BtzgDq6vALfkrtWnv8%3D
>
> BOOT TESTS
>
> No new boot failures found
>
> Tested-by: kernelci.org bot <bot@kernelci.org>
>
> Thanks,
> KernelCI team
>
I do all my kernel build tests with CONFIG_WERROR=Y, and I found that due to THIS driver,
I had to increase CONFIG_FRAME_WARN to 2048 from its default 1024 (which comes from my PVE
oldconfig). This avoids this warning/error. However I don't know whether a driver, or any
function, using a larger stack frame than 1024 bytes will generally be a problem.
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
next prev parent reply other threads:[~2024-10-10 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 12:01 Greg Kroah-Hartman
2024-10-08 16:05 ` Peter Schneider
2024-10-08 17:25 ` Mark Brown
2024-10-08 18:16 ` Florian Fainelli
2024-10-08 22:03 ` Shuah Khan
2024-10-09 6:22 ` Naresh Kamboju
2024-10-09 11:35 ` Anders Roxell
2024-10-09 11:53 ` [LTP] " Cyril Hrubis
2024-10-09 12:03 ` Jan Stancek
2024-10-09 22:03 ` Sasha Levin
2024-10-09 14:58 ` Jon Hunter
2024-10-09 21:59 ` Sasha Levin
2024-10-10 10:40 ` Jon Hunter
2024-10-10 12:13 ` Jon Hunter
2024-10-10 0:04 ` Ron Economos
2024-10-10 8:58 ` Muhammad Usama Anjum
2024-10-10 17:18 ` Peter Schneider [this message]
2024-10-10 11:16 ` Miguel Ojeda
2024-10-11 16:22 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86472ad5-6fd3-4273-be9b-e4815b54797e@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=Usama.Anjum@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®