From: John Soros <sorosj@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] lguest on 2.6.25
Date: Mon, 25 Aug 2008 20:48:41 +0200 [thread overview]
Message-ID: <20080825204841.3806af18@dazone> (raw)
In-Reply-To: <70babc1dbfdd8db3637a493869aa3726@coraid.com>
Hello again,
Well, i don't think I am starting two timesync, ps a shows only one:
cpu% ps a |grep timesync
bootes 77 0:00 0:00 92K Pread timesync
I also can not write to /dev/rtc, so the timesync part of cpurc fails, this part in particular
=========snip
if(! ps|grep -s timesync) {
aux/timesync -n pool.ntp.org
if (test -e '#r/rtc') @ {
sleep 10 # let timesync correct the time
awk '{print $1}' /dev/time >'#r/rtc' # fix hw clock
} &
}
=============
awk: i/o error occurred while closing /dev/stdout
input record /dev/time:1
source line 1
I have also tried to compile the kernel by doing:
cpu% fcp /n/sources/contrib/rminnich/lguest/lg25.tgz $home/src; cd $home/src; tar xzf lg25.tgz;
cpu% mkdir src/boot
cpu% mkdir src/ip
cpu% mkdir src/pc
cpu% mkdir src/port
cpu% rc bin/rc/lguest
cpu% mk 'conf=lguestcpu'
.....
8c -FTVw lgkbd.c
../port/portdat.h:536 dat.h:130 lgkbd.c:4 syntax error, last name: Tval
mk: 8c -FTVw lgkbd.c : exit status=rc 887: 8c 889: error
Any help would be appreciated, this timesync problem is causing me quite some headaches :-)
Thanks
John
On Mon, 25 Aug 2008 10:59:37 -0400
erik quanstrom <quanstro@coraid.com> wrote:
> >> both the excessive load and these messages sound like a timesync problem.
> >>
> >
> > yeah, that's really weird. One option is to set up the kernels without
> > any fancy timers -- just use the old PC timers.
>
> do you think that's the problem?
>
> time jumping backwards doesn't seem like something that could
> be traced to some oddity of the lguest environment. (at least i
> lack the imagination to know how this could happen.) it sounds
> more like the traditional problem of having started two timsyncs.
>
> it any event, fixing timesync properly is likely to fix the excessive
> load problem.
>
> - erik
>
>
next prev parent reply other threads:[~2008-08-25 18:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 23:23 Alex Lee
2008-08-25 4:26 ` ron minnich
2008-08-25 4:32 ` ron minnich
2008-08-25 4:58 ` Alex Lee
2008-08-25 9:03 ` John Soros
2008-08-25 10:56 ` erik quanstrom
2008-08-25 14:52 ` ron minnich
2008-08-25 14:52 ` ron minnich
2008-08-25 14:59 ` erik quanstrom
2008-08-25 15:09 ` ron minnich
2008-08-25 18:48 ` John Soros [this message]
2008-08-25 18:54 ` lucio
2008-08-25 20:39 ` John Soros
2008-08-25 21:27 ` John Soros
2008-08-25 23:53 ` [9fans] Anyone handy with Alpha assembler? Benjamin Huntsman
2008-08-26 15:24 ` Paweł Lasek
2008-08-26 17:56 ` Benjamin Huntsman
2008-08-26 22:03 ` Paweł Lasek
2008-08-26 23:09 ` Benjamin Huntsman
2008-08-25 22:44 ` [9fans] lguest on 2.6.25 ron minnich
2008-08-26 6:44 ` John Soros
2008-08-28 2:28 ` Alex Lee
2008-08-28 2:38 ` ron minnich
2008-08-28 12:06 ` erik quanstrom
2008-08-28 8:21 ` John Soros
2008-08-28 15:38 ` ron minnich
2008-08-28 16:50 ` John Soros
2008-08-28 16:59 ` erik quanstrom
2008-08-28 17:24 ` Alex Lee
2008-08-28 18:07 ` John Soros
2008-08-28 8:27 ` Richard Miller
2008-08-28 11:55 ` erik quanstrom
2008-08-28 17:34 ` Alex Lee
2008-08-28 2:39 ` ron minnich
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=20080825204841.3806af18@dazone \
--to=sorosj@gmail.com \
--cc=9fans@9fans.net \
/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).