From: Mike Galbraith <efault@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: regression: nfs mount (even idle) eventually hangs server
Date: Thu, 22 Dec 2022 04:42:26 +0100 [thread overview]
Message-ID: <241c118c2fb60df744bbe351387fc29a34ff6ab9.camel@gmx.de> (raw)
In-Reply-To: <360f3dcfb6cfbefdbcc42fc84c660995142a8645.camel@gmx.de>
On Wed, 2022-12-21 at 10:56 +0100, Mike Galbraith wrote:
> > 6.1 didn't reproduce either, so it would appear to be a merge window bug.
Ah, not true, turning evolution loose in nfs mounted home and letting
it refresh mailboxes while desktop box was kept busy jammed up 6.1.0 in
fairly short order.
homer:..debug/tracing # grep WARNING: /netconsole.log2
[ 3309.873094] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1655 __queue_delayed_work+0x6a/0x90
[ 3309.873446] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1657 __queue_delayed_work+0x5a/0x90
[ 3309.873780] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.874120] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.874452] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.874783] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.875099] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.875426] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.875745] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.876064] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 3309.876383] WARNING: CPU: 1 PID: 78 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
Sigh. Ok 6.0, batter up...
-Mike
next prev parent reply other threads:[~2022-12-22 3:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65ed34338c69cb034295f2c9cbe0af684d65d30f.camel@gmx.de>
2022-12-21 9:56 ` regression: nfs mount (even idle) eventually hangs server Mike Galbraith
2022-12-22 3:42 ` Mike Galbraith [this message]
2022-12-22 4:14 ` Mike Galbraith
2022-12-22 4:28 ` Chuck Lever III
2022-12-22 4:44 ` Mike Galbraith
2022-12-22 13:30 ` Mike Galbraith
2022-12-22 14:21 ` Chuck Lever III
2022-12-23 4:41 ` Mike Galbraith
2022-12-23 6:28 ` Mike Galbraith
2022-12-23 12:02 ` dai.ngo
2022-12-23 13:05 ` Mike Galbraith
2023-01-09 0:50 ` dai.ngo
2023-01-09 2:41 ` Mike Galbraith
2023-01-09 6:34 ` dai.ngo
2023-01-05 14:14 ` summary: " Mike Galbraith
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=241c118c2fb60df744bbe351387fc29a34ff6ab9.camel@gmx.de \
--to=efault@gmx.de \
--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