On Tuesday 13 September 2005 15:52, Daniel Drake wrote:
Frank Schafer wrote:
Does someone know if it's worth a try with the vanilla and if vanilla
here means a really vanilla from kernel.org or if it's sufficient to
get the (too patched and thus not so vanilla) vanilla-sources.
Hello,
this bug is from 2005-02-05. It was reported again (in this thread)
2005-02-10. I hit the same behavior 2005-09-08.
internal compiler error: segmentation fault during emerge Xorg
The bug is simply reproducible (emerge Xorg) at the same line of code.
The bug is still marked as NEW.
On Tue, Sep 13, 2005 at 03:24:38PM +0200, Frank Schafer wrote:
Hello,
this bug is from 2005-02-05. It was reported again (in this thread)
2005-02-10. I hit the same behavior 2005-09-08.
internal compiler error: segmentation fault during emerge Xorg
The bug is simply reproducible (emerge
Frank Schafer wrote:
Does someone know if it's worth a try with the vanilla and if vanilla
here means a really vanilla from kernel.org or if it's sufficient to get
the (too patched and thus not so vanilla) vanilla-sources.
vanilla-sources is not patched.
Please be kind with me regarding to
On Tue, 2005-09-13 at 14:52 +0100, Daniel Drake wrote:
are running vesafb-tng and have =1GB RAM then try
turning off vesafb-tng
Why ?
--
Cheers,
Ivan Yosifov.
--
gentoo-dev@gentoo.org mailing list
Ivan Yosifov wrote:
On Tue, 2005-09-13 at 14:52 +0100, Daniel Drake wrote:
are running vesafb-tng and have =1GB RAM then try
turning off vesafb-tng
Why ?
Actually, this shouldn't matter, as this only occurs with 64gb highmem. I only
mentioned it as this is the only random crasher
On Tue, 2005-09-13 at 17:01 +0300, Ivan Yosifov wrote:
On Tue, 2005-09-13 at 14:52 +0100, Daniel Drake wrote:
are running vesafb-tng and have =1GB RAM then try
turning off vesafb-tng
Why ?
Because of known bugs I'd guess?
--
Stand still, and let the rest of the universe move
On Tue, 2005-09-13 at 15:14 +0100, Daniel Drake wrote:
Ivan Yosifov wrote:
On Tue, 2005-09-13 at 14:52 +0100, Daniel Drake wrote:
are running vesafb-tng and have =1GB RAM then try
turning off vesafb-tng
Why ?
Actually, this shouldn't matter, as this only occurs with 64gb
Frank Schafer wrote:
I'm still on the kernel from the life-cd. The self compiled kernel has
the highmem option set to off (I have only 1GB). I'm on x86 Intel
Celeron M and have CHOST set to i686-pc-linux-gnu and CFLAGS=-O2
-march=pentium2
Um, why pentium2? The Celeron-M is the same core
