From: Fengguang Wu <fengguang.wu@intel.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@01.org
Subject: [NFSv4.1] 6ae373394c4: kernel boot crash
Date: Fri, 6 Feb 2015 18:45:46 -0800 [thread overview]
Message-ID: <20150207024546.GA27323@wfg-t540p.sh.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Trond,
We noticed the below kernel crash on
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
commit 6ae373394c4257bad562817aa60464ff7fe8f9c4 ("NFSv4.1: Ask for no delegation on OPEN if using O_DIRECT")
testbox/testcase/testparams: vm-vp-quantal-x86_64/boot/1
0e3b137fbf0f4ab9 6ae373394c4257bad562817aa6
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:100 4% 2:46 dmesg.BUG:kernel_test_crashed
The last dmesg lines before the kernel crash are
[ 0.274266] NET: Registered protocol family 1
[ 0.275236] RPC: Registered named UNIX socket transport module.
[ 0.276123] RPC: Registered udp transport module.
[ 0.276860] RPC: Registered tcp transport module.
[ 0.277617] RPC: Registered tcp NFSv4.1 backchannel transport module
Thanks,
Fengguang
[-- Attachment #2: job.yaml --]
[-- Type: text/plain, Size: 985 bytes --]
---
testcase: boot
default-monitors:
default_watchdogs:
watch-oom:
watchdog:
cpufreq_governor:
model: qemu-system-x86_64 -enable-kvm
nr_vm: 64
nr_cpu: 2
memory: 360M
rootfs: quantal-core-x86_64.cgz
boot-slabinfo:
boot-meminfo:
memmap:
boot-memory:
boot-time:
kernel-size:
sleep: 1
branch: nfs/linux-next
commit: 6ae373394c4257bad562817aa60464ff7fe8f9c4
repeat_to: 2
testbox: vm-vp-quantal-x86_64-3
tbox_group: vm-vp-quantal-x86_64
kconfig: x86_64-rhel
enqueue_time: 2015-02-05 18:54:42.323364417 +08:00
kernel: "/kernel/x86_64-rhel/6ae373394c4257bad562817aa60464ff7fe8f9c4/vmlinuz-3.19.0-rc5-g6ae3733"
user: lkp
queue: rand
result_root: "/result/vm-vp-quantal-x86_64/boot/1/quantal-core-x86_64.cgz/x86_64-rhel/6ae373394c4257bad562817aa60464ff7fe8f9c4/0"
job_file: "/lkp/scheduled/vm-vp-quantal-x86_64-3/rand_boot-1-quantal-core-x86_64.cgz-x86_64-rhel-6ae373394c4257bad562817aa60464ff7fe8f9c4-1.yaml"
dequeue_time: 2015-02-05 18:55:49.602324841 +08:00
job_state: finished
next reply other threads:[~2015-02-07 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 2:45 Fengguang Wu [this message]
2015-02-07 3:43 ` Trond Myklebust
2015-02-07 4:31 ` Fengguang Wu
2015-02-07 4:33 ` Trond Myklebust
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=20150207024546.GA27323@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=trond.myklebust@primarydata.com \
/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®