All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: chris perkins <cperkins@OCF.Berkeley.EDU>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rt16
Date: Wed, 01 Feb 2006 16:36:20 -0600	[thread overview]
Message-ID: <1138833380.18762.67.camel@localhost.localdomain> (raw)
In-Reply-To: <1138832179.6632.12.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

On Wed, 2006-02-01 at 17:16 -0500, Steven Rostedt wrote:
> 
> No, but I don't use an initrd, so my failure was first that it couldn't
> recognize my harddrives.  So I compiled in the necessary drivers into my
> kernel, and it booted right up to the GDM login.  I logged in, and was
> going to reply to you, but I guess I have a different network card since
> I had no network.
> 

Ok, I took the config file I sent you, globally substituted '=y' for
'=m' and rebuilt, then booted that kernel. Other than a message that it
was unable to open the console (udev wasn't started) I got the exact
same failure (same panic backtrace).

> > 
> > I'm fairly certain that the initrd contains the appropriate modules,
> > since I regenerate the initrd each time I generate a new kernel, but
> > I'll go back and verify. 
> > 
> > I'll also convert modules to compiled in and see if that makes a
> > difference.
> 
> Thanks, I've been burnt before with incompatible modules in initrd, that
> I now only use compiled in modules that are needed to boot (ide, ext3,
> etc).  When compiling 3 different kernels with several different configs
> constantly for the same machine, it just becomes easier to not use an
> initrd.

One of the things I wanted to see was how the -rt patch worked with
SELinux, so I decided to try and run a kernel that looked like a distro
kernel (in this case FC4).  I just put together some scripting logic to
build the kernel and module tree three times (athlon64, p3smp, and
duron).  After I've rebuilt, I install on each target system using a
shell script that deletes the old module tree, rsyncs a new one,
installs the matching kernel and builds a new initrd.

Hmmm, FC4 is based on 2.6.14.x. Did something change in the 2.6.15
series that needs a user-space change as well? (I'm running a current
FC4 rootfs).

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-02-01 22:36 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               ` 2.6.15-rt16 Steven Rostedt
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                     ` Clark Williams [this message]
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=1138833380.18762.67.camel@localhost.localdomain \
    --to=williams@redhat.com \
    --cc=cperkins@OCF.Berkeley.EDU \
    --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 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.