From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Best way to debug an Intel Core i5 hang - likely graphics (possibly power) related
Date: Tue, 31 Jan 2012 11:25:34 +0700 [thread overview]
Message-ID: <CAGdaadY+DqPFZd_K1GYtHZACFPJEF0UnTMjtXWNM0SFaa84zCw@mail.gmail.com> (raw)
In-Reply-To: <CALButCJsiA_KTQ1Xy-pzGMER4HgdPP0ZT-yu3dtNudja5f84FA@mail.gmail.com>
Hi :)
On Tue, Jan 31, 2012 at 10:00, Graeme Russ <graeme.russ@gmail.com> wrote:
> I _think_ I've solved the problem - SDRAM Voltage
You got my respect man, you're really stubborn :)
> The SDRAM I am using has a rated operating voltage of 1.5V +/- 0.075.
> It looked like the motherboard BIOS had decided to use the upper limit
> of 1.575V when set to 'Auto'. I changed it to 'Manual' and set the
> SDRAM voltage to 1.5V and it's been running stably for the longest
> time it ever has.
Thanks (again) for sharing. So this indeed has tight relationship with
RAM "misbehaviour". How do you know it? Do you inspect every piece of
your hardware? I am curious to know (maybe others too).
NB: it could be a good lesson that system lock up might have
absolutely nothing to do with kernel.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2012-01-31 4:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 2:20 Best way to debug an Intel Core i5 hang - likely graphics (possibly power) related Graeme Russ
2012-01-20 4:05 ` Mulyadi Santosa
[not found] ` <4F1A8C32.3050907@gmail.com>
2012-01-21 17:40 ` Mulyadi Santosa
2012-01-23 11:12 ` Graeme Russ
2012-01-23 17:21 ` Mulyadi Santosa
2012-01-26 10:15 ` Graeme Russ
2012-01-26 10:30 ` Mulyadi Santosa
2012-01-26 10:45 ` Graeme Russ
2012-01-26 11:00 ` Mulyadi Santosa
2012-01-31 3:00 ` Graeme Russ
2012-01-31 4:25 ` Mulyadi Santosa [this message]
2012-01-31 4:52 ` Graeme Russ
2012-01-31 5:49 ` Mulyadi Santosa
2012-01-31 10:44 ` Graeme Russ
2012-01-31 14:41 ` Mulyadi Santosa
2012-01-31 22:06 ` Graeme Russ
2012-02-01 15:03 ` Mulyadi Santosa
2012-02-01 15:28 ` Graeme Russ
2012-02-01 15:34 ` Mulyadi Santosa
2012-02-01 15:44 ` Graeme Russ
2012-02-01 22:11 ` Graeme Russ
2012-02-02 3:28 ` Mulyadi Santosa
2012-02-02 23:04 ` Graeme Russ
2012-02-03 6:02 ` Mulyadi Santosa
2012-01-31 6:14 ` Fredrick
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=CAGdaadY+DqPFZd_K1GYtHZACFPJEF0UnTMjtXWNM0SFaa84zCw@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).