All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: David Edelsohn <dje@watson.ibm.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel Gurus Help! Possible kernel bug in conversion of jiffees in nanosleep.
Date: Sun, 13 Feb 2000 11:51:20 -0500	[thread overview]
Message-ID: <v03110700b4cc8fce0321@[209.183.136.12]> (raw)
In-Reply-To: <200002130440.XAA25134@mal-ach.watson.ibm.com>


Hi,

>	Maybe submit the question to the glibc-alpha mailinglist as well?
>
>David

I submitted two bug reports about this via the glibc bug database.

The second report just adds info about the first.

The bug reports are 1597 and 1598.

I have previously fixed pthread_cond_timedwait in glibc 2.1.3 to actually
work recently but a final "cleanup" recently committed patch rewrote things
so that it no longer worked.

The funny thing is that their technique *should* work if the remtime value
from nanosleep would actually decrease and not increase.

So I think the whole thing is actually a kernel bug but I am not sure.

I know nothing about jiffees and their conversion to and from time values
and I am not sure how jiffees could ever grow (lost jiffees added back?).

If anyone who knows something about jiffees and conversions could look at
nanosleep I would greatly appreciate it.

Thanks,

Kevin


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2000-02-13 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-13  4:21 Kernel Gurus Help! Possible kernel bug in conversion of jiffees in nanosleep Kevin Hendricks
     [not found] ` <200002130440.XAA25134@mal-ach.watson.ibm.com>
2000-02-13 16:51   ` Kevin B. Hendricks [this message]

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='v03110700b4cc8fce0321@[209.183.136.12]' \
    --to=khendricks@ivey.uwo.ca \
    --cc=dje@watson.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.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.