From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: Fwd: [pm:bleeding-edge] BUILD REGRESSION 208501f6808a1dc0205904ed84cac99da01bbf70
Date: Tue, 17 Dec 2019 16:27:09 -0800 [thread overview]
Message-ID: <20191218002709.GA8314@dtor-ws> (raw)
In-Reply-To: <1860961.FledB3ecnK@kreacher>
Hi Rafael,
On Fri, Dec 13, 2019 at 11:14:16AM +0100, Rafael J. Wysocki wrote:
> Hi Dmitry,
>
> Unfortunately, this report was sent directly to me without any CCs to
> mailing lists.
>
> This is a tree with the v9 of the last patch from the software nodes series
> merged.
I tried fetching your linux-pm tree, but it does not contain the commit
Kbuild referenced. But you must be testing with an old version of tests
because I see the largest frame at 600 bytes, not the 2.5-3K as in your
logs:
dtor@dtor-ws:~/kernel/linux-next (swnode-refs-v9)$ make CFLAGS_KERNEL=-Wframe-larger-than=512
drivers/base/test/property-entry-test.o
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CC drivers/base/test/property-entry-test.o
drivers/base/test/property-entry-test.c: In function ‘pe_test_uint_arrays’:
drivers/base/test/property-entry-test.c:214:1: warning: the frame size of 600 bytes is larger than 512 bytes [-Wframe-larger-than=]
}
Could you please try the 0-day on your tree again?
Thanks.
>
> Cheers,
> Rafael
> Date: Tue, 10 Dec 2019 13:18:25 +0800
> From: kbuild test robot <lkp@intel.com>
> To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Subject: [pm:bleeding-edge] BUILD REGRESSION
> 208501f6808a1dc0205904ed84cac99da01bbf70
>
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
> branch HEAD: 208501f6808a1dc0205904ed84cac99da01bbf70 Merge branch 'acpi-pm' into bleeding-edge
>
> Regressions in current branch:
>
> drivers/base/test/property-entry-test.c:214:1: warning: the frame size of 2784 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> drivers/base/test/property-entry-test.c:214:1: warning: the frame size of 3128 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> drivers/base/test/property-entry-test.c:214:1: warning: the frame size of 3136 bytes is larger than 2048 bytes [-Wframe-larger-than=]
>
> Error ids grouped by kconfigs:
>
> recent_errors
> |-- arm-allmodconfig
> | `-- drivers-base-test-property-entry-test.c:warning:the-frame-size-of-bytes-is-larger-than-bytes
> |-- i386-allmodconfig
> | `-- drivers-base-test-property-entry-test.c:warning:the-frame-size-of-bytes-is-larger-than-bytes
> `-- mips-allmodconfig
> `-- drivers-base-test-property-entry-test.c:warning:the-frame-size-of-bytes-is-larger-than-bytes
>
> elapsed time: 352m
>
> configs tested: 98
>
> xtensa common_defconfig
> openrisc or1ksim_defconfig
> nios2 3c120_defconfig
> xtensa iss_defconfig
> c6x evmc6678_defconfig
> c6x allyesconfig
> nios2 10m50_defconfig
> openrisc simple_smp_defconfig
> arm at91_dt_defconfig
> arm64 defconfig
> arm multi_v5_defconfig
> arm64 allyesconfig
> arm allnoconfig
> arm efm32_defconfig
> arm sunxi_defconfig
> arm64 allnoconfig
> arm64 allmodconfig
> arm exynos_defconfig
> arm shmobile_defconfig
> arm multi_v7_defconfig
> sh allmodconfig
> sh rsk7269_defconfig
> sh sh7785lcr_32bit_defconfig
> sh allnoconfig
> sh titan_defconfig
> s390 allnoconfig
> s390 debug_defconfig
> s390 allmodconfig
> s390 defconfig
> arm allmodconfig
> i386 allnoconfig
> i386 defconfig
> i386 alldefconfig
> parisc c3000_defconfig
> parisc b180_defconfig
> parisc defconfig
> parisc allnoconfig
> um x86_64_defconfig
> um i386_defconfig
> um defconfig
> ia64 allmodconfig
> ia64 allnoconfig
> ia64 defconfig
> ia64 alldefconfig
> sparc64 allmodconfig
> sparc defconfig
> sparc64 allnoconfig
> sparc64 defconfig
> arc randconfig-a001-20191210
> ia64 randconfig-a001-20191210
> sparc randconfig-a001-20191210
> arm64 randconfig-a001-20191210
> arm randconfig-a001-20191210
> x86_64 lkp
> x86_64 rhel
> x86_64 rhel-7.6
> x86_64 fedora-25
> x86_64 kexec
> m68k multi_defconfig
> m68k m5475evb_defconfig
> h8300 h8300h-sim_defconfig
> h8300 edosk2674_defconfig
> m68k sun3_defconfig
> h8300 h8s-sim_defconfig
> m68k allmodconfig
> riscv allnoconfig
> riscv defconfig
> nds32 defconfig
> alpha defconfig
> csky defconfig
> nds32 allnoconfig
> sh randconfig-a001-20191209
> csky randconfig-a001-20191209
> s390 randconfig-a001-20191209
> xtensa randconfig-a001-20191209
> openrisc randconfig-a001-20191209
> i386 randconfig-d001-20191209
> x86_64 randconfig-d001-20191209
> i386 randconfig-d002-20191209
> x86_64 randconfig-d003-20191209
> i386 randconfig-d003-20191209
> x86_64 randconfig-d002-20191209
> arc allyesconfig
> microblaze nommu_defconfig
> microblaze mmu_defconfig
> arc defconfig
> powerpc allnoconfig
> mips allmodconfig
> mips 32r2_defconfig
> mips malta_kvm_defconfig
> mips 64r6el_defconfig
> mips allnoconfig
> mips fuloong2e_defconfig
> c6x randconfig-a001-20191209
> sparc64 randconfig-a001-20191209
> h8300 randconfig-a001-20191209
> microblaze randconfig-a001-20191209
> nios2 randconfig-a001-20191209
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
--
Dmitry
next prev parent reply other threads:[~2019-12-18 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 10:14 Fwd: [pm:bleeding-edge] BUILD REGRESSION 208501f6808a1dc0205904ed84cac99da01bbf70 Rafael J. Wysocki
2019-12-18 0:27 ` Dmitry Torokhov [this message]
2019-12-18 9:17 ` Rafael J. Wysocki
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=20191218002709.GA8314@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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