Date: Sun, 6 Oct 2002 03:30:09 -0700 (PDT) From: "Bjoern A. Zeeb" <bzeeb@zabbadoz.net> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/43491: microuptime () went backwards Message-ID: <200210061030.g96AU9Bg025440@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/43491; it has been noted by GNATS.
From: "Bjoern A. Zeeb" <bzeeb@zabbadoz.net>
To: Valentin Nechayev <netch@iv.nn.kiev.ua>
Cc: bug-followup@FreeBSD.ORG
Subject: Re: i386/43491: microuptime () went backwards
Date: Sun, 6 Oct 2002 10:26:15 +0000 (UTC)
On Sun, 6 Oct 2002, Valentin Nechayev wrote:
Hi,
> You can do it for your particular system. For most systems, it is not such
> useful. Pity for you but I suggest you to change hardware. VIA Apollo MVP3
> has too strange relations with time counting. I saw a system with it
yeah I heared. I think it was Alan Cox who had fun with it in
linux kernel...
> Of course one can argue that total PC time counting is horribly brain-damaged,
> but it is common place and we should live with it. (Only PIIX4 seems to be
> correct. But 4.5 secs is too small period.) Change it to Intel chipset based
> motherboard and you will be satisfied.
Just to mention: this machine has been running FreeBSD since somewhen in late
1999 (Sep-Dec) (starting with 3.3-REL) and is up almost 24/7/365 and doing
really fine.
This was the very first issue I had and just to say "change your
hardware" is not a point for me.
There two things that happend lately I should have mentioned too:
a) I turned on softupdates and after installing the 3rd disc had lots
of directory tree moving yesterday evening (> 15 GB) before this
happened i.e. it started while the last MBs where freed on the
original slice minutes after the move had completed (softupdates
syncing)
b) started to run ntpd with server 127.127.1.0 two days ago (cause of
no permanent connection to a timeserver and the system internal
clock wasn't off by half a minute in >2 years).
Don't know if b) might be realted to this one.
Having too few knowledge about the real internals on what is happening
there in the kernel (just had a 5 minute look at it yesterday) and
what is f%$^ed up with these VIA chips I would say if we did not get a
workaround for it in the last two years ...
> I don't see a reason to keep this PR open. You may want to open PR to fix
... feel free to close it. If it happens a second time and I can find some
minutes I will have a look at it and also check what's going on in HEAD.
> total FreeBSD time counting subsystem or simply ask phk@ to describe it
> in details, but this shall be another PR.
For sure I am not going to open that one in the moment ;-)
Thanks
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210061030.g96AU9Bg025440>