We are pleased to announce the 2.6.24-rc7-rt3 tree, which can be
downloaded from the location:

  http://rt.et.redhat.com/download/

Information on the RT patch can be found at:

  http://rt.wiki.kernel.org/index.php/Main_Page

Changes since 2.6.24-rc7-rt2

  - KVM updates (Thomas Gleixner)

  - more PPC32 compile fixes

  - Mips clean ups (Frank Rowand)

  - workqueue lock leak cleanup (Daniel Walker)

  - hacked fix for rt-migration (Mike Galbraith)


to build a 2.6.24-rc7-rt3 tree, the following patches should be applied:

  http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.tar.bz2
  http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.24-rc7.bz2
  http://rt.et.redhat.com/download/patch-2.6.24-rc7-rt3.bz2


And like always, my RT version of Matt Mackall's ketchup will get this
for you nicely:

  http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3


The broken out patches are also available.

-- Steve



--

[ message continues ]

Up and running here:

mark@lightning ~ $ uname -a
Linux lightning 2.6.24-rc7-rt3 #1 PREEMPT RT Wed Jan 16 11:06:11 PST
2008 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
mark@lightning ~ $

Nothing of interest in dmesg. The issue I reported earlier about
/var/log/messages has been there for a long time without me noticing
it. I'm in 2.6.23-rt1 and I still see it so it has nothing to do with
the kernel as I'm sure you decided already.

Jan 16 11:12:55 lightning sshd[5915]: Server listening on :: port 22.
Jan 16 11:12:55 lightning sshd[5915]: error: Bind to port 22 on
0.0.0.0 failed: Address already in use.

Will continue testing as I get time.

Cheers,
Mark
--

[ message continues ]

Thanks,

Are you sure you don't see this when booting the vanilla kernel. Also, if
you do try a vanilla kernel, don't use the distro version. Use what ever
version of the -rt patch you used. ie. for 2.6.23-rt1 try out 2.6.23 with
the same config (with necessary updates).

-- Steve

--

[ message continues ]

Steve,
   I'll give it a try. I am pretty sure it's a distro specific issue
so I'm going to check with them about how to properly configure sshd.
It's likely jsut some oversight in one of my config files. Being a
Gentoo user we have more things like this that we have to look after.
Probably some update clobbered something and I just noticed it
recently.

   If I get a quick minute I'll build the 2.6.23 and take a look at that also.

Thanks,
Mark
--

[ message continues ]