public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Periodic posix timer support broke between 2.6.9-rc1 and 2.6.9-rc1-bk17
Date: Wed, 13 Oct 2004 17:25:09 +0000	[thread overview]
Message-ID: <416D64F5.4000307@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410130902490.9272@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Tue, 12 Oct 2004, George Anzinger wrote:
> 
> 
>>Christoph Lameter wrote:
>>
>>>I ran some test programs and discovered that the periodic timer support
>>>is broken. The timer is triggered once and then never again. Single shot
>>>timers work fine. 2.6.9-rc1 is fine. The first kernel that I tested where
>>>I noticed the breakage was 2.6.9-rc1-bk17. 2.6.9-rc2 and following all
>>>cannot do periodic timer signals.
>>>
>>>I looked through the changelog but I cannot see anything that would cause
>>>the problem. Roland's patch surely could not have done this.
>>>
>>>Will try to track this down further, time permitting...
>>
>>The most likely thing would be failure to do the call back from the signal
>>delivery code.
> 
> 
> The problem is IA64 arch specific. Works fine on i386.

And I repeat:
The most likely thing would be failure to do the call back from the signal
delivery code.

> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  reply	other threads:[~2004-10-13 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 16:03 Periodic posix timer support broke between 2.6.9-rc1 and Christoph Lameter
2004-10-13 17:25 ` George Anzinger [this message]
2004-10-13 17:29 ` Christoph Lameter

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=416D64F5.4000307@mvista.com \
    --to=george@mvista.com \
    --cc=linux-ia64@vger.kernel.org \
    /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