From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: 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 10:44:30 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1003151042390.9496@p34.internal.lan> (raw)
In-Reply-To: <4B9E46F9.8090209@sandeen.net>
On Mon, 15 Mar 2010, Eric Sandeen wrote:
> Justin Piszcz wrote:
>> Specifications:
>>
>> 2.6.33
>> 32bit
>> Debian Testing
>>
>> On Mar 14th, my server hung up:
>>
>> Mar 14 00:00:22 server1 kernel: [488470.189675] ------------[ cut here
>> ]------------
>> Mar 14 00:00:22 server1 kernel: [488470.189679] invalid opcode: 0000
>> [#1] SMP
>> Mar 14 00:00:22 server1 kernel: [488470.189681] last sysfs file:
>> /sys/devices/pci0000:00/0000:00:0e.0/host0/target0:0:0/0:0:0:0/block/sda/uevent
>>
>> Mar 14 00:00:22 server1 kernel: [488470.189704] Process xfssyncd (pid:
>> 584, ti=f687a000 task=f70fa400 task.ti=f687a000)
>> Mar 14 00:00:22 server1 kernel: [488470.189705] Stack:
>> Mar 14 00:00:22 server1 kernel: [488470.189721] Call Trace:
>> Mar 14 00:00:22 server1 kernel: [488470.189739] Code: 00 e8 ea e5 01 00
>> 83 c4 14 c3 8d b6 00 00 00 00 83 ec 10 89 4c 24 0c 89 54 24 08 89 44 24
>> 04 c7 04 24 30 ab 42 c1 e8 7c 11 1c 00 <0f> 0b eb fe 90 55 57 89 cf 56
>> 89 c6 b8 80 b0 52 c1 83 e6 07 53
>> Mar 14 00:00:22 server1 kernel: [488470.189739] EIP: [<c11a018b>]
>> assfail+0x1b/0x20 SS:ESP 0068:f687bf14
>>
>> Is this a bug related to AMD (CPU) or XFS?
>
> Hard to know without seeing the rest of the stack trace, is this all you got?
Yes, that was the only entry in the log file, I could not wake up the
monitor to get any more information.
>
> You hit an assertion failure in xfs.
>
> Are you running with CONFIG_XFS_DEBUG?
Nope.
CONFIG_XFS_FS=y
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG is not set
>
> -Eric
>
next prev parent reply other threads:[~2010-03-15 14:44 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 [this message]
2010-03-15 14:46 ` Eric Sandeen
2010-03-15 15:11 ` Christoph Hellwig
2010-03-15 15:21 ` Justin Piszcz
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.1003151042390.9496@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--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®