public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Tristan Linnenbank <tristan@byte.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file_splice_read problem in 2.6.24.2?
Date: Thu, 5 Jun 2008 09:03:24 +0200	[thread overview]
Message-ID: <20080605070324.GB5757@kernel.dk> (raw)
In-Reply-To: <48478EB5.9020207@byte.nl>

On Thu, Jun 05 2008, Tristan Linnenbank wrote:
> Jens Axboe wrote:
> >So either this is fixed by this:
> >
> >http://git.kernel.dk/?p=linux-2.6.git;a=commit;h=8191ecd1d14c6914c660dfa007154860a7908857
> >
> >or it's a different bug. You should post the full oops (including any
> >message that came before the oops, like the 'locked up for foo seconds'
> >in the urls you reference above) with the Code line at the bottom as
> >well so we can see what the registers are used for.
> >
> >If it's the bug fixed with the above commit, then 2.6.25.x should
> >work. Unfortunately I'm unsure of the -stable status of the above
> >patch.
> >
> thanks for your reply.
> 
> I appended five of the bunch of errors to this mail. They all lock the 
> CPU for 11 seconds (just like the nfsd errors we had in February/April), 
> so that could be a sign of them being the same bug.
> 
> It seems to be the same problem. We've only seen this behaviour once on 
> the one machine though. I'll keep a couple of webservers on 2.6.24.2 and 
> some on 2.6.25.4, just to see what happens.
> 
> Thanks!
> 
> Kind regards,
> 
> Tristan
> 
> Jun  4 15:08:38 web10.c1.internal kernel: BUG: soft lockup - CPU#0 stuck 
> for 11s! [apache2:22361]

Yep, that looks like the same 'spinning in splice read' problem, so
the 2.6.25 kernel should work fine.

-- 
Jens Axboe


      reply	other threads:[~2008-06-05  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 14:48 file_splice_read problem in 2.6.24.2? Tristan Linnenbank
2008-06-04 16:36 ` Jens Axboe
2008-06-05  6:59   ` Tristan Linnenbank
2008-06-05  7:03     ` Jens Axboe [this message]

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=20080605070324.GB5757@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tristan@byte.nl \
    /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