Bug#684666: R: Re: Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
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...@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-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/29234664.274371354198097450.JavaMail.defaultUser@defaultHost
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
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 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. That spam was sent on 8th November. On 8th November i've send *no* emails. ciao, Asdrubale -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4016423.11710681352475623733.JavaMail.defaultUser@defaultHost
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
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...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/22561044.9318171351972642373.JavaMail.defaultUser@defaultHost
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
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 syslog-like messages appeared. I remember reading something about swapper and then at the bottom of the screen kernel panic. I was downloading a file via iceweasel and watching a movie via IRC/xdcc with the command: nc -v -v -n IP PORT|pv|mplayer -cache 50 - when suddently all crashed. the ramdisk was 1gB and the tmpfs mounts (are they ramdisks?) are: /run (376M) /run/lock (5M) /run/shm (752M) Now i have replaced the module B with the module A* and i'm going to do exactly the same things i was doing (a web dwl + an Irc stream opened bia mplayer with cache == 500M ) to see if it crash again. * (the other 4gB module of the 8gB set, A is the one that worked well last time i used it alone) ciao, Asdrubale -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1734894.6062461351988376723.JavaMail.defaultUser@defaultHost
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
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 +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 default in the options column for the /home partition (ext4). next test will start in the next days, with SSD + 8gB. I think that probably the problem resides in how my installation is handling the 8gB ram. Are there some special settings that i need to configure when switching from a 4gB ram to 8gB ram? No change should be necessary. One thing I should have thought of earlier is that a pair of different memory modules might not be reliable. In my personal experience, two different modules will often work, but it's generally recommended to use a matched set. Ben. -- Ben Hutchings Humour is the best antidote to reality. Hi, (i'm still using SSD + 4gB , atm) thanks for your reply. dmidecode contains the string Product Name: K52Jc I 've bought the 8gB on crucial.com. The site says that the hw they sell is 100% compatiple for my notebook. It works like this: i went on their website and then i entered K52Jc in the search form and then the site presents me all available and compatible upgrades for my notebook (K52Jc). It showed me various SSD disks and only one RAM upgrade: 8gB. According to dmidecode my mobo supports a maximum of 16gB of RAM, but checking on asus.com it seems that the notebook only support a max of 8gB. So i bought and SSD and the 8gB RAM. I've the 8gB RAM in front of me and i can read on one of the two: 4GB DDR3 - 1333 (PC3 10600) SODI It is very similar to what i can see via dmidecode about the 4gB that are mounted at the moment on my notebook: 4gB on dmidecode: Handle 0x0041, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 16 GB Error Information Handle: Not Provided Number Of Devices: 4 Handle 0x0042, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: SODIMM Set: None Locator: DIMM0 Bank Locator: BANK 0 Type: DDR3 Type Detail: Synchronous Speed: 1067 MHz Manufacturer: Kinston Serial Number: 923C7BB9 Asset Tag: Unknown Part Number: ASU1333D3S9DR8/2G Rank: Unknown Handle 0x0043, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x000 Ending Address: 0x0007FFF Range Size: 2 GB Physical Device Handle: 0x0042 Memory Array Mapped Address Handle: 0x004B Partition Row Position: Unknown Interleave Position: 1 Interleaved Data Depth: 1 Handle 0x0044, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM1 Bank Locator: BANK 1 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: [Empty] Serial Number: [Empty] Asset Tag: Unknown Part Number: [Empty] Rank: Unknown Handle 0x0045, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: SODIMM Set: None Locator: DIMM2 Bank Locator: BANK 2 Type: DDR3 Type Detail: Synchronous Speed: 1067 MHz Manufacturer: Kinston Serial Number: 923CDEB1 Asset Tag: Unknown Part Number: ASU1333D3S9DR8/2G Rank: Unknown Handle 0x0046, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x000 Ending Address: 0x0007FFF Range Size: 2 GB Physical Device Handle: 0x0045 Memory Array Mapped Address Handle: 0x004B Partition Row Position: Unknown Interleave Position: 2 Interleaved Data Depth: 1 Handle 0x004A, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM3 Bank
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
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: This is a digitally signed message part
