From: Boaz Harrosh <bharrosh@panasas.com>
To: Joerg Platte <jplatte@naasa.net>
Cc: <linux-kernel@vger.kernel.org>, NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Kernel 3.4.X NFS regression
Date: Sun, 10 Jun 2012 14:43:55 +0300 [thread overview]
Message-ID: <4FD4887B.1050901@panasas.com> (raw)
In-Reply-To: <4FD47D4E.9070307@naasa.net>
Forwarding to Linux-NFS ML
On 06/10/2012 01:56 PM, Joerg Platte wrote:
> All 3.4 kernels I tried so far (3.4, 3.4.1 and 3.4.2) suffer from the
> same NFS related problem:
>
> Jun 10 09:23:36 coco kernel: INFO: task kworker/u:1:8 blocked for more
> than 120 seconds.
> Jun 10 09:23:36 coco kernel: "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Jun 10 09:23:36 coco kernel: kworker/u:1 D 002ba28c 0 8
> 2 0x00000000
> Jun 10 09:23:36 coco kernel: df465ec0 00000046 00000005 002ba28c
> 00000000 0000000a 00000282 df465e70
> Jun 10 09:23:36 coco kernel: df465ec0 df44d2b0 ffff6b60 df465e84
> df44d2b0 e33fa6b3 00000282 de764ae0
> Jun 10 09:23:36 coco kernel: ffffffff d78bcfb8 df465e8c c012e0f6
> df465ea4 c013610c 00000000 d78bcf80
> Jun 10 09:23:36 coco kernel: Call Trace:
> Jun 10 09:23:36 coco kernel: [<c012e0f6>] ? add_timer+0x11/0x17
> Jun 10 09:23:36 coco kernel: [<c013610c>] ? queue_delayed_work_on+0x74/0xf0
> Jun 10 09:23:36 coco kernel: [<c0136ba4>] ? queue_delayed_work+0x1b/0x28
> Jun 10 09:23:36 coco kernel: [<c0350f5b>] schedule+0x1d/0x4c
> Jun 10 09:23:36 coco kernel: [<e0cda5f1>] cld_pipe_upcall+0x4e/0x75 [nfsd]
> Jun 10 09:23:36 coco kernel: [<e0cda678>]
> nfsd4_cld_grace_done+0x60/0x99 [nfsd]
> Jun 10 09:23:36 coco kernel: [<e0cd9cb5>]
> nfsd4_record_grace_done+0x10/0x12 [nfsd]
> Jun 10 09:23:36 coco kernel: [<e0cd6696>] laundromat_main+0x291/0x2d8
> [nfsd]
> Jun 10 09:23:36 coco kernel: [<c0136d2f>] process_one_work+0xff/0x325
> Jun 10 09:23:36 coco kernel: [<c0134bec>] ? start_worker+0x20/0x23
> Jun 10 09:23:36 coco kernel: [<e0cd6405>] ?
> nfsd4_process_open1+0x32b/0x32b [nfsd]
> Jun 10 09:23:36 coco kernel: [<c013727a>] worker_thread+0xf4/0x39a
> Jun 10 09:23:36 coco kernel: [<c0137186>] ? rescuer_thread+0x231/0x231
> Jun 10 09:23:36 coco kernel: [<c013a556>] kthread+0x6c/0x6e
> Jun 10 09:23:36 coco kernel: [<c013a4ea>] ? kthreadd+0xe8/0xe8
> Jun 10 09:23:36 coco kernel: [<c035263e>] kernel_thread_helper+0x6/0xd
>
> A kworker task is stuck in D state and nfs mounts from other clients do
> not work at all. This happens only on one machine, another one with the
> same kernel (same self compiled Debian package) works. All previous 3.3
> kernels work as well.
>
> Since this machine is remote it is not that easy to bisect to find the
> bad commit. Are there any other things I can try?
>
> regards,
> Joerg
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next parent reply other threads:[~2012-06-10 11:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FD47D4E.9070307@naasa.net>
2012-06-10 11:43 ` Boaz Harrosh [this message]
2012-06-10 15:00 ` Kernel 3.4.X NFS server regression Myklebust, Trond
2012-06-11 12:16 ` bfields
2012-06-11 12:39 ` Jeff Layton
2012-06-11 13:13 ` Jeff Layton
2012-06-11 13:25 ` Jörg Platte
2012-06-11 14:20 ` Jeff Layton
2012-06-11 15:55 ` Joerg Platte
2012-06-11 13:32 ` Boaz Harrosh
2012-06-11 13:44 ` Boaz Harrosh
2012-06-11 14:29 ` Jeff Layton
2012-06-11 15:01 ` Boaz Harrosh
2012-06-11 15:15 ` bfields
2012-06-11 16:25 ` Boaz Harrosh
2012-06-11 13:51 ` Jeff Layton
2012-06-11 14:05 ` Boaz Harrosh
2012-06-11 14:11 ` Jeff Layton
2012-06-11 14:45 ` Boaz Harrosh
2012-06-11 14:55 ` Jeff Layton
2012-06-11 15:04 ` Boaz Harrosh
2012-06-11 14:03 ` [PATCH] rpc_pipefs: allow rpc_purge_list to take a NULL waitq pointer Jeff Layton
2012-06-15 15:24 ` Kernel 3.4.X NFS server regression Joerg Platte
2012-06-15 16:28 ` bfields
2012-06-15 17:19 ` Joerg Platte
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=4FD4887B.1050901@panasas.com \
--to=bharrosh@panasas.com \
--cc=jplatte@naasa.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).