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, fixed the > > hardware problem, and have not seen the message since? > > Yes. 99% of the times it was bad RAM (verified with memtest86). > Of course, for trivial emerges a subsequent emerge completed fine, but > the first failure put me on the alert. Yes, it was a bad/incompatible RAM module for the particular memory controller. memetest86 did not identify it, I found out by trial and error! The symptom was random crashes (mostly) during emerge which would complete fine after a hard reboot. The crashes would invariably happen either when the memory controller was switching onto the next memory module, or when both modules were used up and it started using swap. > > 3. Have you re-run the emerge and not seen the message in a while > > (please indicate how long "a while" is.) > > For me, "a while" is "since fixing the hardware problem". Ditto, i.e. about 18 months so far. HTH. -- Regards, Mick
pgpy2Wqda1NFT.pgp
Description: PGP signature
