[Top] [All Lists]

Re: 2.6.33 crash: invalid opcode: 0000 [#1] SMP: EIP: [<c11a018b>] assfa

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: 2.6.33 crash: invalid opcode: 0000 [#1] SMP: EIP: [<c11a018b>] assfail+0x1b/0x20 SS:ESP 0068:f687bf14
From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Mon, 15 Mar 2010 11:21:42 -0400 (EDT)
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20100315151136.GA1401@xxxxxxxxxxxxx>
References: <alpine.DEB.2.00.1003150528060.6999@xxxxxxxxxxxxxxxx> <4B9E46F9.8090209@xxxxxxxxxxx> <alpine.DEB.2.00.1003151042390.9496@xxxxxxxxxxxxxxxx> <4B9E4863.80905@xxxxxxxxxxx> <20100315151136.GA1401@xxxxxxxxxxxxx>
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)

On Mon, 15 Mar 2010, Christoph Hellwig wrote:

On Mon, Mar 15, 2010 at 09:46:59AM -0500, Eric Sandeen wrote:
Ok, then you hit an ASSERT_ALWAYS

There are only a few:

If the box is a nfs server I suspect it's a reclaimable state one and
the patch below should help:


The host is not running an NFS server actively, the option may be compiled in but it is not 'acting' as an NFS server/has shares exported. I
need stability for this specific host, I cannot run netconsole due to
restrictions etc/will switch to ext4 since, if it recurs again, all I/O to the disk stops and I will not be able to assist in reporting the bug/giving the full output. If I could reproduce the bug in another environment, I would be able to troubleshoot the problem more.. This bug is very similar to the one I reported in the past (that host was an active NFS server):


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