From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@sandeen.net>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.33 crash: invalid opcode: 0000 [#1] SMP: EIP: [<c11a018b>] assfail+0x1b/0x20 SS:ESP 0068:f687bf14
Date: Mon, 15 Mar 2010 11:21:42 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1003151112330.22155@p34.internal.lan> (raw)
In-Reply-To: <20100315151136.GA1401@infradead.org>
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:
Hello,
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):
http://lists.openwall.net/linux-kernel/2009/10/19/118
Justin.
prev parent reply other threads:[~2010-03-15 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 9:32 Justin Piszcz
2010-03-15 14:40 ` Eric Sandeen
2010-03-15 14:44 ` Justin Piszcz
2010-03-15 14:46 ` Eric Sandeen
2010-03-15 15:11 ` Christoph Hellwig
2010-03-15 15:21 ` Justin Piszcz [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=alpine.DEB.2.00.1003151112330.22155@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®