xfs
[Top] [All Lists]

Re: BUG: soft lockup - is this XFS problem?

To: Guus Sliepen <Guus.Sliepen@xxxxxxxxxxx>, Nick Piggin <npiggin@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Roman Kononov <kernel@xxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Subject: Re: BUG: soft lockup - is this XFS problem?
From: Peter Klotz <peter.klotz99@xxxxxxxxx>
Date: Thu, 14 Jul 2011 20:03:09 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ViM7hCC4IlUkfM104VM5BzLt016VWpZvRwDp35iMsss=; b=dlH6Gc0AAplgIyUWhwY9GWu3ifhfbKVcjrMFP2VG37pCcYoGOLH1l6/aYZI+bozhRr QcjjILphaIMI2zgqm2RLg0mADAq7ytMh+KmIV7RldF85PznJ1JPXQ8BIhsI9YNNlYbTA kwQyzGo9T8rq+5QgY5k8Snhk3Cur5QENK4Xlg=
In-reply-to: <20110714112324.GM30145@xxxxxxxxxxx>
References: <20090105064838.GA5209@xxxxxxxxxxxxx> <20110714112324.GM30145@xxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
On 07/14/2011 01:23 PM, Guus Sliepen wrote:

I'm having a problem with a system having an XFS filesystem on RAID locking up
fairly consistently when writing large amounts of data to it, with several
kernels, including 2.6.38.2 and 2.6.39.3, on both AMD and Intel multi-core
processors. The kernel always logs this several times:

BUG: soft lockup - CPU#2 stuck for 67s! [kswapd0:33]
...
I believe this patch should solve it. Please test and confirm before
I send it upstream.

Further comments on that thread in 2009 indicated the patch was very useful,
but it doesn't seem to have been applied upstream. Is there any reason this
patch should not be applied?

Hello Guus

This Bugzilla entry documents the XFS bug from 2009 in detail including links:

http://oss.sgi.com/bugzilla/show_bug.cgi?id=805

The problem was finally solved by a patch proposed by Linus. This is the reason the original patch developed by Nick never made it into the kernel.

My tests back then showed that both patches fixed the problem.

It seems you have found a test case where just Nick's patch helps.

Regards, Peter.

<Prev in Thread] Current Thread [Next in Thread>