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 14:28:11 +0000	[thread overview]
Message-ID: <4D42D27B.5040004@cfl.rr.com> (raw)
In-Reply-To: <4D40E39E.4030406@cfl.rr.com>

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@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2011-01-28 14:28 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
2011-01-28  9:25 ` Jean Delvare
2011-01-28  9:39 ` Jean Delvare
2011-01-28 14:28 ` Phillip Susi [this message]

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=4D42D27B.5040004@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.