Date: Wed, 5 Mar 2003 12:27:19 +1000 (EST) From: Andy Farkas <andyf@speednet.com.au> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: Volunteer with genuine i386 cpu & lots of time wanted. Message-ID: <20030305113829.A58375-100000@hewey.af.speednet.com.au> In-Reply-To: <29201.1046297598@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Feb 2003, Poul-Henning Kamp wrote:
> Is there anybody out there who can try to run a straight -current
> on a _real_ i386 class CPU ?
>
> Ie, not a i486, not a Cyrix, not an AMD but a genuine Intel i386DX
> (SX would be but too suicidal to be informative).
Well, finally got a kernel to boot on a 16MHz 386SX (suicidal is an
understatement!) - will this do?
(Actually, the box is a AST Bravo/286 with the 80286 CPU replaced with a
386SX upgrade. The company I used to work for made various CPU upgrade
products for 286's and 386's in the early 90's, especially for IBM PS/2's)
Had to patch the npx_attach() function in src/sys/i386/isa/npx.c to get it
to work though. It seems revision 1.131 broke FPU-less CPU support:
(bad bde, no cookie)
> diff -u npx.c-orig npx.c
--- npx.c-orig Wed Mar 5 11:42:49 2003
+++ npx.c Wed Mar 5 11:43:27 2003
@@ -495,7 +495,7 @@
}
npxinit(__INITIAL_NPXCW__);
- if (npx_cleanstate_ready == 0) {
+ if (npx_cleanstate_ready == 0 && npx_exists) {
s = intr_disable();
stop_emulating();
fpusave(&npx_cleanstate);
I'll try and get some data for your clock/time tracking requests in a few
days. I assume you want wall-clock tracking info for both with and
without ntpd running?
> I am also not interested in people running heavily modified source
> trees, it is -current I am interested in. (It's OK to fiddle the
> kernel config and hints of course.)
>
> If somebody has the time and inclination, I have a number of questions
> I would like answers to:
>
> 1. Does -current even boot on that vintage of hardware any more ?
>
> 2. Does it survive a kernel (GENERIC) build ?
> 2a. Does the clock track wall-clock time correctly while doing so ?
>
> 3. Does it survive a buildworld ?
> 3a. Does the clock track wall-clock time correctly while doing so ?
>
> 4. Can ntpd run against some random (but decent) NTP server steer
> the clock ?
> 1) If the machine is idle
> 2) During buildworld.
> Please notice if
> a) ntpd resorts to clock steps
> b) ntpd exits
> c) ntpd core dumps
>
> Thanks in advance!
>
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030305113829.A58375-100000>