public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Clark Williams <williams@redhat.com>
Cc: chris perkins <cperkins@OCF.Berkeley.EDU>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rt16
Date: Wed, 01 Feb 2006 16:47:56 -0500	[thread overview]
Message-ID: <1138830476.6632.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1138819142.18762.10.camel@localhost.localdomain>

On Wed, 2006-02-01 at 12:39 -0600, Clark Williams wrote: 
> On Wed, 2006-02-01 at 13:32 -0500, Steven Rostedt wrote:
> > 
> > I'm still curious to what's happening with your kernel.  I'm currently
> > running my x86_64 (typing right now on it) with CONFIG_SMP=n and
> > CONFIG_LATENCY=y.  I know you probably sent a config before, but could
> > you send it to me again.  (probably best to send it to me off list)
> 
> yeah, it's been gnawing at me too. Not really stopping me, but I've seen
> it happen on two Athlon64's (3000+ and 3400+). 
> 
> I'll send the .config offlist.

Clark,

Could you make sure that your modules in the initrd that you use are the
ones created with the LATENCY_TRACE option.  After converting all the
modules into compiled in options, I successfully booted the kernel.  So
you might have an incompatibility with the modules in initrd, when you
turn on LATENCY_TRACE.

-- Steve



  parent reply	other threads:[~2006-02-01 21:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 16:49 2.6.15-rt16 chris
2006-01-30 17:03 ` 2.6.15-rt16 Thomas Gleixner
2006-01-30 17:09   ` 2.6.15-rt16 Steven Rostedt
2006-01-30 17:24   ` 2.6.15-rt16 chris perkins
2006-01-30 18:42     ` 2.6.15-rt16 Steven Rostedt
2006-01-31 17:45       ` 2.6.15-rt16 chris perkins
2006-01-30 20:33     ` 2.6.15-rt16 Clark Williams
2006-01-31 17:52       ` 2.6.15-rt16 chris perkins
2006-01-31 18:07         ` 2.6.15-rt16 Clark Williams
2006-02-01 18:32           ` 2.6.15-rt16 Steven Rostedt
2006-02-01 18:39             ` 2.6.15-rt16 Clark Williams
2006-02-01 20:20               ` 2.6.15-rt16 Lee Revell
2006-02-01 21:47               ` Steven Rostedt [this message]
2006-02-01 21:51                 ` 2.6.15-rt16 Clark Williams
2006-02-01 22:16                   ` 2.6.15-rt16 Steven Rostedt
2006-02-01 22:36                     ` 2.6.15-rt16 Clark Williams
2006-02-02  1:10                       ` 2.6.15-rt16 Steven Rostedt
2006-02-02 14:46                         ` 2.6.15-rt16 Clark Williams
2006-02-02  1:22                       ` 2.6.15-rt16 Steven Rostedt
2006-02-02 15:01                         ` 2.6.15-rt16 Clark Williams

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=1138830476.6632.5.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=cperkins@OCF.Berkeley.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=williams@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox