* [gentoo-user] [OT] Disable memory @ 2005-11-13 22:11 Peper 2005-11-13 22:34 ` Dale 2005-11-14 0:45 ` [gentoo-user] " Urs Schuetz 0 siblings, 2 replies; 8+ messages in thread From: Peper @ 2005-11-13 22:11 UTC (permalink / raw To: gentoo-user Hello, Is there anyway to disable specific part of memory? memtest86 freezes only when egzamining first MB of it. -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] [OT] Disable memory 2005-11-13 22:11 [gentoo-user] [OT] Disable memory Peper @ 2005-11-13 22:34 ` Dale 2005-11-13 22:57 ` [gentoo-user] " Peper 2005-11-14 0:45 ` [gentoo-user] " Urs Schuetz 1 sibling, 1 reply; 8+ messages in thread From: Dale @ 2005-11-13 22:34 UTC (permalink / raw To: gentoo-user Peper wrote: >Hello, >Is there anyway to disable specific part of memory? memtest86 freezes only >when egzamining first MB of it. > > > LOL. Could it be bad you think?? If you have two sticks of ram, swap them around and see if it fails somewhere else then. If it does, bad ram, if not, memtest has a bug. I'm not sure how to make it not test it all though. I have also never had it lock up. I have tested some really old rigs as well as some new ones. Dale :-) -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: [OT] Disable memory 2005-11-13 22:34 ` Dale @ 2005-11-13 22:57 ` Peper 2005-11-13 23:10 ` Hemmann, Volker Armin 2005-11-14 0:23 ` b.n. 0 siblings, 2 replies; 8+ messages in thread From: Peper @ 2005-11-13 22:57 UTC (permalink / raw To: gentoo-user > LOL. Could it be bad you think?? If you have two sticks of ram, swap > them around and see if it fails somewhere else then. If it does, bad > ram, if not, memtest has a bug. > I'm not sure how to make it not test it all though. I have also never > had it lock up. I have tested some really old rigs as well as some new > ones. I think you have misunedstood me. My memory is bad for sure, beacause my PC freezes between-whiles. Memtest does the same during test 5(block move) when egamining 1st MB of it(you can set which part of memory you want to check). And my questions is, how can i disable this first MB from being used by system? I was thinking of setting ramfs in this 1st MB and then not using it, but is it possible? -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: [OT] Disable memory 2005-11-13 22:57 ` [gentoo-user] " Peper @ 2005-11-13 23:10 ` Hemmann, Volker Armin 2005-11-14 0:23 ` b.n. 1 sibling, 0 replies; 8+ messages in thread From: Hemmann, Volker Armin @ 2005-11-13 23:10 UTC (permalink / raw To: gentoo-user On Sunday 13 November 2005 23:57, Peper wrote: > > LOL. Could it be bad you think?? If you have two sticks of ram, swap > > them around and see if it fails somewhere else then. If it does, bad > > ram, if not, memtest has a bug. > > I'm not sure how to make it not test it all though. I have also never > > had it lock up. I have tested some really old rigs as well as some new > > ones. > > I think you have misunedstood me. My memory is bad for sure, beacause my PC > freezes between-whiles. Memtest does the same during test 5(block move) > when egamining 1st MB of it(you can set which part of memory you want to > check). And my questions is, how can i disable this first MB from being > used by system? I was thinking of setting ramfs in this 1st MB and then not > using it, but is it possible? > no You could switch the ram sticks if you have several and disable everything above a certain size, but when the error is in the first mb, you could also just throw it away. Ram is cheap at the moment, get new one or RMA the old. Since memtest does not find a lot of errors, there is a big chance, that even more of the ram is defective, you should spare you the trouble. -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: [OT] Disable memory 2005-11-13 22:57 ` [gentoo-user] " Peper 2005-11-13 23:10 ` Hemmann, Volker Armin @ 2005-11-14 0:23 ` b.n. 2005-11-13 23:27 ` Peper 1 sibling, 1 reply; 8+ messages in thread From: b.n. @ 2005-11-14 0:23 UTC (permalink / raw To: gentoo-user > I think you have misunedstood me. My memory is bad for sure, beacause my PC > freezes between-whiles. Memtest does the same during test 5(block move) when > egamining 1st MB of it(you can set which part of memory you want to check). > And my questions is, how can i disable this first MB from being used by > system? I was thinking of setting ramfs in this 1st MB and then not using it, > but is it possible? > Try to check this: http://rick.vanrein.org/linux/badram/ m. -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: [OT] Disable memory 2005-11-14 0:23 ` b.n. @ 2005-11-13 23:27 ` Peper 0 siblings, 0 replies; 8+ messages in thread From: Peper @ 2005-11-13 23:27 UTC (permalink / raw To: gentoo-user > Try to check this: > http://rick.vanrein.org/linux/badram/ I'll give it a try. Thanks! -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] [OT] Disable memory 2005-11-13 22:11 [gentoo-user] [OT] Disable memory Peper 2005-11-13 22:34 ` Dale @ 2005-11-14 0:45 ` Urs Schuetz 2005-11-14 15:10 ` [gentoo-user] " Peper 1 sibling, 1 reply; 8+ messages in thread From: Urs Schuetz @ 2005-11-14 0:45 UTC (permalink / raw To: gentoo-user On Sun, 13 Nov 2005, Peper wrote: > Hello, > Is there anyway to disable specific part of memory? memtest86 > freezes only when egzamining first MB of it. As a boot option for the kernel (e.g. /etc/lilo.conf): append="mem=exactmap mem=640k@0 247M@1M 8M@248M" Somehing like this worked with older kernels, don't know how to do it with 2.6 kernels. Urs -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: [OT] Disable memory 2005-11-14 0:45 ` [gentoo-user] " Urs Schuetz @ 2005-11-14 15:10 ` Peper 0 siblings, 0 replies; 8+ messages in thread From: Peper @ 2005-11-14 15:10 UTC (permalink / raw To: gentoo-user > As a boot option for the kernel (e.g. /etc/lilo.conf): > append="mem=exactmap mem=640k@0 247M@1M 8M@248M" > > Somehing like this worked with older kernels, don't know how to > do it with 2.6 kernels. I have found somewhere that in 2.6 mem changed to memmap, but i'm not sure if it works in default kernel. Anyway what are those 3 parts in your example(640k 257M 8M)? -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2005-11-14 15:15 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2005-11-13 22:11 [gentoo-user] [OT] Disable memory Peper 2005-11-13 22:34 ` Dale 2005-11-13 22:57 ` [gentoo-user] " Peper 2005-11-13 23:10 ` Hemmann, Volker Armin 2005-11-14 0:23 ` b.n. 2005-11-13 23:27 ` Peper 2005-11-14 0:45 ` [gentoo-user] " Urs Schuetz 2005-11-14 15:10 ` [gentoo-user] " Peper
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox