From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] travel backwards in time?
Date: Thu, 18 Oct 2001 13:21:45 -0700 [thread overview]
Message-ID: <20011018132145.H4123@tausq.org> (raw)
Recently Grant and I have observed several hangs in do_gettimeofday on a
c3k running 32 or 64-bit kernels (UP).
The symptom we see is gettimeoffset returns a negative number which
results in a huge (unsigned) usec offset in do_gettimeofday, which ends
up spinning in a while loop.
On further investigation we found this piece of code that we don't
quite understand in the gettimeoffset function:
/* this is the intended time of the next tick */
last_tick = cpu_data[smp_processor_id()].it_value;
/* so subtract one tick */
/* and account for possible difference between wall and actual time */
last_tick += clocktick * (jiffies - wall_jiffies - 1);
The last_tick adjustment looks a bit odd. Looking at ia64, it looks more
like this:
last_tick -= clocktick * (jiffies - wall_jiffies + 1);
I tried this and couldn't reproduce the hangs anymore, but am not sure
if this is the right fix.
jsm suggested we try an experiment to disable interrupts in the
timer_interrupt handler. I tried that yesterday (add a __cli() call) and
it didn't seem to fix the hangs.
Can someone more familiar with that part of the code (pb?) please comment?
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next reply other threads:[~2001-10-18 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <randolph@tausq.org>
2001-10-18 20:21 ` Randolph Chung [this message]
2001-10-18 23:23 ` [parisc-linux] travel backwards in time? Paul Bame
2001-11-29 18:58 ` Grant Grundler
2001-12-04 7:17 ` [parisc-linux] 2.4.16-pa12 broken on c3000 Randolph Chung
2001-12-05 17:45 ` Grant Grundler
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=20011018132145.H4123@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@parisc-linux.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