Hi,
Messaggio originale
Da: b...@decadent.org.uk
Data: 10-nov-2012 19.23
A: asronche...@libero.itasronche...@libero.it
Ogg: Re: Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS
may corrupt low RAM, working around it.
On Fri, 2012-11-09 at 16:40 +0100, asronche
Hi,
with only the working 4gB SODIMM of the 8gB set i've reached a ~ 5days and
15mins uptime.
Now i'm testing that SODIMM + one 2gB SODIMM from the 4gB set.
This way the ram will amount to ~ 6gB , so i'll be able to understand if my pc
has some problems when the ram is 4gB.
P.s.: someone is
Hi,
after ~48 hours of memtest86+ (almost 60 tests) , it has founded no errors on
the 'problematic' RAM (the 4gB ram B of the 8gB set).
I'm now trying again to use that ram to run debian, to see if i have a crash
also this time.
ciao,
Asdrubale
--
To UNSUBSCRIBE, email to
Hi,
The 4gB module B of the 8gB set isnt working.
(B is the one that caused a system crash the last time i used it. It is the
same that gave me *no* errors when i tested it via memtest86+)
after 4 hours i had a kernel panic: the notebook started a continuos
'beeep' and on the screen
Hi,
kernel is 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux,
test with: SSD + 8gB.
nothing crashed for 28 hours. I also managed to copy 3 files (5-8 gB per file)
to another pc via ethernet and the md5sums were ok. I also did the opposite
(the other pc already had the
Messaggio originale
Da: b...@decadent.org.uk
Data: 23-ott-2012 3.02
A: asronche...@libero.itasronche...@libero.it
Cc: 684...@bugs.debian.org, stapp...@stappers.nl
Ogg: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM,
working around it.
On Tue, 2012-10-23 at 02:55
Since your upgrade involved replacing the old 2*2GB modules with 2*4GB
new modules, rather than adding a new 4GB module to an old 4GB module, I
agree that there isn't any reason to suspect incompatibility.
Ben.
--
Ben Hutchings
Humour is the best antidote to reality.
signature.asc
7 matches
Mail list logo
