On 1/28/2011 4:25 AM, Jean Delvare wrote: > FWIW, last time I experienced this, it was caused by a mouse connected > to the serial port of the machine. Disconnecting the mouse fixed it. All USB here. I wonder if the SMM keyboard and mouse emulation could be the problem? > Also, there are various versions of memtest86 and memtest86+ around, > trying a different version might work around the bug. OTOH, old > versions probably won't know how to deal with DDR3. I'll have to try the latest one tonight and see. The one on my Ubuntu Maverick install just instantly reboots. The one on my Natty test flash stick hangs after drawing the initial screen and a few lines of output. > Oh well. The market of memory modules has gone crazy. And the number of > timing values has literally exploded since DDR2. My BIOS offers to let > me tweak each setting manually and I got totally frightened by the > length of the list (of course I set it all back to auto and ran away.) That's exactly how I felt. > Anyway, I don't think this will be a big issue in practice. All I > really meant was: take the output of decode-dimms with a grain of salt, > while it should be OK on SDRAM and DDR, DDR2 and DDR3 support isn't too > well tested and the reported values may be incorrect. That's why I'm reporting it; so the bugs can be fixed ;) _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
