From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: use raw spinlocks instead of spinlocks
Date: Wed, 5 Nov 2008 11:55:41 +0100 [thread overview]
Message-ID: <20081105105541.GB19361@elte.hu> (raw)
In-Reply-To: <c62985530811050250u638c8f95j7d80a13f834b06bf@mail.gmail.com>
* Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 2008/11/4 Ingo Molnar <mingo@elte.hu>:
> > just make sure normal printk is totally silent. (otherwise you get
> > double lines on the console plus no reduction in recursion risk)
> >
> > i usually add a return; hack to kernel/printk.c:printk(), to make sure
> > it never executes anything. (and add a notrace to it as well) Maybe we
> > could even make this dependent on early_printk=...,keep.
>
> Thanks for your help!
>
> I tried the earlyprintk=vga,keep and I thought that the normal printk
> output would
> be replaced by early_printk output but that's not the case...
> So I replaced the content of printk by this of early_printk and it worked.
> But it seems that after the setting of the console, the early_printk
> doesn't work anymore.
>
> Should I disable something else? I haven't any console=.... parameter
> but I guess I missed
> something there...
perhaps try a "console=tty 3" bootup - to boot into non-graphics
initlevel 3, and to have a vga tty set up. Then comment out the
regular printk(), to make sure it never tries to output to the regular
tty.
does earlyprintk=vga,keep work in that case?
> But, I set the parameter nmi_watchdog=2 (I didn't know I had to
> start explicitly the nmi watchdog) and at last... I had my
> backtraces :-)
heh :-)
> All these backtraces were related to time function. And one of the
> special things of the time functions is that they often manipulate
> 64 bits numbers. Actually I totally forgot that a function could
> return a long long, so I had to save edx register in the return
> handler to restore it in its end because 64 bits numbers are
> returned as a couple into eax and edx in x86-32.
>
> So the main problem is now solved. But it remains a last (but more
> rare) deadlock somewhere. I don't know why at this time and the nmi
> watchdog doesn't tell anything. So I will have to use early_printk
> to see the last functions traced. But the problem is that it doesn't
> print on the console...
hm. Let me know if you cannot get this to work. I regularly use
earlyprintk=serial,...,keep myself, and it works there - but i dont
use earlyprintk=vga,keep that often.
Ingo
next prev parent reply other threads:[~2008-11-05 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 0:01 Frederic Weisbecker
2008-11-03 0:45 ` Steven Rostedt
2008-11-03 1:17 ` Frédéric Weisbecker
2008-11-03 6:46 ` Ingo Molnar
2008-11-03 13:24 ` Frédéric Weisbecker
2008-11-04 2:03 ` Frédéric Weisbecker
2008-11-04 9:43 ` Ingo Molnar
2008-11-04 11:14 ` Frédéric Weisbecker
2008-11-04 12:03 ` Ingo Molnar
2008-11-05 10:50 ` Frédéric Weisbecker
2008-11-05 10:55 ` Ingo Molnar [this message]
2008-11-06 0:41 ` Frédéric Weisbecker
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=20081105105541.GB19361@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®