Slackware 12.0 on 64 MB
in [Slackware]
|
Prev: Web Cam
Next: sound problem in 12.1
From: Helmut Hullen on 1 Feb 2008 07:50 Hallo, Mark, Du meintest am 01.02.08: >> Memtest86+ Pass 17% ##### > ... >> WallTime 2:26:26 > It ran through the test cycle 3 times without showing an error, and > that's good, but 17% of the way through the 4th pass the machine > locked up. I see from the clock that it ran tests for 2 hours and 26 > minutes before locking. Lockups are not unknown with memtest, since > it is messing with the memory after all. "memtest" works in Video RAM; maybe there are bad cells. > The fact that no errors were detected is a good thing, No, not at all. One of my laptops sometimes hung up. Running "memtest" showed some errors after about 24 hours. Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Arun Dev on 1 Feb 2008 08:13 Hi all Am 01.02.2008 13:50, Helmut Hullen schrieb: > > Du meintest am 01.02.08: > >>> Memtest86+ Pass 17% ##### >> ... >>> WallTime 2:26:26 > >> It ran through the test cycle 3 times without showing an error, and >> that's good, but 17% of the way through the 4th pass the machine >> locked up. I see from the clock that it ran tests for 2 hours and 26 >> minutes before locking. Lockups are not unknown with memtest, since >> it is messing with the memory after all. > > "memtest" works in Video RAM; maybe there are bad cells. > >> The fact that no errors were detected is a good thing, > > No, not at all. In any case memtest was stuck (no reaction to Esc, c, etc.) That's not good ;-( I restarted memtest and it froze after 14 Sec.! Stole the RAM from another identical model, and memtest is running again. We'll see. Thanks for the support! Arun
From: Mark South on 1 Feb 2008 08:37 On Fri, 01 Feb 2008 13:50:00 +0100, Helmut Hullen wrote: >> It ran through the test cycle 3 times without showing an error, and >> that's good, but 17% of the way through the 4th pass the machine locked >> up. I see from the clock that it ran tests for 2 hours and 26 minutes >> before locking. Lockups are not unknown with memtest, since it is >> messing with the memory after all. > > "memtest" works in Video RAM; maybe there are bad cells. Good point. >> The fact that no errors were detected is a good thing, > > No, not at all. That's open to interpretation. It's a good thing as long as no errors are detected. That is not the same thing as saying that one can be certain there will be no errors. A man fell off a tall building. As he passed each floor on his way down, he said "So far, so good."
From: Arun Dev on 1 Feb 2008 10:25 Am 01.02.2008 14:13, Arun Dev schrieb: > > In any case memtest was stuck (no reaction to Esc, c, etc.) That's > not good ;-( > > I restarted memtest and it froze after 14 Sec.! > > Stole the RAM from another identical model, and memtest is running > again. We'll see. No use. memtest would freeze anything between 10 sec to couple of minutes. I give up. Thanks to everybody. Arun
From: ray on 1 Feb 2008 16:46
Arun Dev wrote: > Hi all > > Am 01.02.2008 13:50, Helmut Hullen schrieb: >> >> Du meintest am 01.02.08: >> >>>> Memtest86+ Pass 17% ##### >>> ... >>>> WallTime 2:26:26 >> >>> It ran through the test cycle 3 times without showing an error, and >>> that's good, but 17% of the way through the 4th pass the machine >>> locked up. I see from the clock that it ran tests for 2 hours and 26 >>> minutes before locking. Lockups are not unknown with memtest, since >>> it is messing with the memory after all. >> >> "memtest" works in Video RAM; maybe there are bad cells. >> >>> The fact that no errors were detected is a good thing, >> >> No, not at all. > > In any case memtest was stuck (no reaction to Esc, c, etc.) That's > not good ;-( > > I restarted memtest and it froze after 14 Sec.! > > Stole the RAM from another identical model, and memtest is running > again. We'll see. > > Thanks for the support! > > Arun For me, a machine needs to be able to run memtest/some other benchmark for 72 hours before I consider it stable. Ray |