From: Matthew Wilcox <willy@infradead.org>
To: lkp@lists.01.org
Subject: Re: [xarray] 4e99d4e957: BUG:soft_lockup-CPU##stuck_for#s
Date: Tue, 11 Dec 2018 06:29:47 -0800 [thread overview]
Message-ID: <20181211142947.GC6830@bombadil.infradead.org> (raw)
In-Reply-To: <20181211095441.GR23332@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 2420 bytes --]
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 kernel and optional env $INSTALL_MOD_PATH
>
> kernel=$1
>
> initrds=(
> /osimage/yocto/yocto-tiny-i386-2016-04-22.cgz
> /lkp/lkp/lkp-i386.cgz
> /osimage/deps/debian-x86_64-2016-08-31.cgz/run-ipconfig.i386_2016-09-03.cgz
> )
>
> HTTP_PREFIX=https://download.01.org/0day-ci/lkp-qemu
> wget --timestamping "${initrds[@]/#/$HTTP_PREFIX}"
>
> {
> cat "${initrds[@]//*\//}"
> [[ $INSTALL_MOD_PATH ]] && (
> cd "$INSTALL_MOD_PATH"
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
When I do this, the only output I get is:
make: Entering directory '/home/willy/kernel/lkp-tests/bin/event'
gcc -c -o wakeup.o wakeup.c
gcc -static -o wakeup wakeup.o
rm -f wakeup.o
strip wakeup
make: Leaving directory '/home/willy/kernel/lkp-tests/bin/event'
Running under sh -x, I get as far as:
+ exec /home/willy/kernel/lkp-tests/lkp-exec/qemu -k ../idrext/.build-yocto/arch/x86/boot/bzImage job-script
Editing that script to set -x, I get to:
+ /home/willy/kernel/lkp-tests/sbin/pack -f -a x86_64 lkp-src
make: Entering directory '/home/willy/kernel/lkp-tests/bin/event'
gcc -c -o wakeup.o wakeup.c
gcc -static -o wakeup wakeup.o
rm -f wakeup.o
strip wakeup
make: Leaving directory '/home/willy/kernel/lkp-tests/bin/event'
+ exit
which would seem to indicate your 'pack' command failed with a non-zero
exit code? Adding set -x to _that_ script gives me:
+ find . -type d -exec chmod g+rwx '{}' ';'
+ chmod -R g+rw etc lib root usr
+ '[' -d /osimage/addon-x86_64 ']'
+ gzip -n -9 /home/willy/.lkp/cache/lkp-x86_64.cpio
+ mv -f /home/willy/.lkp/cache/lkp-x86_64.cpio.gz /home/willy/.lkp/cache/lkp-x86_64.cgz
+ [[ -n '' ]]
+ [[ -n '' ]]
+ exit
I'm using your top-of-tree lkp-tests, commit
e28c726dfe85e3e595ba4776a4eb92f2559d3ac0
By the way, I took this kernel config and ran it under one of your other
test cases (the one which runs Trinity) 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.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkp@01.org
Subject: Re: [LKP] [xarray] 4e99d4e957: BUG:soft_lockup-CPU##stuck_for#s
Date: Tue, 11 Dec 2018 06:29:47 -0800 [thread overview]
Message-ID: <20181211142947.GC6830@bombadil.infradead.org> (raw)
In-Reply-To: <20181211095441.GR23332@shao2-debian>
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 kernel and optional env $INSTALL_MOD_PATH
>
> kernel=$1
>
> initrds=(
> /osimage/yocto/yocto-tiny-i386-2016-04-22.cgz
> /lkp/lkp/lkp-i386.cgz
> /osimage/deps/debian-x86_64-2016-08-31.cgz/run-ipconfig.i386_2016-09-03.cgz
> )
>
> HTTP_PREFIX=https://download.01.org/0day-ci/lkp-qemu
> wget --timestamping "${initrds[@]/#/$HTTP_PREFIX}"
>
> {
> cat "${initrds[@]//*\//}"
> [[ $INSTALL_MOD_PATH ]] && (
> cd "$INSTALL_MOD_PATH"
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
When I do this, the only output I get is:
make: Entering directory '/home/willy/kernel/lkp-tests/bin/event'
gcc -c -o wakeup.o wakeup.c
gcc -static -o wakeup wakeup.o
rm -f wakeup.o
strip wakeup
make: Leaving directory '/home/willy/kernel/lkp-tests/bin/event'
Running under sh -x, I get as far as:
+ exec /home/willy/kernel/lkp-tests/lkp-exec/qemu -k ../idrext/.build-yocto/arch/x86/boot/bzImage job-script
Editing that script to set -x, I get to:
+ /home/willy/kernel/lkp-tests/sbin/pack -f -a x86_64 lkp-src
make: Entering directory '/home/willy/kernel/lkp-tests/bin/event'
gcc -c -o wakeup.o wakeup.c
gcc -static -o wakeup wakeup.o
rm -f wakeup.o
strip wakeup
make: Leaving directory '/home/willy/kernel/lkp-tests/bin/event'
+ exit
which would seem to indicate your 'pack' command failed with a non-zero
exit code? Adding set -x to _that_ script gives me:
+ find . -type d -exec chmod g+rwx '{}' ';'
+ chmod -R g+rw etc lib root usr
+ '[' -d /osimage/addon-x86_64 ']'
+ gzip -n -9 /home/willy/.lkp/cache/lkp-x86_64.cpio
+ mv -f /home/willy/.lkp/cache/lkp-x86_64.cpio.gz /home/willy/.lkp/cache/lkp-x86_64.cgz
+ [[ -n '' ]]
+ [[ -n '' ]]
+ exit
I'm using your top-of-tree lkp-tests, commit
e28c726dfe85e3e595ba4776a4eb92f2559d3ac0
By the way, I took this kernel config and ran it under one of your other
test cases (the one which runs Trinity) 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.
next prev parent reply other threads:[~2018-12-11 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:54 [xarray] 4e99d4e957: BUG:soft_lockup-CPU##stuck_for#s kernel test robot
2018-12-11 14:29 ` Matthew Wilcox [this message]
2018-12-11 14:29 ` [LKP] " Matthew Wilcox
2018-12-19 9:54 ` Rong Chen
2018-12-19 9:54 ` [LKP] " Rong Chen
2018-12-20 2:26 ` Rong Chen
2018-12-20 2:26 ` [LKP] " Rong Chen
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=20181211142947.GC6830@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.