| 1 |
it's worth noting that a failing power supply can produce what seem to be ram problems. it happened to me, swapping ram, a motherboard and then a power supply made it clear. |
| 2 |
|
| 3 |
-- |
| 4 |
Note the right side (his right) of Mr. Trumps face, He's clearly had a major stroke or similar neurological insult. The eye always droops, and that side of his mouth hardly moves when he speaks. I try not to throw stones from inside my glass house, others obviously don't mind hypocrisy. |
| 5 |
|
| 6 |
|
| 7 |
8. Oct 2017 18:14 by r030t1@×××××.com: |
| 8 |
|
| 9 |
|
| 10 |
> On Sun, Oct 8, 2017 at 4:53 PM, Grant Edwards <> grant.b.edwards@×××××.com> > wrote: |
| 11 |
>> On 2017-10-08, R0b0t1 <>> r030t1@×××××.com>> > wrote: |
| 12 |
>> |
| 13 |
>>> Usually what happens is it will be corrupted in RAM after being |
| 14 |
>>> verified on disk, and faulty results will be saved to disk from RAM. A |
| 15 |
>>> user on the forums recently had this issue compiling dev-lang/vala, |
| 16 |
>>> and I have had related issues. |
| 17 |
>> |
| 18 |
>> I've had failing RAM corrupt files and cause compile failures (and |
| 19 |
>> various other odd problems). But, the exact symptoms tend to be pretty |
| 20 |
>> random. The chances are infinitesmal that a HW problem would corrupt |
| 21 |
>> the download (or the compile itself) in an identical manner a second |
| 22 |
>> time. |
| 23 |
>> |
| 24 |
> |
| 25 |
> Right, redownloading or rerunning the compilation usually fixes such |
| 26 |
> issues. At the same time, I have seen people hit bad areas of RAM |
| 27 |
> repeatedly and have it look like other errors. |
| 28 |
> --------------------------snip |
| 29 |
> Cheers, |
| 30 |
> R0b0t1 |
Archives