From: graeme.russ@gmail.com (Graeme Russ)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Best way to debug an Intel Core i5 hang - likely graphics (possibly power) related
Date: Thu, 2 Feb 2012 02:44:51 +1100 [thread overview]
Message-ID: <CALButCK5sskYYuRfBqOuA93EihacUO+AVkNHxLKPWrL5gB9BUA@mail.gmail.com> (raw)
In-Reply-To: <CAGdaada8Vvp=_YNTOiyJmjTSCZQ5SaB3C-DSdpmBc6nrSqXBnw@mail.gmail.com>
Hello (again :))
On Feb 2, 2012 2:35 AM, "Mulyadi Santosa" <mulyadi.santosa@gmail.com> wrote:
>
> Hi again :)
>
> On Wed, Feb 1, 2012 at 22:28, Graeme Russ <graeme.russ@gmail.com> wrote:
> > I suspect possibly flakey cap in one of the voltage regulators
>
> if that's true, that's really nasty. And I think that also means that
> motherboard is pretty unusable for long usage period.
>
> Is it possible to just trade your motherboard with new one?
Since the shop I bought it from is so difficult to deal with, I ordered a
new one (different brand, Gigabyte this time) online like I always have
before.
> > 3.3.0+ (top of Linus' tree from a few days ago)
>
> Somehow, IMHO, 2.6.x series is still better for stability. After
> looking at kernel.org, I think you can test with 2.6.32.55.
I think Fedora 16 came with that (or close to)
The freeze happens in Winows 7 as well
Regards,
Graeme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120202/30cdf1ac/attachment.html
next prev parent reply other threads:[~2012-02-01 15:44 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
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 [this message]
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=CALButCK5sskYYuRfBqOuA93EihacUO+AVkNHxLKPWrL5gB9BUA@mail.gmail.com \
--to=graeme.russ@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).