Re: 2.6.33 crash: invalid opcode: 0000 [#1] SMP: EIP: [<c11a018b>]assfail+0x1b/0x20 SS:ESP 0068:f687bf14

[Eric Sandeen]

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?

You hit an assertion failure in xfs.

Are you running with CONFIG_XFS_DEBUG?

-Eric

> Justin.
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/