All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Woodruff <sjwoodr@yahoo.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] RT Timers problem
Date: Wed, 23 Apr 2003 14:54:04 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705588@msgid-missing> (raw)

Hi - i've encountered a couple of different, but
maybe related problems in Debian linux on an RX2600
(ia64).  Maybe someone can comment if they've seen
this before?

1. RT signals RTMIN, RTMIN+1, RTMIN+2 are not being
   delivered.  I created a simple test case that sets
   an interval timer set to fire once per second, 
   but the signal never arrives!  When i use RTMIN+3
   or greater, then the code works fine.  I can 
   provide the test code to anyone who is interested
   in trying it out on their system.

2. In some cases, a call to timer_create() will block.
   This one is harder to reproduce, but i've done it
   multiple times and have something like this in 
   my code:

fprintf(stderr, 
  "HMM: Creating timer with signo=%d\n", 
  signal_no);
status =  timer_create(CLOCK_REALTIME,
  &h_event_struct, &h_timer_id);
fprintf(stderr, 
  "HMM: Timer created, status = %d\n", status);

And in the output, only the first line is
printed.  The timer_create() never returns!  I also
did a strace and the tail of that is:

write(2, "HMM: Creating timer with signo="..., 35HMM:
Creating timer with signo5
) = 35
getpid()                                = 591
getrlimit(RLIMIT_STACK, {rlim_curÅ92*1024,
rlim_max=RLIM_INFINITY}) = 0
brk(0)                                  0x600000000009c000
brk(0x60000000000a4000)                 0x60000000000a4000
pipe([2973872, 536870912])              = 4
SYS_1213(0x20000000000393a8, 0x60000000000988c0,
0x7fe0, 0xf00, 0x20000000002fc640, 0x20000000000393a8,
0x20000000002fc640, 0xf00) = 600
write(5, "\1\0\0\0\0\0\0\0\5\0\0\0\0\0\0\0pj-\0\0\0\0
\30\0\3\0\0"..., 168) = 168
rt_sigprocmask(SIG_SETMASK, NULL, [RT0], 8) = 0
write(5, "\200\300/\0\0\0\0
\0\0\0\0\0\0\0\0\10{\7\0\0\0\0 \10\257"..., 168) = 168
rt_sigprocmask(SIG_SETMASK, NULL, [RT0], 8) = 0
rt_sigsuspend([]

and there it sits.

Has anyone seen either of these problems come up
on debian linux/ia64? For what its worth, i was
using redhat AS back in January and the problems
never popped up back then, so i do think may be
specific to the librt provided in debian:
libc6.1-dev: /usr/lib/librt.so

Thanks,

/steve


==----------------------------------------------------------
 Steve Woodruff, N9OH @ 42.18N 88.34W, sjwoodr@yahoo.com

__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com


             reply	other threads:[~2003-04-23 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 14:54 Steve Woodruff [this message]
2003-04-23 15:01 ` [Linux-ia64] RT Timers problem Matthew Wilcox
2003-04-23 15:05 ` Steve Woodruff
2003-04-23 16:30 ` Steve Woodruff

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=marc-linux-ia64-105590723705588@msgid-missing \
    --to=sjwoodr@yahoo.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.