Linux NFS development
 help / color / mirror / Atom feed
From: Gertjan Oude Lohuis <gertjan-DW70C6hi67U@public.gmane.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Allard Hoeve <allard-DW70C6hi67U@public.gmane.org>,
	linux-nfs@vger.kernel.org, "Nilssen,
	Rune" <rune.nilssen-FJFKJQU35qU@public.gmane.org>
Subject: Re: Kernel 2.6.23.17 crash (Was: Kernel (2.6.24) crash on nfsd  (BUG: soft lockup))
Date: Wed, 05 Mar 2008 11:25:33 +0100	[thread overview]
Message-ID: <47CE751D.4090301@byte.nl> (raw)
In-Reply-To: <20080301170322.GY6704@kernel.dk>

Hi Jens et al,

On 03/01/2008 06:03 PM, Jens Axboe wrote:
> On Sat, Mar 01 2008, J. Bruce Fields wrote:
>> So, the summary: several people are reporting soft lockup warnings with
>> _generic_file_splice_read as the latest or next-to-latest function on
>> the stack.  Sounds like 2.6.18 is good, various kernels around 2.6.23
>> and 2.6.24 are reported bad.  Is it possible this was a regression
>> introduced by the splice changes?
> 
> I posted this two days ago, but didn't get a reply back regarding if
> anyone who can reproduce tested it?
> 
> diff --git a/fs/splice.c b/fs/splice.c

<snip patch>

I'm sorry we didn't respond any earlier. We've been quite busy dividing 
our data over multiple fileservers to lower the load on the primary 
server, and in the process we downgraded the kernels on the NFS-servers 
to 2.6.22.19.
Since then we haven't seen another crash. My gut feeling says that the 
downgraded kernels were the 'solution', but it could also be that the 
lowered load has prevented the servers from crashing.

At the moment we won't be able to test your patch, simply because we 
can't afford any more crashes. However, if 2.6.22.19 does crash in the 
same way in the near future, I'll try your patch.

Thanks for your interest and help!

Regards,
Gertjan Oude Lohuis

  reply	other threads:[~2008-03-05 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 15:48 Kernel (2.6.24) crash on nfsd (BUG: soft lockup) Gertjan Oude Lohuis
     [not found] ` <47C434D2.80601-DW70C6hi67U@public.gmane.org>
2008-02-27  6:46   ` Gertjan Oude Lohuis
     [not found]     ` <47C50754.5030107-DW70C6hi67U@public.gmane.org>
2008-02-27  7:01       ` Gertjan Oude Lohuis
     [not found]         ` <47C50ABB.8050700-DW70C6hi67U@public.gmane.org>
2008-02-28 10:56           ` Kernel 2.6.23.17 crash (Was: Kernel (2.6.24) crash on nfsd (BUG: soft lockup)) Allard Hoeve
     [not found]             ` <Pine.LNX.4.62.0802281153040.31013-FHjt3+7qfYHBZBx2VKNGNcSTQT6m/s+e@public.gmane.org>
2008-03-01 16:39               ` J. Bruce Fields
2008-03-01 17:03                 ` Jens Axboe
2008-03-05 10:25                   ` Gertjan Oude Lohuis [this message]
2008-02-28 11:08   ` Kernel (2.6.24) crash on nfsd (BUG: soft lockup) Gertjan Oude Lohuis

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=47CE751D.4090301@byte.nl \
    --to=gertjan-dw70c6hi67u@public.gmane.org \
    --cc=allard-DW70C6hi67U@public.gmane.org \
    --cc=bfields@fieldses.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rune.nilssen-FJFKJQU35qU@public.gmane.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