On Tue, Sep 18, 2007 at 02:06:44PM +0200, Christian Parpart wrote:
> Sep 11 20:05:11 jupjep ------------[ cut here ]------------
> Sep 11 20:05:11 jupjep kernel BUG at kernel/vserver/context.c:193!
> Sep 11 20:05:11 jupjep invalid opcode: 0000 [1] SMP
> Sep 11 20:05:11 jupjep CPU 2
>
> just a moment later:
>
> Sep 11 20:10:01 jupjep ------------[ cut here ]------------
> Sep 11 20:10:01 jupjep kernel BUG at kernel/vserver/context.c:193!
> Sep 11 20:10:01 jupjep invalid opcode: 0000 [2] SMP
> Sep 11 20:10:01 jupjep CPU 3
> Sep 11 20:10:01 jupjep kernel BUG at kernel/vserver/context.c:193!
> Sep 11 20:10:01 jupjep invalid opcode: 0000 [3] SMP
> Sep 11 20:10:01 jupjep CPU 2
>
> Sep 11 20:10:01 jupjep <0>------------[ cut here ]------------
> Sep 11 20:10:01 jupjep kernel BUG at kernel/vserver/context.c:193!
> Sep 11 20:10:01 jupjep invalid opcode: 0000 [4] SMP
> Sep 11 20:10:01 jupjep CPU 3
All of these are due to opcode 0000 being executed. This is a sign of
something really weird going on. My guesses would be:
1) Kernel image on disk has been corrupted.
2) Memory is bad, possibly leading to the above.
3) A bug in your kernel version is causing slab/kernel memory
corruption.
Someone else suggested code compiled with different
optimizations/subarch. But I don't believe 0000 is ever a valid opcode
on x86_64. I would make sure the kernel image is intact and run
memtest86 as a first stab.
Cheers,
Dan
--
/--------------- - - - - - -
| Dan Noe
| http://isomerica.net/~dpn/
--
[EMAIL PROTECTED] mailing list
