LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rui Nuno Capela <rncbc@rncbc.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: 2.6.21-rt2..8 troubles
Date: Fri, 25 May 2007 21:58:12 +0100	[thread overview]
Message-ID: <46574DE4.2080900@rncbc.org> (raw)
In-Reply-To: <20070401183928.GB27614@elte.hu>

Hi Ingo et al.

It's been quite a while, since last time I've complained about the -rt
kernel patch series. This time I'm afraid I have a nasty specialty I've
been trying to figure out and isolate but to no definitive results.

Fact is, since 2.6.21-rt2 and still on latest -rt8, that I'm facing
troubled behavior while running on a Core2 T7200 laptop (SMP). Somehow,
soon or later, the whole system starts crawling to death. It just slows
down to some kind of Big Freeze, with no evidence over the console
whatsoever, so that I'm ultimately left with a brick on my hands.

This behavior is consistent and occurs every time after a while. It
surely does not occur on 2.6.21-rt1 and earlier. Even stranger, it does
not occur on another but older P4@3.3Ghz desktop (HT/SMP) where a very
identical system image is deployed (openSUSE 10.2 i386, gcc 4.1.2, KDE
3.5.7)

I wish I could give you more details, but the fact is I don't know where
to look. The machine just freezes silently, again and again, with all
kernels from -rt2 to -rt8 inclusive, with no traceable evidence, at
least to my knowledge. The only symptom that I can come about is that,
from some moment on and ever since, the system cannot start any new
process anymore, or otherwise takes forever to realize and launch any
new started process thread.

A sample dmesg output:
   http://www.rncbc.org/datahub/dmesg-2.6.21-rt5.0
The corresponding .config:
   http://www.rncbc.org/datahub/config-2.6.21-rt5.0

Again, there's no logged evidence of the problem, which is as nasty as
repeatable after each boot. Unfortunately, it's not quite
deterministically reproducible, this behavior of turning into an
unresponsive brick ;) It's just a matter of time, or so I think. That's
why I have no clues.

Is there anything I can do better to help myself figuring out this
issue? As this is a  modern laptop such things like a serial console are
unavailable, but it would be nice to track things up over netconsole
perhaps?

I just need some bright and nice directions now ;) Hope someone finds
this worth of attention too. Meanwhile, I'll be happy with 2.6.21-rt1 :)

Cheers.
-- 
rncbc aka Rui Nuno Capela
rncbc@rncbc.org


  parent reply	other threads:[~2007-05-25 21:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 11:26 2.6.20-rc6-rt4 register_cpu_notification undefined Rui Nuno Capela
2007-02-09 18:56 ` 2.6.20-rt5 Oops on boot Rui Nuno Capela
2007-02-16  0:46   ` 2.6.20-rt5 Oops on boot [-rt8 OK] Rui Nuno Capela
2007-02-16  8:25     ` Ingo Molnar
2007-02-19 12:38       ` Sergio Monteiro Basto
2007-04-01 17:12 ` 2.6.21-rc5-rt6 make errors Rui Nuno Capela
2007-04-01 18:39   ` Ingo Molnar
2007-04-03 23:49     ` 2.6.21-rc5-rt10 troubles Rui Nuno Capela
2007-04-04  8:49       ` Ingo Molnar
2007-04-04  9:42         ` Ingo Molnar
2007-05-25 20:58     ` Rui Nuno Capela [this message]
2007-05-26 16:08       ` 2.6.21-rt2..8 troubles Thomas Gleixner
2007-05-26 21:21         ` Rui Nuno Capela
2007-06-06  0:44           ` Rui Nuno Capela
2007-06-08 15:47             ` Thomas Gleixner
2007-06-08 18:21               ` Rui Nuno Capela
2007-06-08 18:50                 ` Thomas Gleixner
2007-06-11 19:36                   ` Rui Nuno Capela
2007-06-11 19:45                     ` Thomas Gleixner
2007-06-11 19:55                       ` Daniel Walker
2007-06-11 20:50                         ` Rui Nuno Capela
2007-06-11 21:14                           ` Thomas Gleixner
2007-06-11 21:25                             ` Rui Nuno Capela
2007-06-11 21:42                               ` Thomas Gleixner
2007-06-11 22:34                                 ` Daniel Walker
2007-06-11 23:08                                   ` Thomas Gleixner
2007-06-12 10:10                                     ` Rui Nuno Capela
2007-07-06 14:16                                       ` Rui Nuno Capela
2007-05-31 15:56       ` Steven Rostedt

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=46574DE4.2080900@rncbc.org \
    --to=rncbc@rncbc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --subject='Re: 2.6.21-rt2..8 troubles' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).