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: Fri, 20 Jan 2012 11:05:48 +0700 [thread overview]
Message-ID: <CAGdaadbrPuKyo4dC-_7heAgHwkvhpuE4w-aySsdLiu5KKyqfFA@mail.gmail.com> (raw)
In-Reply-To: <CALButCJhjJ_9aN9wgLnpaMBMr2YV+8HpXxFLysjmKdaNNv4P=Q@mail.gmail.com>
Hi Graeme :)
On Fri, Jan 20, 2012 at 09:20, Graeme Russ <graeme.russ@gmail.com> wrote:
> This may not be the best place to post this question, so please excuse...
>
> I have a brand new Intel i5 / z68 EUFI motherboard (ASRock Z68 Pro3
> Gen3) with 8GB RAM running Fedora 16 (64 bit) which is experiencing
> lockups which send the video crazy (flashing screen) but there is
> nothing appearing in /var/log/messages to indicate what is going wrong
> (no oops).
>
> I'm sure it is graphics related. I thought of Cc'ing the i915
> maintainer (Keith Packard) but figured I should wait until I am sure
>
> I _think_ it might be power related as the hang never seems to occur
> while I'm actively using the computer - Only after I have stopped for
> a few minutes does it happen but not always.
>From your description alone, I think it's still hard to pinpoint the
root of the problem. So I guess we'll gonna play cat and mouse a bit
here.
First of all, IMHO you still need to do logging. Maybe, just maybe,
the reason why you don't see anything suspicious in /var/log/messages
because the lock is bad enough that prevents the error messages to be
picked up. Try setting up netconsole (here is the clue:
https://wiki.ubuntu.com/Kernel/Netconsole) or serial console (try
reading http://linux.koolsolutions.com/2009/03/29/howto-redirecting-linux-console-output-over-serial-port-on-another-machine/).
Hopefully it will catch suspicious message.
You could also enable several verbose debugging message under "Kernel
hacking" section during "make menuconfig".
Hope it helps....
NB: You said if it actively used, it goes well? Sounds like dynamic
CPU frequency adjustment bug....
--
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-20 4:05 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 [this message]
[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
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=CAGdaadbrPuKyo4dC-_7heAgHwkvhpuE4w-aySsdLiu5KKyqfFA@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).