* [NFSv4.1] 6ae373394c4: kernel boot crash
@ 2015-02-07 2:45 Fengguang Wu
2015-02-07 3:43 ` Trond Myklebust
0 siblings, 1 reply; 4+ messages in thread
From: Fengguang Wu @ 2015-02-07 2:45 UTC (permalink / raw)
To: Trond Myklebust; +Cc: LKML, lkp
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [NFSv4.1] 6ae373394c4: kernel boot crash
2015-02-07 2:45 [NFSv4.1] 6ae373394c4: kernel boot crash Fengguang Wu
@ 2015-02-07 3:43 ` Trond Myklebust
2015-02-07 4:31 ` Fengguang Wu
0 siblings, 1 reply; 4+ messages in thread
From: Trond Myklebust @ 2015-02-07 3:43 UTC (permalink / raw)
To: Fengguang Wu; +Cc: LKML, LKP
On Fri, Feb 6, 2015 at 9:45 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>
> 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
Hi Fengguang,
I'm trying to reproduce this issue, but so far no luck. Do you have
any details on the test itself that you could share with me?
Thanks
Trond
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [NFSv4.1] 6ae373394c4: kernel boot crash
2015-02-07 3:43 ` Trond Myklebust
@ 2015-02-07 4:31 ` Fengguang Wu
2015-02-07 4:33 ` Trond Myklebust
0 siblings, 1 reply; 4+ messages in thread
From: Fengguang Wu @ 2015-02-07 4:31 UTC (permalink / raw)
To: Trond Myklebust; +Cc: LKML, LKP
Hi Trond,
On Fri, Feb 06, 2015 at 10:43:34PM -0500, Trond Myklebust wrote:
> On Fri, Feb 6, 2015 at 9:45 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> >
> > 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
>
>
> Hi Fengguang,
>
> I'm trying to reproduce this issue, but so far no luck. Do you have
> any details on the test itself that you could share with me?
It looks like a false report, sorry! The real crash dmesg is much
longer and it ends here:
[ 14.605487] i6300esb: Unexpected close, not stopping watchdog!
Which is not relevant to the NFS change at all.
The dmesg I looked at happen to be truncated (perhaps by email server)
exactly at a NFS line, which treats me to believe it's a good bisect.
Cheers,
Fengguang
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [NFSv4.1] 6ae373394c4: kernel boot crash
2015-02-07 4:31 ` Fengguang Wu
@ 2015-02-07 4:33 ` Trond Myklebust
0 siblings, 0 replies; 4+ messages in thread
From: Trond Myklebust @ 2015-02-07 4:33 UTC (permalink / raw)
To: Fengguang Wu; +Cc: LKML, LKP
On Fri, Feb 6, 2015 at 11:31 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> Hi Trond,
>
> On Fri, Feb 06, 2015 at 10:43:34PM -0500, Trond Myklebust wrote:
>> On Fri, Feb 6, 2015 at 9:45 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>> >
>> > 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
>>
>>
>> Hi Fengguang,
>>
>> I'm trying to reproduce this issue, but so far no luck. Do you have
>> any details on the test itself that you could share with me?
>
> It looks like a false report, sorry! The real crash dmesg is much
> longer and it ends here:
>
> [ 14.605487] i6300esb: Unexpected close, not stopping watchdog!
>
> Which is not relevant to the NFS change at all.
>
> The dmesg I looked at happen to be truncated (perhaps by email server)
> exactly at a NFS line, which treats me to believe it's a good bisect.
>
> Cheers,
> Fengguang
Phew. So I'm off the hook then. :-)
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-02-07 4:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-07 2:45 [NFSv4.1] 6ae373394c4: kernel boot crash Fengguang Wu
2015-02-07 3:43 ` Trond Myklebust
2015-02-07 4:31 ` Fengguang Wu
2015-02-07 4:33 ` Trond Myklebust
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®