Hi,
>----Messaggio originale---- >Da: b...@decadent.org.uk >Data: 10-nov-2012 19.23 >A: "asronche...@libero.it"<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 +0100, asronche...@libero.it wrote: >> 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. > >Yes, that's a good experiment. That experiment went well. After that, i tried another experiment: I mounted the problematic 4gB SODIMM into a notebook of a friend and he borrowed me one of his SODIMM (4gB) and the two laptops worked well. In this case my laptop was using 2 SODIMM: SODIMM A) 4gB (it's the good one of the 8gB set) SODIMM B) 4gB (it comes from my friend notebook) so my friend notebook used this set: SODIMM A) 2gB (it was already there in his notebook) SODIMM B) 4gB (this is the one that created problems in my notebook) my friend uses windows 7 and i use debian wheezy. No problem arised . The two notebook worked good for more than 5 days without problems. After the 5 days i stopped the experiment and i gave back that SODIMM to my friend. Conclusions: 1)The problematic SODIMM could be defective in a way that create problems when plugged in my notebook. (problem with its pins, maybe) 2)That SODIMM worked well in another notebook and passed long memtesting on my notebook. Why doesnt it work on my notebook? Why does it create memory corruption problems? This remains a mistery. 3)My notebook has no problem handling RAM amount >4gB, since it was able to survive a 5 days uptime with 8gB RAM mounted. Problem is partially solved, since i can at least mount 6gB RAM on my notebook (4gB SODIMM + the old 2gB one ) Ben, thanks for your help but now i'm pretty sure that this is simply an hardware problem (since , as i could see , my debian wheezy installation had no problems to handle 8gB RAM) > >> P.s.: someone is spamming on bugs.debian.org spoofing my email address: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683177 >> i 've signaled the spam using the "signal spam" link. I hope this doesnt get >> my email backlisted. > >No, spam reporting should just result in that single message being >hidden. > >Ben. it's happend again, i've just seen that another spam email has been sent via my email account on 22 november. I think that's because i usually use Tor to access the webmail. Maybe someone owning an exit node sniffed my traffic. Some spam was sent to some subscription e-mail addresses, the ones with an hash in the address. I checked in my webmail and i've seen that they're the same mail addresses that were used by bugs. debian.org to receive my subscription-confirmation. That 'hash mail address' is the kind of thing someone can only know by using my webmail (aka accessing the list of addressess i've communicated with) Ciao, Asdrubale -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
