All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Tomas Winkler <tomasw@gmail.com>,
	reinette chatre <reinette.chatre@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [MEMO] ftrace suckage++
Date: Thu, 30 Oct 2008 17:03:07 -0600	[thread overview]
Message-ID: <490A3D2B.2060400@canonical.com> (raw)
In-Reply-To: <43e72e890810301445r665a0139g752fb1c97069fe59@mail.gmail.com>

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] http://lwn.net/Articles/303390/
> 

I disabled it in the 2.6.27 Intrepid Ubuntu kernel prior to release.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

  reply	other threads:[~2008-10-30 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 21:45 [MEMO] ftrace suckage++ Luis R. Rodriguez
2008-10-30 23:03 ` Tim Gardner [this message]
2008-10-31  1:54 ` Steven Rostedt
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:
  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=490A3D2B.2060400@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=reinette.chatre@linux.intel.com \
    --cc=rostedt@goodmis.org \
    --cc=tomasw@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.