public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rui Nuno Capela <rncbc@rncbc.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: 2.6.21-rt2..8 troubles
Date: Mon, 11 Jun 2007 20:36:10 +0100	[thread overview]
Message-ID: <466DA42A.6010600@rncbc.org> (raw)
In-Reply-To: <1181328636.4404.335.camel@chaos>

Thomas Gleixner wrote:
> On Fri, 2007-06-08 at 19:21 +0100, Rui Nuno Capela wrote:
>> Just built from linux-2.6.22-rc4.tar.bz2, with patch-2.6.22-rc4-hrt5.
>> All's working apparentely nice on this offending machine (laptop, intel
>> core2 T7200). In fact, I'm writing this very reply under it and through
>> ipw3945 wifi module--which never was so pragmatic on -rt2..9 ;)
>>
>> Nevertheless, this is not preempt-realtime (-rt) is it? And I it never
>> complained about vanilla.
>>
>> Is this good news though?
> 
> Well, the patch carries the same high resolution timer fixes as -rt, so
> I just wanted to exclude those. Thanks for testing.
> 
> I'm spinning -rt10 with a couple of fixes. Should be out sometimes
> tomorrow. If the problem persists, we need to dig deeper.
> 

Uhoh. I'm sorry to tell, but the problem is still creeping on
2.6.21.4-rt11 and -rt12 :(

So sorry.
-- 
rncbc aka Rui Nuno Capela
rncbc@rncbc.org

  reply	other threads:[~2007-06-11 19:38 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     ` 2.6.21-rt2..8 troubles Rui Nuno Capela
2007-05-26 16:08       ` 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 [this message]
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=466DA42A.6010600@rncbc.org \
    --to=rncbc@rncbc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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