All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Identifying i2c devices on Asus P8P67 sandybridge
Date: Fri, 28 Jan 2011 04:51:00 +0000	[thread overview]
Message-ID: <4D424B34.6090309@cfl.rr.com> (raw)
In-Reply-To: <4D40E39E.4030406@cfl.rr.com>

On 01/27/2011 12:14 PM, Jean Delvare wrote:
>>> I am surprised by the tRAS though, it seems way too high, there may be a
>>> bug in the script.
>>
>> It should be 6-8-6-24.
>
> Really? Is this what memtest86 is report? It's a long time since I last
> saw a memory module with the 3 first digits not being the same.

memtest86 seems to hang or reboot.  I am now quite confused because the 
part number that I ordered was OCZ3P11600C6LV4GK and was listed on 
newegg as having 6-8-6-24 timings.  That is the part number listed on 
the retail packaging, but the SPD decodes with decode-dimms ( release 
3.0.3 ) as having part number OCZ3P1600C6LV2G with 7-7-7-33 timing.  The 
Asus bios has an SPD decode utility that agrees with the part number, 
but shows 7-7-7 for cas, trcp, trp, but 16 for tras, not 33.  Despite 
showing tRas as 16 in the SPD, it defaults to driving it at 18.  It also 
lists a bunch of additional timings, none of which are 33.  I can find 
neither part number on OCZ's web site.


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2011-01-28  4:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  3:16 [lm-sensors] Identifying i2c devices on Asus P8P67 sandybridge Phillip Susi
2011-01-27  8:15 ` Jean Delvare
2011-01-27 16:07 ` Phillip Susi
2011-01-27 17:14 ` Jean Delvare
2011-01-27 18:47 ` Phillip Susi
2011-01-28  4:51 ` Phillip Susi [this message]
2011-01-28  9:25 ` Jean Delvare
2011-01-28  9:39 ` Jean Delvare
2011-01-28 14:28 ` Phillip Susi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D424B34.6090309@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.