| 1 |
Raymond Lewis Rebbeck wrote: |
| 2 |
> On Thursday, 30 November 2006 16:16, Vladimir G. Ivanovic wrote: |
| 3 |
>> Etaoin Shrdlu wrote: |
| 4 |
>>> On Thursday 23 November 2006 14:39, Leandro Melo de Sales wrote: |
| 5 |
>>>> The bug is not reproducible, so it is likely a hardware or OS problem. |
| 6 |
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 7 |
>>> |
| 8 |
>>> As the message says, you might have a hardware problem (usually bad RAM |
| 9 |
>>> or CPU). |
| 10 |
>> My experience has been that it NEVER is a hardware problem. The next |
| 11 |
>> emerge of the same package always completes successfully. |
| 12 |
>> |
| 13 |
> |
| 14 |
> That behaviour usually indicates a hardware problem. Random unexplainable |
| 15 |
> segfaults that you can't reproduce. |
| 16 |
|
| 17 |
Let's take a poll. |
| 18 |
|
| 19 |
1. Have you seen this error message in an emerge? |
| 20 |
2. Have you subsequently identified a hardware problem, fixed the |
| 21 |
hardware problem, and have not seen the message since? |
| 22 |
3. Have you re-run the emerge and not seen the message in a while |
| 23 |
(please indicate how long "a while" is.) |
| 24 |
|
| 25 |
For me, the answers are: |
| 26 |
1. Yes |
| 27 |
2. No |
| 28 |
3. Yes (~months) |
| 29 |
|
| 30 |
BTW, do you know portage/emerge/make/whatever knows that the problem |
| 31 |
is not reproducible? |
| 32 |
|
| 33 |
--- Vladimir |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives