y start timing after the "touch" returns?
The result is normal after retesting, thank you for helping us improve
the test.
Best Regards,
Rong, Chen
--b.
On 08/24/2018 12:55 AM, Dave Jiang wrote:
I am not able to reproduce when I booted my test system with "mem=8G
memmap=4G!8G". I ended up with a single pmem:
The issue seems to be related to specific machines,
If you need any other debug log, please tell me.
Best Regards,
p qemu -k job-script # job-script is attached in this
email
Thanks,
Rong, Chen
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.18.0-rc5 Kernel Configuration
#
#
# Compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DEC
section.
Something strange happened, we're trying to figure out the root cause.
Best Regards,
Rong Chen
Thanks,
Daniel
test-description: Will It Scale takes a testcase and runs it from 1 through to
n parallel copies to see if the testcase will scale. It builds both a process
an
On 08/10/2018 04:35 PM, Joerg Roedel wrote:
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
commit a13c600e15de44ccf03df28d3311ef3cb754ed9b
Author: Joerg Roedel
AuthorDate: Wed Aug 8 13:16:40 2018 +0200
Commit: Thomas Gleixner
CommitDate: Thu Aug 9 20:42:07 2018 +
/test_ubsan.c? Please can you double-
check this result?
Hi,
I'm sorry for the trouble, It's a false warning, we will look into it.
Best Regards,
Rong Chen
Thanks.
[auto build test WARNING on arm/for-next]
[also build test WARNING on v4.20-rc5]
[if your patch is applied to the wron
ity) and didn't see a boot problem,
so either it's something specific to this setup, or the problem got
fixed between this commit and current top-of-tree.
Please accept my apologies for taking your time, the reproduce tool was broken
for a long time, and it's fixed now.
if it can't be reproduced, here is the original
bzImage(https://download.01.org/0day-ci/lkp-qemu/fbc/4e99d4e9579d3b950bf4b38d0d64eb1b9be78761/).
Best Regards,
Rong Chen
the original
bzImage(https://download.01.org/0day-ci/lkp-qemu/fbc/5404a7f1c21cfda061712bedf2d06cc0f6c755e9/)
for your reference.
Best Regards,
Rong Chen
On 12/19/2018 05:54 PM, Rong Chen wrote:
On 12/11/2018 10:29 PM, Matthew Wilcox wrote:
On Tue, Dec 11, 2018 at 05:54:41PM +0800, kernel test robot wrote:
# To reproduce,
# 1) save job-script and this script (both are attached in 0day
report email)
# 2) run this script with your compiled
code,
and the robot shouldn't track old commits. we'll fix it.
Best Regards,
Rong Chen
thanks,
greg k-h
ivers are not enabled, so the build error does not
happen.
None of these Kconfig symbols (from the attached .config file) is enabled
after running "make oldconfig":
we used "make olddefconfig" to correct possible problems.
Best Regards,
Rong Chen
CONFIG_SND
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
how is this related? Could someone please explain this.
It Iooks like a kbuild issue, we will looking into it.
Best Regards,
Rong Chen
during this testing?
It wasn't applied during this testing.
Best Regards,
Rong Chen
https://github.com/0day-ci/linux repo needs a better way to stay in sync?
Sorry for the delay, indeed, it's a issue from 0day-CI, we'll update
linux-mm in the system.
Best Regards,
Rong Chen
ave that hardware, but does the following help? (It at least
builds for me, but your mileage may vary.)
Thanx, Paul
Yes, the patch works for kbuild robot.
Thanks,
Rong Chen
-
don't have more logs to prove it.
$ grep BTRFS config-5.0.0-rc8-00196-g70d28b0
CONFIG_BTRFS_FS=y
# CONFIG_BTRFS_FS_POSIX_ACL is not set
# CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set
# CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set
# CONFIG_BTRFS_DEBUG is not set
# CONFIG_BTRFS_ASSERT is no
On Tue, Apr 02, 2019 at 06:04:24AM -0700, Paul E. McKenney wrote:
> On Tue, Apr 02, 2019 at 08:32:45AM +0800, Rong Chen wrote:
> >
> > On 3/28/19 3:57 AM, Paul E. McKenney wrote:
> > >On Mon, Mar 25, 2019 at 02:34:27AM +0800, kbuild test robot wrote:
> > >>t
for the feedback, we'll take a look.
Best Regards,
Rong Chen
Thanks,
Vincenzo
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
htt
/soc/litex/litex_soc_ctrl.o: file format elf32-shbig-linux
Reported-by: kernel test robot
Link: https://lore.kernel.org/linux-mm/202101261118.gbbyslhu-...@intel.com
Signed-off-by: Rong Chen
---
scripts/recordmcount.pl | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/recordm
the advice, do you mean we don't need to test randconfig for
arch s390?
Best Regards,
Rong Chen
$ make allmodconfig
$ scripts/config -d PCI ## this also disables HAS_IOMEM
$ make oldconfig
$ make all
The latter gives a full list of drivers etc. that use iomemp/ioremap
etc. as well
On 2/2/21 1:22 PM, Randy Dunlap wrote:
On 2/1/21 9:09 PM, Rong Chen wrote:
On 2/2/21 6:38 AM, Randy Dunlap wrote:
On 1/31/21 4:06 PM, kernel test robot wrote:
Hi Wang,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
Fixes: c2aa8afc36fa (selftests/vm: rename run_vmtests --> run_vmtests.sh)
Signed-off-by: Rong Chen
---
tools/testing/selftests/vm/{run_vmtests => run_vmtests.sh} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename tools/testing/selftests/vm/{run_vmtests => run_vmtests.sh} (10
On 2/8/21 10:19 PM, Borislav Petkov wrote:
On Sun, Feb 07, 2021 at 04:15:11PM +0800, Rong Chen wrote:
Thanks for the advice, we'll add the check to our cluster,
and sorry for the inconvenience.
When it comes to the tip tree, I'd say you guys are much better off not
scraping any pa
g_hw_init is wrong.
I'd be very interested to know how the identified patch would be able to
have this effect.
Hi Clang Team,
The problem is found by the latest clang, and I can't reproduce it with
clang-11,
could you take a look?
Best Regards,
Rong Chen
confusing.
Hi Gao Xiang,
Sorry for the inconvenience, we'll silence the reports on this commit.
Best Regards,
Rong Chen
Thanks,
Gao Xiang
:: The code at line 161 was first introduced by commit
:: a12ee2349312d7112b9b7c6ac2e70c5ec2ca334e arch/sparc: Introduce
cmpxchg_u8 SPARC
:
, we'll improve the commit message.
Best Regards,
Rong Chen
Fixes: e33929537b76 ("platform/x86: thinkpad_acpi: use standard charge control
attribute names")
Signed-off-by: kernel test robot
run more times
on the parent commit and can reproduce the error too.
Best Regards,
Rong Chen
Dan is long upstream:
1c3d69ab5348
Hi David,
Sorry for the inconvenience, the bot will check head commit before
reporting usually, we'll take a look.
Best Regards,
Rong Chen
New smatch warnings:
drivers/virtio/virtio_mem.c:1031 virtio_mem_mb_plug_any_sb() error:
uninitialized symbo
ively added, not when its content is simply modified?
If not it would be nice to be able to see the difference in a diff-like
format.
Thanks for your advice, we'll seriously consider it.
Best Regards,
Rong Chen
ion to avoid reporting this kind of problem.
Best Regards,
Rong Chen
Mike
New smatch warnings:
drivers/md/dm-mpath.c:524 multipath_clone_and_map() error: double unlocked
'm->lock' (orig line 516)
Old smatch warnings:
drivers/md/dm-mpath.c:446 choose_pgpath() error: double unloc
rame-larger-than=]
static int get_victim_by_default(struct f2fs_sb_info *sbi,
Best Regards,
Rong Chen
On 2021/1/9 21:18, kernel test robot wrote:
Hi Chao,
FYI, the error/warning still remains.
tree:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 996e435fd401de35d
nelle warning, it seems Julia Lawall didn't forward it to you,
it maybe not a real problem.
https://lists.01.org/hyperkitty/list/kbu...@lists.01.org/message/ZN45D2QHCG5W4KMOGVBLUCUOKH32LFHE/
Best Regards,
Rong Chen
elapsed time: 722m
configs tested: 164
configs skipped: 2
gcc tested co
for syzbot.
Can we do that for these kernel test robot reports too? Please?
Linus
Hi Linus,
Sorry for the inconvenience and we're working on it right now.
Happy New Year!
Best Regards,
Rong Chen
On 3/23/21 12:24 AM, Oliver Hartkopp wrote:
Hi Rong,
On 22.03.21 09:52, Rong Chen wrote:
On 3/21/21 10:19 PM, Oliver Hartkopp wrote:
Two reminders in two days? ;-)
Did you check my answer here?
https://lore.kernel.org/lkml/afffeb73-ba4c-ca2c-75d0-9e7899e5c...@hartkopp.net/
And did
Hi Vincent,
On 3/23/21 1:46 PM, Vincent MAILHOL wrote:
Hi Oliver and Rong,
This is an interesting and quite surprising issue!
On Tue. 23 mars 2021 at 11:54, Rong Chen wrote:
On 3/23/21 12:24 AM, Oliver Hartkopp wrote:
Hi Rong,
On 22.03.21 09:52, Rong Chen wrote:
On 3/21/21 10:19 PM
On 3/23/21 4:54 PM, Marc Kleine-Budde wrote:
On 23.03.2021 09:32:10, Oliver Hartkopp wrote:
I wonder if the compiler configurations (gcc -v) or the options used at
kernel build time are identical.
I tested several compilers and with my .config never triggered a
problem, but with Rong Chen
ooks to be false positive.
Hi Viresh,
Thanks for the feedback, we'll stop the bot sending such report again.
Best Regards,
Rong Chen
/usb/dwc3/dwc3-xilinx.c
index a59e1494b1a0..f42f4cbffab0 100644
--- a/drivers/usb/dwc3/dwc3-xilinx.c
+++ b/drivers/usb/dwc3/dwc3-xilinx.c
@@ -1,5 +1,5 @@
// SPDX-License-Identifier: GPL-2.0
-/**
+/*
* dwc3-xilinx.c - Xilinx DWC3 controller specific glue driver
*
* Authors: Manish Narani
Best R
r the suggestion, we have added to the allowlist.
Best Regards,
Rong Chen
config: powerpc64-randconfig-r001-20210301 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project
5de09ef02e24d234d9fc0cd1c6dfe18a1bb784b0)
reproduce (this is a W=1 build):
ed the related tests.
Best Regards,
Rong Chen
Arnd
___
kbuild-all mailing list -- kbuild-...@lists.01.org
To unsubscribe send an email to kbuild-all-le...@lists.01.org
DLC for 8 byte payload length (9 ..
15) */
Best Regards,
Rong Chen
Maybe there's a mismatch in include files - or BUILD_BUG_ON()
generally does not work with unions on ARM as assumed here:
https://lore.kernel.org/lkml/6e57d5d2-9b88-aee6-fb7a-82e24144d...@hartkopp.net/
In both
on how those things can be
reproduced.
Hi Borislav,
Sorry for the inconvenience, there's a bug in our system which sent
internal reports to outside.
please ignore the warnings.
Best Regards,
Rong Chen
l fix both asap.
Best Regards,
Rong Chen
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
riscv64-linux-gnu-objcopy: 'arch/riscv/kernel/vdso/vdso.so.dbg': No such file
This error only occurs b
fig file's ITCM_RAM_BASE parameter is expected to be
set/modified by the user. The default value of 0x is invalid.
Hi Randy,
Thanks for the advice, we'll modify the config files for arch csky.
Best Regards,
Rong Chen
e already explained this in:
RE: [bug report] ASoC: Intel: catpt: Firmware loading and context restore
https://www.spinics.net/lists/alsa-devel/msg117145.html
Hi all,
Thanks a lot, we'll ignore the warning next time.
Best Regards,
Rong Chen
.org/show_bug.cgi?id=38809
Hi Andrey,
Thanks for the explanation, we'll disable CONFIG_KASAN_SW_TAGS.
Best Regards,
Rong Chen
On 11/24/20 5:13 PM, Andy Shevchenko wrote:
On Tue, Nov 24, 2020 at 10:06 AM Rong Chen wrote:
On 11/23/20 7:41 PM, Rojewski, Cezary wrote:
On 2020-11-23 11:53 AM, Andy Shevchenko wrote:
On Sun, Nov 22, 2020 at 03:52:27AM +0800, kernel test robot wrote:
...
This sounds like false
On 11/24/20 7:51 PM, Andrey Konovalov wrote:
On Tue, Nov 24, 2020 at 9:02 AM Rong Chen wrote:
On 11/23/20 10:15 PM, Andrey Konovalov wrote:
On Thu, Nov 19, 2020 at 11:16 PM kernel test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head
size .LPBX0," ] can avoid the
error.
+ [ ! = .size -a ABI = .LPBX0, ]
./kernel/gcov/geninfosize.sh: 13: [: =: unexpected operator
Best Regards,
Rong Chen
On 3/13/21 1:52 AM, Linus Torvalds wrote:
On Thu, Mar 11, 2021 at 7:50 PM Rong Chen wrote:
The issue is from a=!, and [ "$a $b" = ".size .LPBX0," ] can avoid the
error.
+ [ ! = .size -a ABI = .LPBX0, ]
./kernel/gcov/geninfosize.sh: 13: [: =: unexpected operator
But
When building out-of-tree, attempting to make target from $(OUTPUT) directory:
make[1]: *** No rule to make target '$(OUTPUT)/protection_keys.c', needed by
'$(OUTPUT)/protection_keys_32'.
Reported-by: kernel test robot
Signed-off-by: Rong Chen
---
tools/testing/selft
'alloc_contig_ratelimit' [-Wmissing-prototypes]
8348 | int alloc_contig_ratelimit(void)
| ^~
mm/page_alloc.c:8353:6: warning: no previous prototype for
'dump_migrate_failure_pages' [-Wmissing-prototypes]
8353 | void dump_migrate_failure_pages(struct list_head *page_list)
Best Regards,
Rong Chen
pplied the patches to a tree that had
the required objtool patches as described in 0/n. Or better yet, don't
scrape emails if the 0/n includes a git link which you'll run on anyway.
Hi Peter,
Thanks for the advice, we'll add the check to our cluster,
and sorry for the inconvenience.
Best Regards,
Rong Chen
build test ERROR on b65054597872ce3aefbc6a666385eabdf9e288da]
url:
https://github.com/0day-ci/linux/commits/Erez-Geva/Add-sending-TX-hardware-timestamp-for-TC-ETF-Qdisc/20201210-000521
I can not find this commit
Hi Erez,
The url has been recovered now.
Best Regards,
Rong Chen
base
I have created a issue in GCC Bugzilla:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98310
Best Regards,
Rong Chen
Regards,
Willy
___
kbuild-all mailing list -- kbuild-...@lists.01.org
To unsubscribe send an email to kbuild-all-le...@lists.01.org
A [=y]
WARNING: unmet direct dependencies detected for HOTPLUG_CPU
Depends on [n]: SMP [=y] && (PPC_PSERIES [=n] || PPC_PMAC [=n] ||
PPC_POWERNV [=n] || FSL_SOC_BOOKE [=n])
Selected by [y]:
- PM_SLEEP_SMP [=y] && SMP [=y] && (ARCH_SUSPEND_POSSIBLE [=y] ||
ARCH_HIBERNATION_POSSIBLE [=y]) && PM_SLEEP [=y]
Please begin including Kconfig warnings. I have asked previously but...
thanks.
Hi Randy,
We have added Kconfig warnings in reports now. please see another
report:
https://lore.kernel.org/linux-block/202012170150.y7ycoei9-...@intel.com/
Best Regards,
Rong Chen
branch name to reflect the branch does not only queue
chipidea USB patches.
next branch: for-usb-next
fixes branch: for-usb-fixes
Peter
Hi Peter,
Thanks for the feedback, we'll update it on the CI system.
Best Regards,
Rong Chen
[If your patch is applied to the wrong git tree, kindly
.files_per_sec instead of
fsmark.app_overhead in the subject.
Best Regards,
Rong Chen
o a git tree to test. Maybe your
patch was applied to a wrong git tree.
Best Regards,
Rong Chen
generic/269.full file for your reference.
Best Regards,
Rong Chen
btrfs-progs v4.7.3
See http://btrfs.wiki.kernel.org for more information.
Label: (null)
UUID:
Node size: 16384
Sector size:4096
Filesystem size:512.00MiB
Block group profil
o apply the
patch to this particular commit.
Thanks.
Thanks for your comment, robot applied the patch to the head of
char-misc/char-misc-testing,
It seems the branch was still old at that moment. We'll fix it asap.
Best Regards,
Rong Chen
/master.
Sorry for the inconvenience, we'll take a look. btw, 0day-CI introduced
'--base' option to record base tree info in format-patch.
please see https://stackoverflow.com/a/37406982
Best Regards,
Rong Chen
Alex
[cannot apply to v5.3-rc7 next-20190904]
[if your patch is
Hi Peter,
We have updated to only send the reports to you, please see
https://github.com/intel/lkp-tests/blob/master/repo/linux/omap-audio
Best Regards,
Rong Chen
On 8/9/19 9:21 PM, Julia Lawall wrote:
On Fri, 9 Aug 2019, Peter Ujfalusi wrote:
On 09/08/2019 15.31, Mark Brown wrote:
On
Hi,
The patch can fix the issue for me.
Best Regards,
Rong Chen
On 2/20/19 8:57 PM, Michal Hocko wrote:
Rong Chen,
coudl you double check this indeed fixes the issue for you please?
On Mon 18-02-19 19:15:44, Michal Hocko wrote:
From: Michal Hocko
Rong Chen has reported the following boot
?
AFAICT, this triggers only on gcc-4.9, 32-bit build. Or do you have
other configurations which trigger it?
Hi Boris,
we have added it to the blacklist, and there's no other configuration
found in the past reports.
Best Regards,
Rong Chen
by
https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git/commit/?h=for-v5.1&id=28713169d879b67be2ef2f84dcf54905de238294
Thanks for your explanation. we'll blacklist it.
Best Regards,
Rong Chen
Gr{oetje,eeting}s,
Geert
ext4/307 ext4/308 generic/001 generic/002 generic/003
Given some of the failures, especially this one:
Yes, it's our fault, we have fixed it.
Best Regards,
Rong Chen
ext4/307- output mismatch (see
/lkp/benchmarks/xfstests/results//ext4/307.out.bad)
--- tests/ext4/307.ou
for systemd (232-25+deb9u2) ...
[ 48.959231]
[ 49.729064] 25 Jul 16:02:52 ntpdate[1803]: step time server 192.168.1.1
offset 28724.486990 sec
[ 49.729069]
[ 81.657115] can't load the disk LABEL=LKP-ROOTFS, skip testing...
Thanks,
Rong Chen
dmesg.xz
Description: applicatio
sn't complain about missing/corrupt BTF.
We need to convince lkp people to upgrade clang, otherwise, I suppose,
we'll get more of these reportings after your recent df0b77925982 :-(
Thanks for the clarification, we'll upgrade clang asap.
Best Regards,
Rong Chen
# libbpf:
ntel(R) CPU 000 @ 2.27GHz
model: Westmere-EX
memory: 256G
nr_node: 4
nr_cpu: 80
Best Regards,
Rong Chen
Thanks,
tglx
On 6/25/19 2:24 PM, Thomas Gleixner wrote:
Rong,
On Tue, 25 Jun 2019, Rong Chen wrote:
On 6/22/19 3:08 AM, Thomas Gleixner wrote:
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m
2G
I cannot reproduce that issue. What's the underlying hardware machine?
On 6/25/19 7:32 PM, Thomas Gleixner wrote:
Rong,
On Tue, 25 Jun 2019, Rong Chen wrote:
On 6/25/19 2:24 PM, Thomas Gleixner wrote:
On 6/22/19 3:08 AM, Thomas Gleixner wrote:
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp
2 -m
2G
I cannot reproduce that issue. What&#
rubygems/core_ext/kernel_require.rb:54:in
`require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require': cannot
load such file -- active_support/core_ext/enumerable (LoadError)
Hi Josef,
I tried the latest lkp-tests, and didn't have the problem. Could you
please up
On 6/26/19 11:17 AM, Josef Bacik wrote:
On Wed, Jun 26, 2019 at 10:39:36AM +0800, Rong Chen wrote:
On 6/25/19 10:22 PM, Josef Bacik wrote:
On Fri, Jun 21, 2019 at 08:48:03AM +0800, Huang, Ying wrote:
"Huang, Ying" writes:
"Huang, Ying" writes:
Hi, Josef,
kerne
. +Rong
to help check the exact problem.
Hi all,
There's a problem with the network in our side, we're trying to solve it.
Sorry for the inconvenience that may have caused to you.
Best Regards,
Rong Chen
--
Kalle Valo
inconvenience, the robot noticed that the error "WARNING:
held lock freed!" first appears with commit fcc784be83
and didn't find the error in parent commit. then it sent it out
automatically. We'll improve the robot to sent reports more carefully.
Best Regards,
Ro
On 2/18/19 5:03 PM, Michal Hocko wrote:
On Mon 18-02-19 16:47:26, Rong Chen wrote:
On 2/18/19 3:08 PM, Michal Hocko wrote:
On Mon 18-02-19 13:28:23, kernel test robot wrote:
[...]
[ 40.305212] PGD 0 P4D 0
[ 40.308255] Oops: [#1] PREEMPT SMP PTI
[ 40.313055] CPU: 1 PID: 239 Comm
kport.
Ok, let's see what it is using the web link:
url:
https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/tracing-probes-uaccess-Add-support-user-space-access/20190303-203749
Yeah, that just gives a github 404 error.
Sorry for the broken link, It's ok now.
Best Regard
thing or the warning is just confused?
Thanks for your reply. It looks like a false positive. We'll look into it.
Best Regards,
Rong Chen
[...]
00508538 Michal Hocko 2019-01-07 915 t =
find_lock_task_mm(p);
00508538 Michal Hocko 2019-01-07 916
mp/vdisk-nfs/disk-vm-kbuild-1G-11-3,if=none,id=hd3,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd3,scsi-id=1,lun=3 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-4,if=none,id=hd4,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd4,scsi-id=1,lun=4
Bes
the situation a little more thoroughly (ie at different offsets).
Signed-off-by: Matthew Wilcox
Thank you test-bot. Can you check if this patch fixes the problem?
Thanks, It works.
Best Regards,
Rong Chen
diff --git a/lib/test_ida.c b/lib/test_ida.c
index 2d1637d8136b
least, it comes to a prompt at
which I can log in. I'm not sure whether anything else is meant to happen.
It's a 0day problem, we will fix it as soon as possible.
Best Regards,
Rong Chen
om/0day-ci/linux
UPDATE-20180911-024633/Tetsuo-Handa/mm-oom-Fix-unnecessary-killing-of-additional-processes/20180910-163452
Do you have a msg-id to the patch that has been tested?
message_id: 20180910125513.311-2-mho...@kernel.org
Best Regards,
Rong Chen
On 09/25/2018 03:31 PM, Michal Hocko wrote:
On Tue 25-09-18 15:00:15, Rong Chen wrote:
On 09/25/2018 02:06 PM, Michal Hocko wrote:
On Tue 25-09-18 13:48:20, kernel test robot wrote:
FYI, we noticed the following commit (built with gcc-7):
commit: 6209f6fc62835d84c2a92d237588a114e39436ce
. What am I supposed to do
with this mail?
Hi,
Attached please find the dmesg/reproduce files in previous mail.
please ignore the report if it's a false positive.
Best Regards,
Rong Chen
Thanks,
tglx
___
LKP mailing list
l...@lists.01.org
emu? A Intel one or AMD one?
It's a Intel one,
model: Nehalem-EX
memory: 224G
nr_node: 4
nr_cpu: 64
nr_socket: 4
brand: Intel(R) Xeon(R) CPU X7560 @ 2.27GHz
Best Regards,
Rong Chen
;prepare0' failed
make: *** [prepare0] Error 2
The command in above step 3 was mentioned in the bot mail.
Regards
Syed Nayyar Waris
Hi Syed Nayyar Waris,
We can reproduce the warning with the steps in original report,
you may need to build the whole kernel instead of the 'lib'.
Best Regards,
Rong Chen
n -fshort-wchar
-fno-PIE \
-Werror=implicit-function-declaration
-Werror=implicit-int \
-Wno-format-security \
Best Regards,
Rong Chen
in testcase: will-it-scale
on test machine: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @
2.30GHz with 192G memory
with following par
Hi Tony,
Thanks for the feedback, we'll fix the wrong base.
Best Regards,
Rong Chen
dback, we'll fix the wrong base.
Best Regards,
Rong Chen
Hi Herbert,
Could you take a look at this warning? Roberto mentioned you in previous
report:
https://lore.kernel.org/linux-integrity/9dbec9465bda4f8995a42593eb0db...@huawei.com/
Best Regards,
Rong Chen
On 6/17/20 9:35 PM, kernel test robot wrote:
Hi Roberto,
FYI, the error/warning still
mit failed earlier before the ld.lld error, we're going
to optimize the bisect logic to avoid false positive.
Best Regards,
Rong Chen
+ Kees, idk if this is the warning from the orphan section placement,
if any of those patches have landed?
+ Fangrui, who might know more about this w
on here? Did you just start testing arc? The commit
is... really old.
Hi Pavel,
Only this error "arceb-elf-ld: include/linux/leds.h:193: undefined
reference to `devm_led_classdev_register_ext'" was found in this commit,
other errors are for reference only, and the test config is
On 10/10/20 11:49 AM, Randy Dunlap wrote:
On 10/9/20 8:19 PM, Rong Chen wrote:
On 10/8/20 3:15 PM, Pavel Machek wrote:
Hi!
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c85fb28b6f999db9928b841f63f1beeb3074eeca
commit
all the circumstances.
Best Regards,
Rong Chen
nition-with-different-types-(-int64_t-(aka-long-)-vs-__s64-(aka-long-long-))
`--
tools-include-linux-types.h:error:typedef-redefinition-with-different-types-(-uint64_t-(aka-unsigned-long-)-vs-__u64-(aka-unsigned-long-long-))
Best Regards,
Rong Chen
We will consider how to show useful produ
strtonum never defined
This looks like a problem with the test setup.
Hi Matthew,
Thanks for the response, we'll double check it.
Best Regards,
Rong Chen
/osimage/yocto/$initrd
That results in a 404. Still the same problem as months ago.
Hi Thomas,
Sorry about that, we'll fix it soon.
Best Regards,
Rong Chen
initrd=yocto-trinity-x86_64.cgz
works
___
LKP mailing list -- l...@lists.01.o
eads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G
memory
with following parameters:
nr_task: 100%
mode: thread
test: unlink2
cpufreq_governor: performance
ucode: 0x21
I'll send another report for this regression.
Best Regards,
Rong Chen
On 8/27/20 1:30 AM, Catalin Marinas wrote:
On Tue, Aug 25, 2020 at 11:02:40PM -0400, Qian Cai wrote:
On Aug 25, 2020, at 8:44 PM, Rong Chen wrote:
I rebuilt the kernel on commit c566586818 but the error changed to
"RIP: 0010:clear_page_orig+0x12/0x40", and the error can be
rep
1 - 100 of 122 matches
Mail list logo
