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: Sun, 22 Jan 2012 00:40:49 +0700 [thread overview]
Message-ID: <CAGdaadZOGKKGL176=2GK-iwXEvQL1sLDWhauN3FCGfoPVTnsZA@mail.gmail.com> (raw)
In-Reply-To: <4F1A8C32.3050907@gmail.com>
Hi again :)
On Sat, Jan 21, 2012 at 16:58, Graeme Russ <graeme.russ@gmail.com> wrote:
> Tell me about it :( - I've been here before, just not with the Linux kernel
At least I can tell you will get hiccup less :) Anyway, you do have
data backup, right? Just in case it causes corrupt and you lose some
of your data. Better safe than sorry...
> I got netconsole working and it took a while to crash, but it finally did
> and guess what - No oops :(
Ok, no luck....how about serial console? same result? (I am not sure
which one will be helpful in your case).
Just crossing my mind, is this bug also happen if you work strictly in
text console i.e no X Window at all?
> I've added more (see attached config)
>From what I can see at a glance, you already enabled enough debugging
features....so just keep it that way at least for now.
> Also, I am using a very recent tip of linus' branch (commit
> ccb19d263fd1c9e34948e2158c53eacbff369344)
I think this is the way it will go, you would likely doing bisecting.
Thing is, you first need to find kernel version that works well. You
said you have trouble with 3.1.9-fc...how about 3.1.8 or below?
> Hmmm, any way to test this theory?
Let's say, switching cpu governor? What do you use now? ondemand? then
try to switch to conservative. Or just lock the cpu frequency into
certain number.
--
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-21 17:40 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 [this message]
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='CAGdaadZOGKKGL176=2GK-iwXEvQL1sLDWhauN3FCGfoPVTnsZA@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).