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: [1] SMP
> Sep 11 20:05:11 jupjep CPU 2
>
> just a mome
On Tuesday 18 September 2007, Christian Parpart wrote:
> Sep 11 20:05:11 jupjep invalid opcode: [1] SMP
Invalid opcode!??! This might indicate the kernel/system running were
compiled with optimizations for a different CPU.
Once you've satisfied yourself that the above isn't the case I'd su
On Tue, September 18, 2007 14:06, Christian Parpart wrote:
> well, hard to explain, but recently I encounter *lots* of crashes on
> one mashine serving via vserver-sources with about 3-5 VEs.
>
> The physical server itself is a 10k IBM amd64 host with 2 dual cores
> and 16GB RAM, raid10 SATA, just
Hi all,
well, hard to explain, but recently I encounter *lots* of crashes on
one mashine serving via vserver-sources with about 3-5 VEs.
The physical server itself is a 10k IBM amd64 host with 2 dual cores
and 16GB RAM, raid10 SATA, just if you want to know.
However, this is what I found in th
gentoo-server
--
[EMAIL PROTECTED] mailing list
