1 |
On Tue, Sep 18, 2007 at 02:06:44PM +0200, Christian Parpart wrote: |
2 |
> Sep 11 20:05:11 jupjep ------------[ cut here ]------------ |
3 |
> Sep 11 20:05:11 jupjep kernel BUG at kernel/vserver/context.c:193! |
4 |
> Sep 11 20:05:11 jupjep invalid opcode: 0000 [1] SMP |
5 |
> Sep 11 20:05:11 jupjep CPU 2 |
6 |
> |
7 |
> just a moment later: |
8 |
> |
9 |
> Sep 11 20:10:01 jupjep ------------[ cut here ]------------ |
10 |
> Sep 11 20:10:01 jupjep kernel BUG at kernel/vserver/context.c:193! |
11 |
> Sep 11 20:10:01 jupjep invalid opcode: 0000 [2] SMP |
12 |
> Sep 11 20:10:01 jupjep CPU 3 |
13 |
|
14 |
> Sep 11 20:10:01 jupjep kernel BUG at kernel/vserver/context.c:193! |
15 |
> Sep 11 20:10:01 jupjep invalid opcode: 0000 [3] SMP |
16 |
> Sep 11 20:10:01 jupjep CPU 2 |
17 |
> |
18 |
> Sep 11 20:10:01 jupjep <0>------------[ cut here ]------------ |
19 |
> Sep 11 20:10:01 jupjep kernel BUG at kernel/vserver/context.c:193! |
20 |
> Sep 11 20:10:01 jupjep invalid opcode: 0000 [4] SMP |
21 |
> Sep 11 20:10:01 jupjep CPU 3 |
22 |
|
23 |
All of these are due to opcode 0000 being executed. This is a sign of |
24 |
something really weird going on. My guesses would be: |
25 |
|
26 |
1) Kernel image on disk has been corrupted. |
27 |
|
28 |
2) Memory is bad, possibly leading to the above. |
29 |
|
30 |
3) A bug in your kernel version is causing slab/kernel memory |
31 |
corruption. |
32 |
|
33 |
Someone else suggested code compiled with different |
34 |
optimizations/subarch. But I don't believe 0000 is ever a valid opcode |
35 |
on x86_64. I would make sure the kernel image is intact and run |
36 |
memtest86 as a first stab. |
37 |
|
38 |
Cheers, |
39 |
Dan |
40 |
|
41 |
-- |
42 |
/--------------- - - - - - - |
43 |
| Dan Noe |
44 |
| http://isomerica.net/~dpn/ |
45 |
-- |
46 |
gentoo-server@g.o mailing list |