From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: ftrace WARNING during boot
Date: Sat, 3 Oct 2009 19:36:45 +0300 [thread overview]
Message-ID: <20091003163645.GI32486@mea-ext.zmailer.org> (raw)
In-Reply-To: <1254585561.12892.3.camel@gandalf.stny.rr.com>
On Sat, Oct 03, 2009 at 11:59:21AM -0400, Steven Rostedt wrote:
> On Sat, 2009-10-03 at 14:28 +0300, Matti Aarnio wrote:
>
....
> > > > kernel: ---[ end trace fbf9054ae0f212c7 ]---
> > > > kernel: ftrace faulted on writing [<ffffffffa0003072>] i2c_new_dummy+0x8/0x5e [i2c_core]
>
> This means the update to modify the call to mcount to a nop failed.
> Everything else passed (the read and compare). I think I saw some
> patches go by that works on making the text in modules read only.
>
> The ftrace update for text in core kernel makes the text writable for
> the small window where we call kstop machine and update the text. Then
> it makes that code read only again. At the time this code was written,
> the modules were always read/write. If this has changed, I believe the
> ftrace update needs to be fixed too.
Lattest kernel on Fedora 12 beta series does not have this trouble.
(It has troubles elsewere, but not at ftrace.)
ACPI: Core revision 20090521
ftrace: converting mcount calls to 0f 1f 44 00 00
ftrace: allocating 21030 entries in 83 pages
Setting APIC routing to flat
> -- Steve
/Matti Aarnio
next prev parent reply other threads:[~2009-10-03 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 10:53 ftrace WARNING during boot Matti Aarnio
2009-10-03 11:00 ` Frederic Weisbecker
2009-10-03 11:28 ` Matti Aarnio
2009-10-03 12:00 ` Frederic Weisbecker
2009-10-03 14:00 ` Ingo Molnar
2009-10-03 15:59 ` Steven Rostedt
2009-10-03 16:36 ` Matti Aarnio [this message]
2009-10-03 13:59 ` Ingo Molnar
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=20091003163645.GI32486@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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