public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Sigler <linux.kernel@free.fr>
To: paulmck@linux.vnet.ibm.com
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@elte.hu, tglx@linutronix.de
Subject: Re: Old -rt patches
Date: Tue, 07 Aug 2007 10:52:32 +0200	[thread overview]
Message-ID: <46B832D0.5030803@free.fr> (raw)
In-Reply-To: <20070806144158.GA9309@linux.vnet.ibm.com>

Paul E. McKenney wrote:

> John Sigler wrote:
> 
>> I wrote a Linux app where I need high-resolution timers. I went all the 
>> way and installed the -rt patch, which includes the -hrt patches, as far 
>> as I understand.
>>
>> Since I could not afford to change kernels with every new release, I 
>> decided to track the 2.6.20 branch (arbitrarily).
>>
>> At this point I'm using 2.6.20.7-rt8 (-rt8 was the last patch to the 
>> 2.6.20 branch). (I see 2.6.20 is already up to .15)
>>
>> I see a lot of patches going into the -rt patch, but development moved 
>> on to 2.6.21, then 2.6.22, and now 2.6.23, following mainline.
>>
>> I'm not a kernel hacker, so I don't claim to understand the patches, but 
>> the comments sound like a few bugs are fixed here and there. I can't 
>> tell whether these bugs also exist in previous kernels or only appeared 
>> in newer kernels. Even if I knew, I probably wouldn't have the expertise 
>> to back-port the patch.
>>
>> I'm seeing weird behavior in my app, when it has been running 2-4 days. 
>> The timers start to act out, and all hell breaks loose. Basically, I 
>> have no idea what's going on...
>>
>> My question is: is it possible that there is a bug in 2.6.20-rt8 that 
>> has been fixed in subsequent -rt patches (there's a 2.6.21.6-rt21 and a 
>> 2.6.22.1-rt9)? In other words, if I give 2.6.21.6-rt8 or 2.6.22.1-rt9 a 
>> spin, is it possible that my weird behavior disappears?
>>
>> I'm not saying that it's impossible for the bug to be in my app, but the 
>> app is small enough that I'm fairly confident there's no problem there.
> 
> Would you be willing to post your app so people could try to reproduce
> your bug?

Hello Paul,

I cannot provide the app "as is" (I fear the paranoid PHB would 
spontaneously combust). If time permits, I will try to make a small 
testcase to exhibit the problem.

Regards.

  reply	other threads:[~2007-08-07  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 16:41 Old -rt patches John Sigler
2007-08-06  8:55 ` John Sigler
2007-08-06 14:41   ` Paul E. McKenney
2007-08-07  8:52     ` John Sigler [this message]
2007-08-07  6:01   ` Daniel Walker
2007-08-07  8:27     ` John Sigler
2007-08-07 15:10       ` Daniel Walker

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=46B832D0.5030803@free.fr \
    --to=linux.kernel@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --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