From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] timesync doubletime
Date: Mon, 7 Aug 2006 22:40:16 -0500 [thread overview]
Message-ID: <dc35e94bc62850e8027ef8714e60c771@quanstro.net> (raw)
In-Reply-To: <6c264481f9b33ea17e28646b71d2565e@plan9.bell-labs.com>
this kernel has been running correctly for weeks. only when i tried running
"aux/timesync -f /srv/sources". (i accidently had two running at once at one point.)
did things go haywire. killing the timesync procs has not helped.
so, without the benefit of timesync, have not seen any problems. i may
be having a different or only sightly related problem. especially since i have
neither a realtech, gbe, amd nor a multicore processor. just a "blue-light
special" va linux dual coppermine.
- erik
On Mon Aug 7 21:13:17 CDT 2006, geoff@plan9.bell-labs.com wrote:
> We've recently seen some slowness here that affects the clock. So far
> I think it's only been seen on multiprocessor (multicore) AMD64
> systems with Realtek 8169 Gb Ethernet. Setting *ncpu=1 fixes the
> problem at the cost of using only one processor. When we tried to add
> debugging to the kernel to track this down, the problem vanished.
next prev parent reply other threads:[~2006-08-08 3:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 0:12 erik quanstrom
2006-08-08 0:42 ` Kris Maglione
2006-08-08 1:39 ` erik quanstrom
2006-08-08 1:46 ` andrey mirtchovski
2006-08-08 2:37 ` erik quanstrom
2006-08-08 1:59 ` andrey mirtchovski
2006-08-08 3:10 ` erik quanstrom
2006-08-08 6:09 ` Steve Simon
2006-08-08 6:15 ` andrey mirtchovski
2006-08-08 6:21 ` andrey mirtchovski
2006-08-08 15:00 ` John Floren
2006-08-08 2:09 ` geoff
2006-08-08 3:40 ` erik quanstrom [this message]
2006-08-08 3:09 ` Kris Maglione
2006-08-08 14:53 ` Russ Cox
2006-08-08 20:07 ` erik quanstrom
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=dc35e94bc62850e8027ef8714e60c771@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).