From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <johnstul@us.ibm.com>,
Deepak Saxena <dsaxena@plexity.net>
Subject: Re: 2.6.17-rc6-rt1
Date: Fri, 09 Jun 2006 12:12:30 +0200 [thread overview]
Message-ID: <1149847951.3829.26.camel@frecb000686> (raw)
In-Reply-To: <1149842550.7585.27.camel@Homer.TheSimpsons.net>
On Fri, 2006-06-09 at 10:42 +0200, Mike Galbraith wrote:
> On Wed, 2006-06-07 at 23:14 +0200, Ingo Molnar wrote:
> > i have released the 2.6.17-rc6-rt1 tree, which can be downloaded from
> > the usual place:
> >
> > http://redhat.com/~mingo/realtime-preempt/
> >
> > the biggest change was the port to 2.6.17-rc6, and the moving to John's
> > latest and greatest GTOD queue. Most of the porting was done by Thomas
> > Gleixner (thanks Thomas!). We also picked up the freshest genirq queue
> > from -mm and the freshest PI-futex patchset. There are also lots of ARM
> > fixups and enhancements from Deepak Saxena and Daniel Walker.
>
> I have some fairly strange things going on with this kernel.
>
> First of all, during boot, I end up with these two entries.
> BUG: wq(events) setscheduler() returned: -22.
> BUG: wq(events) setscheduler() returned: -22.
>
> After boot, it takes a very long time for KDE to finish loading... more
> than five minutes for the desktop background to finally appear. Tasks
> which are doing nothing but a ~50ms gettimeofday() select() idle loop
> show up in top as using 1 to 3 percent cpu, though strace of these looks
> fine. Starting any threaded app takes ages, whereas plain-jane things
> like gcc work fine. For example, if I fire up xmms, the gui comes up
> quickly, but it takes over three minutes from the time I poke play until
> the first sound is emitted. Starting evolution takes even longer.
>
> Hoping that something might show up while running glibc-2.4 make check
> to save me from wading through huge truckloads of strace, I tried it.
> It repeatedly goes boom. RT29 goes boom the same way, but doesn't
> exhibit the slow threaded app symptom. Drat.
>
Yep noticed that here too. As you pointed out it seems to be related
to threaded apps. ls, vi, ... work fine whereas xemacs or others are
real slow, portmapper fails to respond, ...
I've got no indication in the logs that something went wrong, nor
do I see any kernel BUG or WARNING.
My box is a dual 2.8GHz HT xeon w/ 2GB mem.
rt29 was fine as is 2.6.17-rc6.
I feel a bit perplexed here.
Sébastien.
next prev parent reply other threads:[~2006-06-09 10:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 21:14 2.6.17-rc6-rt1 Ingo Molnar
2006-06-08 2:09 ` 2.6.17-rc6-rt1 Daniel Walker
2006-06-08 3:49 ` 2.6.17-rc6-rt1 Mark Knecht
2006-06-08 20:12 ` 2.6.17-rc6-rt1 Mark Knecht
2006-06-08 6:42 ` [PATCH -rt] Trivial compiler warning fix Jan Altenberg
2006-06-08 8:51 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-08 19:52 ` 2.6.17-rc6-rt1 john stultz
2006-06-08 20:01 ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-08 10:28 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 12:23 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 11:28 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 18:27 ` 2.6.17-rc6-rt1 Kevin Hilman
2006-06-08 19:03 ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-08 23:57 ` 2.6.17-rc6-rt1 john stultz
2006-06-09 7:28 ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09 8:42 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 10:12 ` Sébastien Dugué [this message]
2006-06-09 11:35 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 11:44 ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 12:20 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 12:57 ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 13:11 ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09 13:42 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 14:31 ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09 15:55 ` 2.6.17-rc6-rt1 Daniel Walker
2006-06-09 18:41 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 19:09 ` 2.6.17-rc6-rt1 Thomas Gleixner
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=1149847951.3829.26.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=dsaxena@plexity.net \
--cc=efault@gmx.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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