LKML Archive on
help / color / mirror / Atom feed
From: Steven Rostedt <>
To: "Luis R. Rodriguez" <>
Cc: Tim Gardner <>,
	Tomas Winkler <>,
	reinette chatre <>,
	"" <>,
	Linux-Kernel <>
Subject: Re: [MEMO] ftrace suckage++
Date: Thu, 30 Oct 2008 21:54:00 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 30 Oct 2008, Luis R. Rodriguez wrote:

> As johannes pointed out to me the culprit to the e1000e corruption was
> determined to be ftrace related [1]. Well it seems I hit an oops with
> ftrace using iwlagn after a simple load of the module using
> wireless-testing. I'm not sure if john's tree yet has ftrace fixes.
> Both Fedora 10 and Ubuntu 8.10 had dynamic ftrace enabled so users on
> these first kernels and using compat-wireless may run into this so
> just putting this out there. I'll can check for this flag in
> compat-wireless for now and bitch/exit if its enabled unless someone
> has a better idea.
> [1]
> Oops, using wireless-testing and iwlagn with these options enabled:

Yes, ftrace in 2.6.27 is known to be broken. That's why labeled 
it as such. What is currently in Linus's 2.6.28 git tree is a completely 
rewritten version of the dynamic ftracer, which addresses all of the 
issues that caused breakage in the 2.6.27 release.

Do not use the 2.6.27 dynamic ftracer, it is known bad. 2.6.28 is fine. If 
you find issues with what is currently in 2.6.28, please let me know. 
There is currently some, "make allyesconfig" breakage that ftrace caused 
on archs other than x86,ppc and sparc, but patches to fix them are 
in queue to Linus.

-- Steve

  parent reply	other threads:[~2008-10-31  1:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 21:45 Luis R. Rodriguez
2008-10-30 23:03 ` Tim Gardner
2008-10-31  1:54 ` Steven Rostedt [this message]
2008-10-31  2:05   ` Luis R. Rodriguez

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [MEMO] ftrace suckage++' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).