Date: Tue, 29 May 2007 14:53:12 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Alex Dupre <ale@FreeBSD.org> Cc: freebsd-hackers@freebsd.org, Ali Mashtizadeh <mashtizadeh@gmail.com>, freebsd-current@freebsd.org Subject: Re: Xorg port problem? Message-ID: <465CA0C8.6020706@FreeBSD.org> In-Reply-To: <465BD7F5.8030109@FreeBSD.org> References: <440b3e930705282241u44fa03a8gb0fedbb1617518df@mail.gmail.com> <465BC3A4.7030008@FreeBSD.org> <465BC507.1060902@FreeBSD.org> <465BD140.20504@FreeBSD.org> <465BD7F5.8030109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Dupre wrote:
> Doug Barton ha scritto:
>> Not disputing your answer, but I'm curious. Why would it cause
>> problems on some systems but not others? I haven't done anything with
>> my cflags ...
>
> It depends on how much RAM + Swap do you have. I know people with 1.5Gb
> that have such problem and others with 2.5Gb that haven't it (if I
> remember correctly the amounts). The "bug" is the un-optimized
> optimization :-) There is already a patch that will be included in 4.2.1
> release, but I hope will be backported before in FreeBSD gcc.
Ok, this makes sense. I was interested in the original post because I
also have 2G of ram, and very little swap configured, so it looked to
me like the only variable was that he had ZFS and I didn't.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465CA0C8.6020706>