Richard Fish wrote:
On 11/30/06, Vladimir G. Ivanovic <[EMAIL PROTECTED]> wrote:
I have done nothing to my hardware and I've seen this error, oh, a
half a dozen times, the last time 3 months (?) ago. I ran memtest when
I installed new memory, and it did not report problems even when run
for hour
On 11/30/06, Vladimir G. Ivanovic <[EMAIL PROTECTED]> wrote:
I have done nothing to my hardware and I've seen this error, oh, a
half a dozen times, the last time 3 months (?) ago. I ran memtest when
I installed new memory, and it did not report problems even when run
for hours.
memtest is basic
Etaoin Shrdlu wrote:
On Thursday 30 November 2006 07:56, Vladimir G. Ivanovic wrote:
Let's take a poll.
1. Have you seen this error message in an emerge?
Yes, several times.
2. Have you subsequently identified a hardware problem, fixed the
hardware problem, and have not seen the messag
On Thursday 30 November 2006 09:02, Etaoin Shrdlu wrote:
> On Thursday 30 November 2006 07:56, Vladimir G. Ivanovic wrote:
> > Let's take a poll.
> >
> > 1. Have you seen this error message in an emerge?
>
> Yes, several times.
Ditto.
> > 2. Have you subsequently identified a hardware problem, fi
On 11/29/06, Vladimir G. Ivanovic <[EMAIL PROTECTED]> wrote:
1. Have you seen this error message in an emerge?
Yes.
2. Have you subsequently identified a hardware problem, fixed the
hardware problem, and have not seen the message since?
Yes. The problem was memory timings...or more spe
On Thursday 30 November 2006 07:56, Vladimir G. Ivanovic wrote:
> Let's take a poll.
>
> 1. Have you seen this error message in an emerge?
Yes, several times.
> 2. Have you subsequently identified a hardware problem, fixed the
> hardware problem, and have not seen the message since?
Yes. 99
Raymond Lewis Rebbeck wrote:
On Thursday, 30 November 2006 16:16, Vladimir G. Ivanovic wrote:
Etaoin Shrdlu wrote:
On Thursday 23 November 2006 14:39, Leandro Melo de Sales wrote:
The bug is not reproducible, so it is likely a hardware or OS problem.
^^^
On Thursday, 30 November 2006 16:16, Vladimir G. Ivanovic wrote:
> Etaoin Shrdlu wrote:
> > On Thursday 23 November 2006 14:39, Leandro Melo de Sales wrote:
> >> The bug is not reproducible, so it is likely a hardware or OS problem.
> >
> >^^^
Etaoin Shrdlu wrote:
On Thursday 23 November 2006 14:39, Leandro Melo de Sales wrote:
The bug is not reproducible, so it is likely a hardware or OS problem.
^
As the message says, you might have a hardware problem (usually
Thank you, I'll read it.
[]s
Leandro
2006/11/23, Etaoin Shrdlu <[EMAIL PROTECTED]>:
On Thursday 23 November 2006 14:39, Leandro Melo de Sales wrote:
> Hi,
>
> I'm trying to compile GCC 4.1.1-r1 but I got the following error
> message:
>[cut]
> 'main': /var/tmp/portage/gcc-4.1.1-r1/work/gcc-4.
On Thursday 23 November 2006 14:39, Leandro Melo de Sales wrote:
> Hi,
>
> I'm trying to compile GCC 4.1.1-r1 but I got the following error
> message:
>[cut]
> 'main': /var/tmp/portage/gcc-4.1.1-r1/work/gcc-4.1.1/gcc/gcc.c:8043:
> internal compiler error: Segmentation fault
> Please submit a full
11 matches
Mail list logo