xfs
[Top] [All Lists]

Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4

To: Jan Kara <jack@xxxxxxx>
Subject: Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4
From: Alessandro Bono <alessandro.bono@xxxxxxxxx>
Date: Wed, 11 Mar 2009 18:04:06 +0100
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs <linux-xfs@xxxxxxxxxxx>, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=Axffz7T/fCJI4879QEKJjPY+Wgbtdu+MxyaVMIdgbco=; b=Zwa4cCG37Orc/+Vk/PFJ3h2CZBl5X1rkqT97n/WXDX/EGnzLWMJjxZf9bCuQpRI2+x 1xBIxLXt4Y+mLqLHDKYZsrnJADM9cE3OQF7l0zD8NL5lF7ora5E79WwI59veR+7IKrXT 4Z7T2f8v6gs9P6PAUJnfg0f1l7BSW9hvVN3u8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=T/M5zgWMsbO7wcZNTRCk2+aJlUOSJr2u06KlOJZkI3jtl+ZWKcleJ1QzwZdgbxVyEF oFUL1gT0YRYMDYmfJLeHNkadR1ZANYh3vCWIbgZLJV1iztow9gAdhCBBKhgxPUZYyVQR AOMj+bn1XR+V1NqpK7ik14iElU1HuN3c6642k=
In-reply-to: <20090302133609.GD23880@xxxxxxxxxxxx>
References: <1234011974.7435.11.camel@xxxxxxxxxxxxxxxxx> <20090208222859.GA2532@xxxxxxxxxxxxx> <1234132752.12370.0.camel@xxxxxxxxxxxxxxxxx> <20090208224249.GA11931@xxxxxxxxxxxxx> <1234133120.12370.7.camel@xxxxxxxxxxxxxxxxx> <20090209075308.GA7360@xxxxxxxxxxxxx> <20090210104304.GP8830@disturbed> <1234432077.9204.15.camel@xxxxxxxxxxxxxxxxx> <20090226165838.GA9602@xxxxxxxxxxxxxxxxxxxxxxxx> <1235763895.5743.3.camel@champagne> <20090302133609.GD23880@xxxxxxxxxxxx>
On Mon, 2009-03-02 at 14:36 +0100, Jan Kara wrote:
.....

>   Such bit flips are usually caused by faulty memory or other HW (io
> controler etc.) so I suggest trying to shuffle the hardware somehow -
> change memory DIMMs as a starter, running memtest if you don't have a spare
> DIMMs but it is not an exception that even though memtest runs just fine
> for a long time, memory is really at fault.

Hi

I changed DIMMs on my laptop and after that I can't reproduce bug
So at the end it's an hardware problem

Many thanks to you, Dave and Christoph for your time and patience 

-- 
Cordiali Saluti
Alessandro Bono

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