[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080605070324.GB5757@kernel.dk>
Date: Thu, 5 Jun 2008 09:03:24 +0200
From: Jens Axboe <jens.axboe@...cle.com>
To: Tristan Linnenbank <tristan@...e.nl>
Cc: linux-kernel@...r.kernel.org
Subject: Re: file_splice_read problem in 2.6.24.2?
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists