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
next prev parent reply other threads:[~2004-10-13 17:25 UTC|newest]
Thread overview: 7+ 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
[not found] <B6E8046E1E28D34EB815A11AC8CA312902CD3264@mtv-atc-605e--n.corp.sgi.com>
2004-09-24 12:16 ` [time] add support for CLOCK_THREAD_CPUTIME_ID and CLOCK_PROCESS_CPUTIME_ID Christoph Lameter
2004-09-25 4:25 ` Ulrich Drepper
2004-09-25 5:54 ` Christoph Lameter
2004-09-25 6:08 ` Ulrich Drepper
[not found] ` <B6E8046E1E28D34EB815A11AC8CA312902CD327E@mtv-atc-605e--n.corp.sgi.com>
2004-09-27 20:58 ` [RFC] Posix compliant behavior of CLOCK_PROCESS/THREAD_CPUTIME_ID Christoph Lameter
2004-09-28 19:18 ` Ulrich Drepper
2004-09-29 3:25 ` Posix compliant CLOCK_PROCESS/THREAD_CPUTIME_ID V4 Christoph Lameter
2004-09-29 17:45 ` George Anzinger
[not found] ` <B6E8046E1E28D34EB815A11AC8CA31290322B307@mtv-atc-605e--n.corp.sgi.com>
2004-10-07 4:56 ` Posix compliant cpu clocks V7 [0/2]: Rationale and test program Christoph Lameter
2004-10-12 20:19 ` Periodic posix timer support broke between 2.6.9-rc1 and 2.6.9-rc1-bk17 Christoph Lameter
2004-10-12 22:24 ` George Anzinger
2004-10-13 18:08 ` Alexander Nyberg
2004-10-13 18:11 ` 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.