Hi,
>Messaggio originale
>Da: b...@decadent.org.uk
>Data: 10-nov-2012 19.23
>A: "asronche...@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 +01
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,
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 syslo
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 debian-kernel-requ
Hi,
The second (B) bank of the 8gB set is working fine.
uptime is:
20:54:53 up 5 days, 9:18, 7 users, load average: 0.68, 0.56, 0.53
and i had no crashes, and right now i 've just tested also file transfer (via
tar + nc), to see if i have md5sums inconsistencies and it works good , no data
Hi,
i was using SSD + 4gB(A)
(A) is the first of the 2 4gB banks.
while browsing the plugin-container crashed many times, like this (from
syslog):
kernel: [24135.522448] plugin-containe[7418] general protection ip:
7f23ffe8c1a1 sp:7f23fe02da00 error:0 in libflashplayer.so[7f23ff83+117b000
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
Description:
>Messaggio originale
>Da: b...@decadent.org.uk
>Data: 23-ott-2012 3.02
>A: "asronche...@libero.it"
>Cc: <684...@bugs.debian.org>,
>Ogg: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM,
working around it.
>
>On Tue, 2012-10-
On Tue, 2012-10-23 at 02:55 +0200, asronche...@libero.it wrote:
> Hi,
>
> `uptime ` is:
> 02:47:34 up 6 days, 6:23,
>
> and still no problem here.
>
> the combination SSD + 4gB RAM is working great.
>
> The only thing i changed was in /etc/fstab, i used "noatime,discard" instead
> of "defau
Hi,
`uptime ` is:
02:47:34 up 6 days, 6:23,
and still no problem here.
the combination SSD + 4gB RAM is working great.
The only thing i changed was in /etc/fstab, i used "noatime,discard" instead
of "default" in the options column for the /home partition (ext4).
next test will start in the
Hi,
this time the test was bad :(
it lasted only 3 hours , then it crashed.
this time the setup was: non-SSD + 8gB.
the crash happened while i was copying a file to another pc, via netcat. The
file was 3.4gB.
At first the file was transmitted until the end, but when i checked the md5sum
i've
Hi,
`uptime` is:
14:56:06 up 5 days, 12:39,
the combination used for the test was:
non-SSD + 4gB
(the same stuff that was mounted in the notebook when i bought it almost 2 yrs
ago)
it works *perfectly* !
I fell like i'm in a time machine :) it works well, as it worked until ~May
2012.
No
On Thu, 2012-10-11 at 15:49 +0200, asronche...@libero.it wrote:
> Hi,
> i did some test with other distros (slackware/fedora) and the corruption
> problem seems to persist.
> Yesterday i was coming back to debian , dumping a dd backup image from an
> external WD hard disk, using a fedora usb-live
13 matches
Mail list logo
